Re: [Flightgear-devel] FDM freeze
Le mercredi 25 mai 2005 à 19:56 -0500, Dave Culp a écrit : > Lately I've been flying around German terrain and have been getting an FDM > freeze at seemingly random occasions after flying for ten minutes or so. > Here's a screenshot of the freeze: > >http://home.comcast.net/~davidculp2/fdm_freeze.jpg > > The user airplane is frozen, but other things keep running fine. The AI > aircraft keep going, as does the clock, frame rate, GUI, key bindings, mouse. > > It looks like just the FDM froze. Anyone else getting this? > > BTW, the HUD lat/lon *never* matches the "actual" lat/lon, so I don't think > that has anything to do with it. > > Dave > > ___ That happen often for me with message on the console: FGInterface is beeing called without scenery below the aircraf -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FDM freeze
> Lately I've been flying around German terrain and have been getting an FDM > freeze at seemingly random occasions after flying for ten minutes or so. > Here's a screenshot of the freeze: > >http://home.comcast.net/~davidculp2/fdm_freeze.jpg > > The user airplane is frozen, but other things keep running fine. The AI > aircraft keep going, as does the clock, frame rate, GUI, key bindings, mouse. > It looks like just the FDM froze. Anyone else getting this? Any correspondence with a single FDM? If it's JSBSim you might see if data is being logged first. Maybe there's a limit being reached. Otherwise, maybe the data log would shed some light on what is happening. The plane flies along just fine? Then, jsut freezes? Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FDM freeze
> That happen often for me with message on the console: > >FGInterface is beeing called without scenery below the aircraf What logging level did you use? --log-level=? Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FDM freeze
I tried log-level=info and flew around Sembach until it happened again. Here's some console output: ... prepare_ground_cache(): ac radius = 11.7738, # leafs = 0, ground_radius = 0 prepare_ground_cache(): trying to build cache without any scenery below the aircraft FGInterface is beeing called without scenery below the aircraft! Updating Sun position Gst = 19.2257 t->cur_time = 1043061518 Sun Geodetic lat = -0.351757 Geocentric lat = -0.34959 sun angle relative to current location = 1.21658 Updating Moon position t->cur_time = 1043061518 Moon Geodetic lat = 0.307437 Geocentric lat = 0.305505 moon angle relative to current location = 1.86307 Updating light parameters. Sun angle = 69.7049 ambient = 0.2 diffuse = 0.977531 specular = 0.5 sky = 0.962797 prepare_ground_cache(): ac radius = 23.2997, # leafs = 0, ground_radius = 0 prepare_ground_cache(): trying to build cache without any scenery below the aircraft FGInterface is beeing called without scenery below the aircraft! ... I've heard others talk of this problem, but this is the first time I've seen it myself. Could it be the European terrain data resolution versus U.S. terrain data resolution? Anyway, it would seem that a fix would be to keep a copy of the last tile info, and if no tile is found on the next update then the last one can be used until a new one appears. Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FDM freeze
> prepare_ground_cache(): ac radius = 11.7738, # leafs = 0, ground_radius = 0 > prepare_ground_cache(): trying to build cache without any scenery below the > aircraft > FGInterface is beeing called without scenery below the aircraft! The last line comes from JSBSim.cxx line 425, inside the function FGJSBsim::update(). If there is a ground cache problem then the function returns without ever calling copy_to_JSBsim() or copy_from_JSBsim(). That would explain the freeze. Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FDM freeze
Dave Culp wrote: > Lately I've been flying around German terrain and have been getting an FDM > freeze at seemingly random occasions after flying for ten minutes or so. > Here's a screenshot of the freeze: > >http://home.comcast.net/~davidculp2/fdm_freeze.jpg You should not do these manouvres with such an old aircraft ;-) I _might_ know a similar szenario. I thought I'd post a description last week but I held it back - until now. The effect _I_ see is that the FDM does _not_ feeze _immediately_ but instead it slows down at a very high rate and I get at least one or two more "state changes". I'm able to reproduce the effect under the following circumstances: 1.) Choose the A-10fl, 2.) take off at EKOD, 3.) switch to some outside view, 4.) activate the autopilot to altitude-hold and select 800 ft, 5.) put EKSB as the first item on the list of waypoints, 6.) put EDXF as the second item on the list of waypoints. The aircraft heads towards EKSB at a constant altitude of approx. 950 (!?!?) ft. After arriving overhead EKSB the aircraft _should_ turn right to head for EDXF. The last picture I see is in the moment of having the aircraft right overhead EKSB, then I encounter a delay of about 15 sec. and the next frame I get shows the aircraft in the mid of the turn towards EDXF. With a bit of luck I get another frame about 20 sec. later. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FDM freeze
On Thu, 26 May 2005 11:37:13 + (UTC), Martin wrote in message <[EMAIL PROTECTED]>: > Dave Culp wrote: > > Lately I've been flying around German terrain and have been getting > > an FDM freeze at seemingly random occasions after flying for ten > > minutes or so. Here's a screenshot of the freeze: > > > >http://home.comcast.net/~davidculp2/fdm_freeze.jpg > > You should not do these manouvres with such an old aircraft ;-) > > I _might_ know a similar szenario. I thought I'd post a description > last week but I held it back - until now. The effect _I_ see is that > the FDM does _not_ feeze _immediately_ but instead it slows down at a > very high rate and I get at least one or two more "state changes". > > I'm able to reproduce the effect under the following circumstances: > > 1.) Choose the A-10fl, > 2.) take off at EKOD, > 3.) switch to some outside view, > 4.) activate the autopilot to altitude-hold and select 800 ft, > 5.) put EKSB as the first item on the list of waypoints, > 6.) put EDXF as the second item on the list of waypoints. > > The aircraft heads towards EKSB at a constant altitude of approx. > 950 (!?!?) ft. After arriving overhead EKSB the aircraft _should_ turn > right to head for EDXF. The last picture I see is in the moment of > having the aircraft right overhead EKSB, then I encounter a delay of > about 15 sec. and the next frame I get shows the aircraft in the mid > of the turn towards EDXF. With a bit of luck I get another frame about > 20 sec. later. ..what happens if you slow the simulation by 15-20 times the clock time? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FDM freeze
Arnt Karlsen wrote: > ..what happens if you slow the simulation by 15-20 times the clock time? Slowing down might not be reasonable as I'm currently getting frame rates in the 15-20 fps region Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FDM freeze
On Thu, 26 May 2005 12:55:38 + (UTC), Martin wrote in message <[EMAIL PROTECTED]>: > Arnt Karlsen wrote: > > > ..what happens if you slow the simulation by 15-20 times the clock > > time? > > Slowing down might not be reasonable as I'm currently getting frame > rates in the 15-20 fps region ..agreed, is only usable for diagnosis work, and moviemaking on old slow irons. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FDM freeze
Dave Culp wrote: > Lately I've been flying around German terrain and have been getting > an FDM freeze at seemingly random occasions after flying for ten > minutes or so. My guess is this is a "crash" due to weird collision detection in the ground or gear code. The last I checked, JSBSim and YASim had the same silently-freeze-on-crash behavior. We should probably come up with some kind of standard way for the FDM to signal to the rest of the simulator that it has detected a collision and stopped. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FDM freeze
Le jeudi 26 mai 2005 à 09:15 -0700, Andy Ross a écrit : > Dave Culp wrote: > > Lately I've been flying around German terrain and have been getting > > an FDM freeze at seemingly random occasions after flying for ten > > minutes or so. > > My guess is this is a "crash" due to weird collision detection in the > ground or gear code. The last I checked, JSBSim and YASim had the > same silently-freeze-on-crash behavior. We should probably come up > with some kind of standard way for the FDM to signal to the rest of > the simulator that it has detected a collision and stopped. > > Andy > don't forget the message error : FGInterface is beeing called without scenery below the aircraft Which not the case with a crash. > -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
