On Saturday, August 14, 2010 02:13:13 pm Stuart Buchanan wrote: > On Sat, Aug 14, 2010 at 9:50 PM, Stuart Buchanan wrote: > > So, I suspect the problem is in these properties that are being used > > in switch statements without a default value, but I don't know enough > > about JSBSim properties to be able to set a sensible default in the > > right place. > > Commenting out most of the "crashed" channel in > Systems/crash-detect.xml appears to solve the problem. > > -Stuart
The crash-detect freeze channel code was lifted from one of Dave Culp's models. But I never got around to actually using this code or figuring out what it does. So the "freeze" channel is basically dead code and should be removed. I will remove this in the next merge. Rather than commenting out the crashed channel way don't you try commenting out the "freeze" channel since it doesn't do anything at this point and is the likely cause of the issues you are having. The "crashed" channel is what stops the sim if an impact is detected or the airframe is over stressed. There is also a nasal script that detects things like exceeding VNE by too much for too long that also sets /fdm/jsbsim/systems/crash-detect/crashed so that the switch in the "crashed" channel can halt the simulation. I had one other user report having problems with the crash-detect code. He was also seeing seg faults. But this does not happen on my machine so I have not been able to trace down the cause. Thanks for digging into it and locating the probable cause. Please let me know if removing the "freeze" channel fixes this problem for you. Hal ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
