Jim Wilson writes: > >Norman Vine <[EMAIL PROTECTED]> said: > >> Whether we do this or leave it in mode[0] really doen't matter, but >> coming up with a 'white' screen after performing a reset from chase >> mode is unacceptable so something should be done before we make >> a release ! >> > >Actually the white screen was the wall of the cockpit, kind of like passing >out, falling on the floor (if there was room) and waking up looking at the >wall.
He He > It's been fixed in CVS. Great ! >While looking at this I wondered why there are two different routines, one for >reseting and one for teleporting. Seems as though they should do the same >thing. And at least making it one routine would reduce the battle against the >bugs down to one routine. My guess is that if 'teleporting' changed the 'airport-id' in the 'initial-conditions' this would work. Otherwise you need two routines or at least a wrapper routine. >I can't tell you exactly how to reproduce this, but >if you do enough teleports and resets the program will eventually crash...and >for some reason no core file. I have seen this too.. But I am not convinced yet that it is the teleporting that causes the crash. ie way back when I introduced teleporting it appeared to be 'bullet proof' note this was before even JSBSim was an FDM and the 'properties'. A lot has changed since then and I am not convinced that all of the additions since then know how to 'reinitialize' themselves or that we know what needs to be reinitialized. Cheers Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
