> > Begin forwarded message: > > > Modified Files: > > > navradio.cxx navradio.hxx > > > Log Message: > > > Various LOC/GS improvements from John Denker, adapted to trunk by me > > > (hopefully not introducing too many bugs along the way). Includes: > > > > A note for anyone trying out the new code - if you're not in one of > > the aircraft I fixed the GS sensitivity for last week (which is only a > > handful right now), then your GS indication may still be incorrect. > > Aircraft that assumed the range was -3.5 .. 3.5 on gs-needle- > > deflection will report correctly, aircraft that assumed any other > > range (especially -10 .. 10) will be wrong (but still usable). If in > > doubt, check where the GS needle/pointer is when the clamped > > properties (gs-needle-deflection-deg or gs-needle-deflection-norm) are > > on the peg. > > I only had time for a single ILS approach at my home base with the Seneca. > I felt pretty comfortable with the new implementation. I noticed two little > glitches: > The has-gs property does not go to false if you switch from an ILS > frequency to a VOR frequency. Probably something like > has_gs_node->setBoolValue(false); > is needed near line 802 in navradio.cxx. > > And the glideslope indicator quickly (many times per second) moves between > to-high and to-low indication when you are very close to the antenna below > 50-100ft above threshold. I havn't investigated this in detail but these > are probably the modeled side lobes which are naturally very close to each > other so close to the station? I think this part needs some tuning, because > I have never observed something like that in reality. > > I'll try to do some more testing during this weekend. > > Torsten One more remark: 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 think the meaning of the range of a navaid is "only use the indication withing this range. If your distance is greater than the given range, indications _might_ be unreliable".
And another: I think the side lobes are to strong. Currently they allways exist and the signal strength is as strong as the original lobe, which shouldn't be the case unless one has a really bad antenna. When side lobes are used instead of the original one, the range and the signal strength should be adjusted by a significant magnitude. Hope this helps Torsten Torsten ------------------------------------------------------------------------------ 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
