On Thu, 28 Jul 2005 00:47:26 +0200, Gerard wrote in message
[EMAIL PROTECTED]:
Le mercredi 27 juillet 2005 à 23:15 +0200, Arnt Karlsen a écrit :
On Wed, 27 Jul 2005 14:18:34 +0200, Gerard wrote in message
[EMAIL PROTECTED]:
I did NOT ask for deleting that piece of code which is
FGLGear.cpp line 507
Here's the code:
// Crash detection logic (really out-of-bounds detection)
if (compressLength 500.0 ||
vForce.Magnitude() 1.0 ||
vMoment.Magnitude() 50.0 ||
SinkRate 1.4666*30)
{
PutMessage(Crash
Le mercredi 27 juillet 2005 à 07:05 -0500, Jon Berndt a écrit :
FGLGear.cpp line 507
Here's the code:
// Crash detection logic (really out-of-bounds detection)
if (compressLength 500.0 ||
vForce.Magnitude() 1.0 ||
vMoment.Magnitude() 50.0
On Wed, 27 Jul 2005 14:18:34 +0200, Gerard wrote in message
[EMAIL PROTECTED]:
I did NOT ask for deleting that piece of code which is rather good
(and could be improved),
i only ask for to remove the new AGL test
^^
which delete the UNDERCARIAGE
Le mercredi 27 juillet 2005 à 23:15 +0200, Arnt Karlsen a écrit :
On Wed, 27 Jul 2005 14:18:34 +0200, Gerard wrote in message
[EMAIL PROTECTED]:
I did NOT ask for deleting that piece of code which is rather good
(and could be improved),
i only ask for to remove the new AGL test
...
This bug showed up about 10 days ago with an update from cvs. Any ideas
what is broken?
I've got a hunch. Dave Culp may have an idea. I'll take a look, too.
Sorry. I haven't been following the FG CVS logs.
Dave
___
Flightgear-devel
I don't know if there are others that use fgfs from front range
locations in Colorado, but I use it to practice instrument approaches in
this my home area and my two favorite aircraft for this are the c172p
and c310, both jsbsim models. _The yasim aircraft still work fine with
this