"BERNDT, JON S. (JON) (JSC-EX) (LM)" <[EMAIL PROTECTED]> said:
> > From: Michael Basler [mailto:[EMAIL PROTECTED]] > > > > Hi, > > > > I just received a problem report from a German user on the > > released version > > 0.7.9 which I - unfortunately - was able to confirm in part. > > > > 1. Start at CL77 Santa Cruz leads to an immediate crash. > > > > 2. He reported a crash at Munich EDDM at start (e010n40 > > installed) which I could not confirm. > > > > 3. However, Start at Innsbruck LOWI gave me an immediate crash, too. > > OK. Has the NTSB been called to the scene[s], yet? > > :-P > > Jon > Hope they disconnected the usb Flamethrower first :-) I'm getting the same thing with CL77. Some screwy looking airstrip. There still seems to be some problems with altitude between fg and jsbsim. A workaround is to add a --alititude=(runway elevation) to the command line. This perhaps is a naive question, but why aren't we kicking in the FDM after the plane is on the runway during initialization? It seems like there's a lot of trouble trying to get an FDM synced up with scenery/airport data during startup. Why is it that flightgear doesn't just put the plane where it goes and dictate the coordinates at startup (or reset) and let the flight model (re-)initialize with those values? It's pretty obvious that when there's a gross discrepency in elevation data (as with CL77) the FDM has kicked in and the plane is stalling and drifting down to the ground...hence the "crash". I guess a side question is to this is why don't the FDM's freeze the lat+long+alt when the parking brake is on and the ground speed is < 1? And keep it frozen until the brake is released. Seems like that'd be an easy way to stop the creeping that some people have complained about. Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
