I've updated both of your/John Denker's glideslope/LOC patches against current trunk, hopefully correctly, and done quite a bit more testing. It's good practice for my ILS approaches!

I'm reasonably happy that all the numbers coming out are plausible, so my inclination at this point is to commit to trunk, and let people with more knowledge of the real world test.

One major remaining issue is the nav-radio code picking the 'wrong end' LOC/GS, which is a separate mess. I'm going to verify that penaltyForNav() (in navlist.cxx) is behaving correctly, but that's a short term fix; longer term, I've some ideas to ensure only one end of a paired ILS installation is active.

Current patch is attached, comments appreciated as always.

Regards,
James

Attachment: jsd-glideslopes.patch
Description: Binary data


------------------------------------------------------------------------------
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

Reply via email to