20,741
edits
Line 214: | Line 214: | ||
* Extend the FGScript template to compute FPAs for each leg, and add a monitoring routine that tracks compliance {{Not done}} | * Extend the FGScript template to compute FPAs for each leg, and add a monitoring routine that tracks compliance {{Not done}} | ||
* Come up with a JSBSim script (FGScript) for a test flight with multiple waypoints (different altitudes) using the c310 in the KSFO area (default scenery) {{progressbar|70}} (now automated via modified route manager/flight plan exports) | * Come up with a JSBSim script (FGScript) for a test flight with multiple waypoints (different altitudes) using the c310 in the KSFO area (default scenery) {{progressbar|70}} (now automated via modified route manager/flight plan exports) | ||
* Extend the modified route manager dialog to show | * Extend the modified route manager dialog to show the route {{Progressbar|70}} | ||
* Extend the route manager to also show a vertical profile using a canvas-driven altitude/distance graph {{Not done}} | * Extend the route manager to also show a vertical profile using a canvas-driven altitude/distance graph {{Not done}} | ||
* Extend the systems/GNCUtilities.xml file to also support altitudes and compute required FPAs for each waypoint {{Not done}} | * Extend the systems/GNCUtilities.xml file to also support altitudes and compute required FPAs for each waypoint {{Not done}} | ||
* look into encoding min/max pitch and thrust settings as part of the script, so that safety margins are not violated {{Not done}} | |||
* .... | * .... | ||
* port the c310 example and use the 737 instead, because it better matches airliners available in FG (will also need AP work) {{Not done}} | * port the c310 example and use the 737 instead, because it better matches airliners available in FG (will also need AP work) {{Not done}} |