20,741
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 18:51, 2 December 2013
, 2 December 2013no edit summary
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
{{#ev:youtube|h4AUfkEcwIg}} | {{#ev:youtube|h4AUfkEcwIg}} | ||
--> | --> | ||
== Objective == | |||
{{Issue|640}} | |||
Determine how to implement the building blocks required for supporting VNAV (vertical navigation) in FlightGear. | |||
== VNAV == | == VNAV == | ||
| Line 74: | Line 79: | ||
The 3rd party approach is being used for TPPs data, but in the case of FDMs, we would need 100% accurate FDMs, too - so it would be better to directly use the FDM for computing a performance DB. | The 3rd party approach is being used for TPPs data, but in the case of FDMs, we would need 100% accurate FDMs, too - so it would be better to directly use the FDM for computing a performance DB. | ||
Supporting VNAV/LNAV still is tricky for other reasons, and currently not on anybody's agenda - it's not just something that can/should be tackled by a single aircraft developer, it requires lower-level changes in FlightGear's architecture and the way FDMs are used. | Supporting VNAV/LNAV still is tricky for other reasons, and currently not on anybody's agenda - it's not just something that can/should be tackled by a single aircraft developer, it requires lower-level changes in FlightGear's architecture and the way FDMs are used. | ||
== Background == | == Background == | ||