Implementing VNAV support in FlightGear: Difference between revisions

Implementing VNAV support in FlightGear (view source)

7 bytes added , 3 December 2013

20,741

edits

@@ Line 171: / Line 171: @@
 Also, VNAV profile data for any particular YASim aircraft would have to be re-built every time someone made a change to the YASim FDM. Seemingly minor FDM tweaks can have major YASim impacts, particularly if the developer isn't very experienced or knowledgeable with YASim. So VNAV data and the YASim aircraft FDM version would have to be tightly coupled. If someone commits a Git change to the aircraft's FDM, then the VNAV DB for that plane is hosed until it's re-calculated.<ref>{{cite web |url=http://forum.flightgear.org|title=YaSim vs. VNAV (by PM)
-|author=Buckaroo |date=Mon Dec 02, 2013 9:38 pm  }}</ref>|
+|author=Buckaroo |date=Mon Dec 02, 2013 9:38 pm  }}</ref>|Buckaroo}}
-}}
 {{cquote|There are some pending merge requests to add some Yasim features, but we have an issue that since none of the current C++ developers own, or are experts in Yasim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.