Re: [Flightgear-devel] Re: Problems with todays CVS
Le lundi 30 mai 2005 à 21:45 +0200, Gerard ROBIN a écrit : > Le lundi 30 mai 2005 à 12:34 -0500, Dave Culp a écrit : > > > >> Only JSBSim doesn't. :-( > > > > > cout << "altitude = " << alt << endl; > > cout << "sea level radius = " << slr << endl; > > cout << "latitude = " << lat << endl; > > cout << "longitude= " << lon << endl; > > //return; > > } > > > > > > I know it works fine in the air (I've been using it for a couple days while > > trying to recreate the error conditions), but what happens if you get a bad > > cache on the ground? Don't know. > > > > Dave > > > may be an other way for research: > > I have build CVS with the JSBSim 9.8 source , > FGFS gives the same "Freeze" with the well known message: > > FGInterface is beeing called without scenery below the aircraft. > > So , Is it really a JSBSim bug??? I would like to be more clear regarding my previous mail: I did build the existing CVS, after patching it with the ==>JSBSim version which is in the stable flightgear-9.8 the resulting fgfs presents exactly -->the same "Freeze" -->the same message error "FGInterface is beeing called without scenery below the aircraft". We could conclude: the error is not in JSBSim but in an other part of fg -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Problems with todays CVS
Le lundi 30 mai 2005 à 12:34 -0500, Dave Culp a écrit : > > >> Only JSBSim doesn't. :-( > > cout << "altitude = " << alt << endl; > cout << "sea level radius = " << slr << endl; > cout << "latitude = " << lat << endl; > cout << "longitude= " << lon << endl; > //return; > } > > > I know it works fine in the air (I've been using it for a couple days while > trying to recreate the error conditions), but what happens if you get a bad > cache on the ground? Don't know. > > Dave > may be an other way for research: I have build CVS with the JSBSim 9.8 source , FGFS gives the same "Freeze" with the well known message: FGInterface is beeing called without scenery below the aircraft. So , Is it really a JSBSim bug??? -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Problems with todays CVS
> >> Only JSBSim doesn't. :-(
While we're finding out the cause and fixing the ground cache thing, how about
making a small modification to JSBSim.cxx that will spit out useful data and
*not* freeze the FDM? (about line 409)
// Compute the potential movement of this aircraft and query for the
// ground in this area.
double groundCacheRadius = acrad + 2*dt*Propagate->GetUVW().Magnitude();
double alt, slr, lat, lon;
FGColumnVector3 cart = Auxiliary->GetLocationVRP();
if ( needTrim && startup_trim->getBoolValue() ) {
alt = fgic->GetAltitudeFtIC();
slr = fgic->GetSeaLevelRadiusFtIC();
lat = fgic->GetLatitudeDegIC() * SGD_DEGREES_TO_RADIANS;
lon = fgic->GetLongitudeDegIC() * SGD_DEGREES_TO_RADIANS;
cart = FGLocation(lon, lat, alt+slr);
}
double cart_pos[3] = { cart(1), cart(2), cart(3) };
bool cache_ok = prepare_ground_cache_ft( State->Getsim_time(), cart_pos,
groundCacheRadius );
if (!cache_ok) {
SG_LOG(SG_FLIGHT, SG_WARN,
"FGInterface is being called without scenery below the aircraft!
\n");
cout << "altitude = " << alt << endl;
cout << "sea level radius = " << slr << endl;
cout << "latitude = " << lat << endl;
cout << "longitude= " << lon << endl;
//return;
}
I know it works fine in the air (I've been using it for a couple days while
trying to recreate the error conditions), but what happens if you get a bad
cache on the ground? Don't know.
Dave
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Problems with todays CVS
Jon Berndt wrote: * Erik Hofman -- Monday 30 May 2005 18:22: I don't get it, I didn't see this behavior until after I committed the patches, when I noticed it once. Melchior has these patches also applied and didn't complain. And I first saw it when I tried to reproduce Jon's problem. Which "worked". Seems like I do really somehow prefer YASim, at least always if I try to test stuff. (The bo105 may have to do with it.) YASim works. Only JSBSim doesn't. :-( Only the **C-172** doesn't? Or, any JSBSim aircraft? I've seen it with the F-16. But not directly, it took some time. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Problems with todays CVS
* Jon Berndt -- Monday 30 May 2005 19:12: > You suspect the new ground callback code? Yes, that's a safe bet. The clouds can hardly do that, neither can my modified beacon. There were no other commits. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Problems with todays CVS
Jon Berndt wrote: * Erik Hofman -- Monday 30 May 2005 18:22: I don't get it, I didn't see this behavior until after I committed the patches, when I noticed it once. Melchior has these patches also applied and didn't complain. And I first saw it when I tried to reproduce Jon's problem. Which "worked". Seems like I do really somehow prefer YASim, at least always if I try to test stuff. (The bo105 may have to do with it.) YASim works. Only JSBSim doesn't. :-( Only the **C-172** doesn't? Or, any JSBSim aircraft? Same problem with the F-18 Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Problems with todays CVS
> > Only the **C-172** doesn't? Or, any JSBSim aircraft? > > I tried several aircraft: all YASim worked. None of the JSBSim aircraft did. > But I wouldn't worry about it. Give Mathias a few hours time. That's probably > not hard to fix. (And enjoy the bo105 in the meantime! :-) > > m. You suspect the new ground callback code? Well, I'm in no hurry. It's a holiday. I'm taking the family to see "Madagascar". With four small kids. At their normal nap time. Ought to be interesting. Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Problems with todays CVS
* Jon Berndt -- Monday 30 May 2005 18:53: * * Melchior FRANZ: > > And I first saw it when I tried to reproduce Jon's problem. Which "worked". > > Seems like I do really somehow prefer YASim, at least always if I try to > > test stuff. (The bo105 may have to do with it.) YASim works. Only JSBSim > > doesn't. :-( > > Only the **C-172** doesn't? Or, any JSBSim aircraft? I tried several aircraft: all YASim worked. None of the JSBSim aircraft did. But I wouldn't worry about it. Give Mathias a few hours time. That's probably not hard to fix. (And enjoy the bo105 in the meantime! :-) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Problems with todays CVS
> * Erik Hofman -- Monday 30 May 2005 18:22: > > I don't get it, I didn't see this behavior until after I committed the > > patches, when I noticed it once. Melchior has these patches also applied > > and didn't complain. > > And I first saw it when I tried to reproduce Jon's problem. Which "worked". > Seems like I do really somehow prefer YASim, at least always if I try to > test stuff. (The bo105 may have to do with it.) YASim works. Only JSBSim > doesn't. :-( Only the **C-172** doesn't? Or, any JSBSim aircraft? Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Problems with todays CVS
* Erik Hofman -- Monday 30 May 2005 18:22: > I don't get it, I didn't see this behavior until after I committed the > patches, when I noticed it once. Melchior has these patches also applied > and didn't complain. And I first saw it when I tried to reproduce Jon's problem. Which "worked". Seems like I do really somehow prefer YASim, at least always if I try to test stuff. (The bo105 may have to do with it.) YASim works. Only JSBSim doesn't. :-( m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
