Mmmm... I can reproduce the first freeze I was refering to, almost 100% of
the times...
Do this,
start from KSFO, normal heading, start engine with throttle set to MAX and
pull the joystick to force the plane raise ASAP... with some luck you'll
get FGFS frozen in 15 to 20 seconds (just a few
Curt,
maybe you were right and the sound system is responsible for the
freezes... I got it to hang again while debugging and I saw this from a
backtrace in gdb:
(gdb) backtrace
#0 slSamplePlayer::skip (this=0x9499798, nframes=1024) at sl.h:260
#1 0x08308cc1 in slPlayer::preempt
no terrain intersection
no terrain intersection
load() base = /usr/local/lib/FlightGear/Scenery
Loading tile
/usr/local/lib/FlightGear/Scenery/w180n1879048190/w180n1879048191/5712
This is (most likely) caused by the current lack of crash protection in
JSBSim. What's happening here
Flavio Villanustre writes:
I saw a different kind of crash (literally)... After crashing against a
mountain, everything became unresponsive and the engines suddenly stopped.
I couldn't turn the engine back on and the pannel looked funny, with
missing needles, instruments, etc. (I regret
Jon S. Berndt writes:
I am trying to add some logic in there that freezes the model when
a crash occurs. The problem is coming up with a set of cases that
works for crash detection. This is hard to do accurately without a
surface normal and knowing which triangle a contact point is on.
