I updated SimGear, fgfs source and data yesterday for both my desktop
and notebook. The glide slope is now broken. The angle seems correct
but it now acts as if the ILS is always from 0 ft MSL. I tried the rw
23 ILS at KBTL with field elevation of 952 ft, rw 23 at KBJC with field
elevation of 5670 ft and rw 28 at KSFO with field elevation near 0. At
KSFO, all seems correct. At KBTL, I flew outbound at 1250 ft MSL and
the GS crossed center at the OM. That was 950 ft too low, or about the
field elevation. Rockey Mountain Metro is too high to make the same check.
I put
cout << "nav_elev = " << nav_elev << endl;
after line 361 and un commented
cout << "dist = " << x << " height = " << y << endl;
after line 594 in navradio.cxx.
This produced at KBTL and the pa24-250 the following in the log window:
creating 3D noise texture... DONE
KI266 dme indicator #0 initialized
Nasal Electrical System Initialized
power up
nav_elev = 0
nav_elev = 930
nav_elev = 0
nav_elev = 930
nav_elev = 0
nav_elev = 930
nav_elev = 0
nav_elev = 930
nav_elev = 0
nav_elev = 930
nav_elev = 0
dist = 553.906 height = 281.795
nav_elev = 930
nav_elev = 0
dist = 553.906 height = 281.795
nav_elev = 930
nav_elev = 0
dist = 553.906 height = 281.795
nav_elev = 930
nav_elev = 0
The height is correct. It looks like every other call of
FGNavRadio::updateWithPower gets the wrong value for nav_elev. Hope
this helps find the bug.
Dave P
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
