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 20:45, 1 December 2013
, 1 December 2013→Background
| Line 58: | Line 58: | ||
|title=New route manager? | |title=New route manager? | ||
|author=James Turner |date= Thu, 08 Oct 2009 15:17:18 -0700}}</ref>|James Turner}} | |author=James Turner |date= Thu, 08 Oct 2009 15:17:18 -0700}}</ref>|James Turner}} | ||
{{cquote|VNAV doesn't really make sense right now - it's not really implemented.<ref>{{cite web |url=http://forum.flightgear.org/viewtopic.php?f=25&t=13589&p=137485&hilit=vnav+hold#p137485 | |||
|title=B777-200ER VNAV | |||
|author=ThorstenB |date= Sun Sep 25, 2011 9:53 am}}</ref>|ThorstenB}} | |||
{{cquote| 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, | {{cquote| 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, | ||