|
|
Line 163: |
Line 163: |
| * {{cite web |url=http://knology.net/~stirmac/POHfiles/BAC777%20POH.pdf |title=777 Pilots Operating Handbook }} | | * {{cite web |url=http://knology.net/~stirmac/POHfiles/BAC777%20POH.pdf |title=777 Pilots Operating Handbook }} |
| }} | | }} |
|
| |
| == Methods for implementing VNAV ==
| |
| #<big>(virtual flight-testing database)</big>:
| |
|
| |
| Instead of doing all this "live" inside the FDM via a reverse solver, another method would be doing virtual test flights and gathering the required flight data to come up with a virtual PerfDB, i.e. actually write test data to some form of database (eg. SQLite) so that this could be queried at runtime in FG.
| |
|
| |
| '''What is required to apply this method?'''
| |
|
| |
| * data analysis to determine the scope of fields, and the domain of values for the gathered data (the domain of units, and relavent data for VNAV's trajectory functions)
| |
| * an agreed standard of tests applied to all airplanes (climb/descend profiles with different configurations)
| |
| * an agreed format(data file structure) in which this data is formated, or using an improved database approach and provide mapping via a DBMS for a changing file structure
| |
| * an agreed property *list inside flightgear to hold this data (a single property won't suffice)
| |
| * an interface for flightgear to query the data file through the DBMS (FlightGear's scripting language Nasal does have SQLite bindings, another option would be a flat text/XML file)
| |
| * a way of implementing this data into the aircraft's model(usually xml file)
| |
|
| |
|
| |
|
| == JSBSim == | | == JSBSim == |