Re: [Flightgear-devel] (no subject)
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=boolfalse/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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net 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=49501711iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] (no subject)
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 tors...@t3r.de 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=boolfalse/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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing listFlightgear-devel@lists.sourceforge.nethttps://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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net 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=49501711iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] (no subject)
On 08/05/2013 01:38 AM, Михаил Сойтанен wrote: 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? Executive summary: VOR alignment in nav.dat should reflect the VOR alignment as reported in the Airport/Facility Directory ... which is generally *not* the same as the actual local magnetic variation. I would expect Robin's xplane data files to track this properly in most cases, since they are routinely rebuilt from official data. = In the real world, VOR alignment is controlled by whomever owns and operates the VOR. It gets changed only on special occasions. There are three things to consider: a) The path through space of the actual electromagnetic VOR radials; b) The airways as plotted on the charts, typically defined in terms of VOR radials; c) The actual local magnetic variation. For obvious reasons, there needs to be very little discrepancy between (a) and (b). The discrepancy between (c) and (a), or between (c) and (b), is much less tightly controlled. Back in the days before GPS, pilots typically would not notice a discrepancy of this kind, even if it was rather large. If you decide to go looking for such discrepancies, they are easy enough to find, by finding the VOR's alignment (i.e. nominal magnetic variation) as documented in the Airport/Facility Directory and cross-checking it against the current local magnetic variation. As a less-precise version of the same idea, you can look at the orientation of the charted compass rose and compare it against the local magnetic variation. Nowadays, however, it is fairly easy for pilots to detect such a discrepancy, even if they weren't looking for it, by cross-checking a VOR radial against the GPS bearing-to-station. This is a predictable source of confusion for pilots working toward their instrument rating. Changing VOR alignment requires revising the charts, so they don't do it more often than necessary. FAA standards say they are supposed to re-align VORs to keep them within 1 degree of the actual magnetic variation, but this effort is chronically underfunded and it is easy to find VORs that are mis-aligned by more than a degree, sometimes quite a bit more. Bottom line: The VOR alignment in nav.dat should track the VOR alignment as documented in the A/FD. It should not track the actual local magnetic variation. -- 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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] (no subject)
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 tors...@t3r.de mailto:tors...@t3r.de 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=boolfalse/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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net mailto:Flightgear-devel@lists.sourceforge.net 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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net mailto:Flightgear-devel@lists.sourceforge.net 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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net 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=49501711iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] (no subject)
Thanks for answers, I will send data about Russian VOR's to Robin, because I have found, that variations are outdated. 2013/8/5 Torsten Dreyer tors...@t3r.de 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 tors...@t3r.de 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=boolfalse/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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing listFlightgear-devel@lists.sourceforge.nethttps://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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net 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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing listFlightgear-devel@lists.sourceforge.nethttps://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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net 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=49501711iu=/4140/ostg.clktrk___ Flightgear-devel mailing list
Re: [Flightgear-devel] (no subject)
Hi, Thanks for answers to both questions, learned something new. And sorry for (no subject) - somehow slipped through. Tomash -- 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=49501711iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flightgear-devel Digest, Vol 88, Issue 1
Le 05/08/2013 11:51, flightgear-devel-requ...@lists.sourceforge.net a écrit : Message: 11 Date: Sun, 04 Aug 2013 22:49:11 +0200 From: jean pellotierjean.pellot...@wanadoo.fr Subject: [Flightgear-devel] fgdata space in filenames To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Message-ID:51febe47.1060...@wanadoo.fr Content-Type: text/plain; charset=iso-8859-1 Hi, Hi weren't the space in fgdata filenames banished long time ago? here's a list of current offending files. I'd like to give a special reward to the README OR DIE.txt :D You're absolutely right. And I want answer because there are several aircrafts of my hangar in my list :( With 232 aircraft in my hangar, I receive regular improvements. I always try to correct the problems, but I admit parfoit I'm tired of correcting the same mistakes from the same people. Most problems come from members of the PAF and are quite old: ((sounds of D510, some liveries, etc ...) For the He 177 I do not understand why the dev files and studies are present on GIT. There is an error on my part :) For the He 177 I'm the only culprit. Sorry. Now, and again, I recall that GIT is a place of development. This is not a finished products stokage! It is normal that there are problems. Regards Emmanuel -- BARANGER Emmanuel http://helijah.free.fr http://embaranger.free.fr -- 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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] (no subject)
On 08/05/2013 03:45 AM, Михаил Сойтанен wrote: I will send data about Russian VOR's to Robin, because I have found, that variations are outdated. That's good ... but it would be even better to figure out how to get /systematic/ updates from reliable sources, now and in the future. Is there perhaps a Russian government web site that has this information? Also note that in addition to VOR alignment data, there is a need for other types of navaids and other details, including frequencies, ident codes, et cetera ... as well as the addition and deletion of entire navaids. -- 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=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgdata space in filenames
Hi Jano, weren't the space in fgdata filenames banished long time ago? Fixed those that I'e touched throughout the years, will leave the others to their respective authors/comitters. Thanks! Gijs -- 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=49501711iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
