18
edits
Implementing VNAV support in FlightGear: Difference between revisions
Jump to navigation
Jump to search
Implementing VNAV support in FlightGear (view source)
Revision as of 03:56, 1 December 2013
, 1 December 2013no edit summary
Flyingsolo (talk | contribs) No edit summary |
|||
| Line 87: | Line 87: | ||
To develop VNAV support, we should take the 777 as it is in the base package and has currently the best developed AP. ThorstenB has put a lot of time in it, and we have an user here who knows the real one. | To develop VNAV support, we should take the 777 as it is in the base package and has currently the best developed AP. ThorstenB has put a lot of time in it, and we have an user here who knows the real one. | ||
== Methods for implementing VNAV == | |||
#(virtual flight-testing database): | |||
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 | |||
* an agreed standard of tests applied to all airplanes | |||
* 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 inside flightgear to hold this data | |||
* an interface for flightgear to query the data file through the DBMS | |||
* a way of implementing this date into the aircraft's model(usually xml file) | |||