Le mardi 26 juillet 2005 à 23:13 +0200, Mathias Fröhlich a écrit :
Hi,
sorry for the late reaction.
Turns out to be a bad interaction between jsbsims crash detection and my
past initialization changes.
The attached patch fixes this by moving crash detection out of the
initialization phase
Mathias Fröhlich wrote:
Erik,
Can you apply that please to flightgears cvs.
I will care for JSBsim's cvs.
Done.
Erik
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Dave Perry wrote:
This bug showed up about 10 days ago with an update from cvs. Any
ideas what is broken?
Regards,
Dave Perry
I have started to investigate that problem but not found anything atm.
I can reproduce the bug in the same situation as you.
FG is *not* freezed. All (?) is working
Hi,
sorry for the late reaction.
Turns out to be a bad interaction between jsbsims crash detection and my
past initialization changes.
The attached patch fixes this by moving crash detection out of the
initialization phase of jsbsim.
Erik,
Can you apply that please to flightgears cvs.
I will
Le mardi 26 juillet 2005 à 23:13 +0200, Mathias Fröhlich a écrit :
Hi,
sorry for the late reaction.
Turns out to be a bad interaction between jsbsims crash detection and my
past initialization changes.
The attached patch fixes this by moving crash detection out of the
initialization phase
I have posted this issue twice before. This is with plib, SimGear, fg,
and data all from recent cvs. I have fgfs from cvs up-to-date on my
desktop and notebook, both running Linux FC3 and both have this bug
after updates from about 10 days ago.
I don't know if there are others that use fgfs
