Dave Perry said:
> I updated SimGear, FlightGear source, and the base package from CVS and
> am getting repeatable aborts or segfaults. The one documented below was
> after flying from KBTL to KAZO and executing a precision approach using
> the ils (110.9) to runway 35 at KAZO. It seems to be related to how
> long I have been flying as on the previous flight, I had done several
> touch-n-goes at KBTL before departing for KAZO and I only got about 2/3
> of the way to KAZO when it aborted.
>
> As you can see, I was running terrasync and atlas. I will try this
> flight again w/o terrasynch or atlas. System is an athlon XP 1800+ with
> 512MB of DDR and Nvidia 5600 ultra running Suse 9.0.
> It looks like a type error.
>
I'm going to take a stab in the dark and say this probably won't happen if you
do not activate glide slope hold. Curt has a patch which will get added when
he comes up for air.
In the meanwhile, if you want to fix your local copy, try something like this
in navcom.cxx:
@@ -516,16 +517,18 @@
// estimate horizontal speed towards ILS in meters per minute
double dist = last_x - x;
last_x = x;
- double new_vel = ( dist / dt );
+ if ( dt > 0.0 ) { // avoid nan
+ double new_vel = ( dist / dt );
Best,
Jim
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
