> FGLGear.cpp line 507 
>  Here's the code: 
>  // Crash detection logic (really out-of-bounds detection) 
>      if (compressLength > 500.0 ||
>          vForce.Magnitude() > 100000000.0 ||
>          vMoment.Magnitude() > 5000000000.0 ||
>          SinkRate > 1.4666*30)
>      {
>        PutMessage("Crash Detected: Simulation FREEZE.");
>        Exec->Freeze();
>      }
> The undercarriage definition is very flexible. It gives the facilities
> to manage an aircraft customised crash animation with the help of a
> nasal script.
> If an improvement must be done it could be done on the old existing code
> with specifics properties like that one which is coming from a Dave
> mail.
> <crash-detection>
>   <altitude-agl>0</altitude-agl>
>    <g-z-max>11.0</g-z-max>
>    <g-z-min>5.0</g-z-min>
>    <g-x-max>20</g-x-max>
>    <g-x-min>20</g-x-min>
>    <qbar>1089.0</qbar>
>    <pitch-rate>3.7</pitch-rate>
>    <yaw-rate>3.5</yaw-rate>
>    <mach>0.99</mach>
>  </crash-detection>

The out-of-bounds detection logic was a development piece of code, really. That 
can be removed if it is causing a problem.

Jon


_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to