HI,

I have a problem with using my Logitech Flight Quadrant with aao:

I've assigned an axis (the x-axis) to the AXIS_THROTTLE1_SET event, axis min -16384, axis max 16384, axis reversed, continuous update - I'm using this for more or less every aircraft I'm flying.

Now when I'm starting a flight (or change the aao profile) aao seems to set a value of 16384 to AXIS_THROTTLE1_SET, even if the lever is on the min position. When starting on the runway the aircraft has full power instead of idle power. A small adjustment of the throttle lever and everything work's as expected. But depending on the aircraft, full power may result in a problem. I'm using the same configs for some time now, I'm quite sure that some time ago this did not happen (but I'm not sure).

Any idea what could be the reason for this behaviour?

Thomas

2 hours ago, quambo said:

Any idea what could be the reason for this behaviour?

That is a known issue, that unfortunately cannot be helped. With the library that AAO is using, it is not possible to read the position of the levers (and buttons) from a controller that hasn't been used yet. It does query the controller, but all it gets back are generic values, not the actual positions - until you make at least one adjustment on any lever or push any button on the controller, then the app gets the correct values. I have tried many things to somehow get the correct data right away, but to no avail.

If you look closely, you can see the same effect in the Windows dialog where you configure USB game controllers. So this seems to be kind of by (Microsoft) design?

Edited September 27Sep 27 by Lorby_SI

Thank's for the answer - pushing any button on the controller is a helpful hint. Pushing a button is better that moving the lever at startup.

Could it be a workaround to have an option to set the initial value in an input field and then use this as long as the generic value has not changed? Maybe to complicated for the problem ...