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 21:51, 30 November 2013
, 30 November 2013→Problem
| Line 2: | Line 2: | ||
== Problem == | == Problem == | ||
http://forum.flightgear.org/viewtopic.php?f=40&t=13777&hilit=performance+vnav#p140230 | |||
<pre> | <pre> | ||
I don't think any aircraft AP supports vertical route navigation yet - and the route-manage itself only has partial support for editing waypoint altitude. There's no real obstacle - waypoints store an altitude (and speed), and the AP can read it, but nobody spent time making it work yet. | |||
Vertical modes (VNAV) also tend to depend more on fuel/load and engine performance data from the FMS, which is an area that's been lacking in FlightGear, | Vertical modes (VNAV) also tend to depend more on fuel/load and engine performance data from the FMS, which is an area that's been lacking in FlightGear, | ||
so hard to model the climb and descent profiles meaningfully.</pre> | so hard to model the climb and descent profiles meaningfully.</pre> | ||
It is the single most important reason why this isn't yet supported by FlightGear, which boils down to a lack of support by the FDMs (JSBsim/YaSim) actually. | It is the single most important reason why this isn't yet supported by FlightGear, which boils down to a lack of support by the FDMs (JSBsim/YaSim) actually. | ||
So far, the general consensus has been that it simply isn't yet possible in FlightGear to properly implement VNAV. | So far, the general consensus has been that it simply isn't yet possible in FlightGear to properly implement VNAV. | ||
| Line 35: | Line 37: | ||
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. | ||
== Related Discussions == | == Related Discussions == | ||