On 09/12/09 08:17, Torsten Dreyer wrote: > The glideslope updates are abruptly terminated at the configured range. This > does not match my experience. The configured range for the ILS at my home > base is 10NM as in nav.dat. This is within the standard instrument approach > procedure, so I don't get a glideslope indication beyond 10NM in FlightGear > (I do get one in RL). The point of descent is at 9.6NM which enables my > glideslope only 0.4 miles before descending, which is bad :-(
I agree, that's bad, and it needs to be fixed. However, I suspect that the problem is not in navradio.cxx but rather in nav.dat. I suspect the GS you are using has an extended service volume in real life, but this is not yet reflected in nav.dat. This is exactly the sort of bug we expect to see during the transitional phase. The phases are: Initial: navradio ignores nav.dat. Bugs in nav.dat do not matter and are not detectable. Transitional: navradio looks at nav.dat. Bugs in nav.dat are now apparent. <-- You are here. Final: nav.dat has been fixed to match real life. The range info in nav.dat is not currently authoritative; it's just guesswork. Robin is working on getting authoritative range data, but the results are not yet there. I've been using my version of navradio.cxx for years. Whenever I find a service volume that needs to be extended, I just edit my copy of nav.dat and send the diff to Robin. Bottom line: I suggest you edit your nav.dat and extend the range a few nm. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
