Hi Torsten and all, On Mon, 2013-08-05 at 09:59 +0200, Torsten Dreyer wrote: > The first is in newnavradio which you can use by setting > <use-new-navradio type="bool">false</use-new-navradio> in your > aircraft xml as does the SenecaII. > Note: this is still an experimental feature and some > instruments/aircraft might not be compatible with that implementation. > I'll continue to work on this, once I find more time for fg hacking.
Could you please elaborate a bit on what might not work with a new code? Will the "standard" nav properties work, namely "nav-loc", "in-range", "heading-needle-deflection-norm", "gs-in-range", "gs-needle-deflection-norm", "dme-in-range", "nav-distance"? Are there any gotchas to keep an eye on? What improvements are worth highlighting? Pointer to docs or some earlier discussion if any will suffice. Thanks in advance! ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
