Re: [Flightgear-devel] Autopilot bug?
Timo Saarinen wrote: Hi, I have tried the altitude and heading hold features of the autopilot (ctrl-A and ctrl-H with arrow keys or F11 autpilot dialog box). They work very well with j3cub aircraft but with the default cessna 172 either of them don't work at all. I suppose this is a bug. The particular autopilot included with the default C172 (KAP-140) must be operated by clicking on the panel buttons. Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Autopilot bug?
On Tuesday 05 April 2005 21:22, Curtis L. Olson wrote: Timo Saarinen wrote: Hi, I have tried the altitude and heading hold features of the autopilot (ctrl-A and ctrl-H with arrow keys or F11 autpilot dialog box). They work very well with j3cub aircraft but with the default cessna 172 either of them don't work at all. I suppose this is a bug. The particular autopilot included with the default C172 (KAP-140) must be operated by clicking on the panel buttons. Shouldn't the keyboard controls and the dialog be disabled then? Of course it would be nice to get some kind of message that you must operate the panel with mouse instead of the standard keyboard shortcuts. -Timo ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d