David Megginson writes: > I was testing some aero changes by flying in mouse mode (which is > easier than pulling out the yoke and clamping it onto my desk) when > something went wrong -- suddenly, the mouse would no longer control > the ailerons, though it still controlled the elevators. I was off > from the runway and heading for some forest, so I added power slowly > (to avoid yaw), overflew a small river, then did a soft-field landing > in some grass on the far side. > > This was a program bug (which I'll try to hunt down later), but it is > also a strong encouragement for us to start adding proper failure > modes to FlightGear. Instruments and radios do stop working, control > surfaces do jam, and engines do fail, though thankfully such events > (except for the first set) are extremely rare in real life.
I've never, ever seen this problem (and I'm not lying my butt off about this like some software vendors I currently have to deal with.) But if you observe this happening again, you might double check that you didn't inadvertantly activate the wing leveler or heading hold or waypoint follower ... that would be one non-bug explanation for what you describe. But to your other point, I agree that we should start looking into failure modes. This is one big un-addressed issue. I could make up a list of interesting failure modes if anyone was interested. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
