Curt Olson wrote:

The last two days I've been hammering on the nav database code. My first goal is to directly support Robin's native nav database file format. In his latest data release, he separates out dme, gs, loc, and marker beacon transmitters rather than lumping them all into a single "ILS" record. This new data structure prompted me to do some code restructuring so that internally these are all kept as separate lists and searched and handled separately. This had a cascading affect on the code so I've gone and "touched" a lot of nav related code in a lot of places. I think it's all coming back together now and seems to be working nicely. I'm going to do some more testing and then commit tonight or tomorrow. I just wanted to give everyone a heads up so you can watch for this commit and make sure I didn't miss anything.

At least some of the glide slopes are now not working that were before this change.

The glideslope at KSFO is working.
The glideslope at Greeley, CO (I-DCI, 110.3) never comes off pegged at the bottom (saying you are high).
Same comment for the glideslope at Fort Collins-Loveland (I-FNL, 109.5).
The glideslope at Jeffco, CO (I-BJC, 111.7) is just a little high (saying you are low when the papi lights say you are right on).

The loc is better aligned now in these cases. The glideslopes used to be good as I have flown these approaches
in fgfs many times. I am working on my instrument rating.

By the way, I just bought a 1/3 ownership in a 1962 Piper Comanche (PA24-250).
GPS nav/com and DME nav/com.
I already had 92 hours in the Comanche 250, 260, and 400 from the late 60's and early 70's
and have always wanted to get into such a partnership. The other 2 owners work with me at
Seagate in Longmont, CO and the AC is hangared at 2V2 (Vance Brand) which is less
than a mile from Seagate. I will probably lose weight because I fly at noon instead of

_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED]

Reply via email to