From: Torsten D. <To...@t3...> - 2013-08-05 10:36:58
|
Hi Michail, the navradio code uses the magnetic variation as stored in nav.dat for the VOR. The environmental magnetic variation is not used for the VOR. The installed offset between magnetic and true north of the signal emitted by the VOR is published in the local AIP, so yes: we have to adjust nav.dat from time to time. HTH, Torsten Am 05.08.2013 10:38, schrieb ?????? ????????: > Let me ask my question here. In nav.dat file VORs have slave > variation. As I understand, slave variation of VOR depends on magnetic > variation at he location. Does Flightgear use this slave variation, or > it computes magnetic variation "on the fly"? > Do we need to track magnetic variation change every year and manually > edit nav.dat for it? > > > 2013/8/5 Torsten Dreyer <To...@t3... <mailto:To...@t3...>> > > Hi Tomash > > the navradio code is far from being perfect and and least to > attempts for improvements exist. > Unfortunately, both have currently stalled due to several reasons. > > 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. > > The second is a very detailed radio signal propagation model that > has not made its way into the repositories. > I don't know what the state of this is. > > I hope this helps - Cheers > > Torsten > > Am 04.08.2013 19:20, schrieb Tomash Brechko: >> Hello! >> >> In file src/Instrumentation/navradio.cxx method >> FGNavRadio::adjustILSRange the code that narrows ILS-LOC beam is >> commented out since the end of 2004. Are there any reasons not >> to have directed localizer beams? Being able to tune to >> localizer just from anywhere is a bit unnatural. >> >> -- >> Tomash Brechko >> >> >> ------------------------------------------------------------------------------ >> 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=49501711&iu=/4140/ostg.clktrk >> >> >> _______________________________________________ >> Flightgear-devel mailing list >> Fli...@li... <mailto:Fli...@li...> >> https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > > ------------------------------------------------------------------------------ > 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=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > <mailto:Fli...@li...> > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > > > > ------------------------------------------------------------------------------ > 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=49501711&iu=/4140/ostg.clktrk > > > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel |