Implementing VNAV support in FlightGear: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 30: Line 30:
Otherwise, it is not currently feasible to come up with VNAV/LNAV modes that properly work for different aircraft.
Otherwise, it is not currently feasible to come up with VNAV/LNAV modes that properly work for different aircraft.
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  
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.


{{cquote|Altitude constraints are a mess - in the short term, they are best avoided. Keep in mind the GPS code doesn't really do proper vertical  navigation - it computes some data like the altitude change and climb/ descent rate for a leg, but I'm not sure if any real aircraft is  driving the VNAV mode of an autopilot from it.
{{cquote|Altitude constraints are a mess - in the short term, they are best avoided. Keep in mind the GPS code doesn't really do proper vertical  navigation - it computes some data like the altitude change and climb/ descent rate for a leg, but I'm not sure if any real aircraft is  driving the VNAV mode of an autopilot from it.

Navigation menu