I am using a throttle quadrant that employs an 8 turn potentiometer for fine movement. Unfortunately, the very slow movement of the axis cursor does not trigger an axis detection in Axis and Oh's. Is there a method for manually entering the specific axis in A&O? Thank you.

Are you quite certain that AAO can see input from that controller at all? The speed of the axis values changing should not matter.

If the controller is generally working and you can assign at least "something", you can try and enter the axis manually in the config xml file (=you would create an axis assignmet but for a different controller, then overwrite the GUID in the file manually AppData\Local\LORBY_SI\LorbyAxisAndOhsMSFS\ConfigDatabase_MSFS.xml).

 

Edited June 18, 20232 yr by Lorby_SI

AAO sees the controller and has no trouble with normal axis; it does not see this particula axis due to its very granular movement. I was hoping to having to avoid manual cfg edits.

Thank you.

1 hour ago, flyforever said:

it does not see this particula axis due to its very granular movement.

Try to keep the control away from the center point, more towards the edges. AAO has a fairly large deadzone in pickup mode and will not detect the movement when it happens inside +/- 15%  around the (theoretical or real) center. 

Also, try to isolate the device with the little lock symbol, using a different axis, one that it can pick up. When the device has been islolated, it goes into "high sensitivity" mode.

If that fails, I suggest that you send an email with your proof of purchase to the support address (last page of the manual) with details about that controller. Is that control really acting like an axis? Could it be sending button events instead? What does it look like in the Windows USB Game Controller dialog, does it register there, and as what kind of asset? 

Edited June 18, 20232 yr by Lorby_SI

This is a custom made quadrant. Many have been sold around the world. In Windows it registers as a USB game controller. The trim wheel is configured as the Y axis in the firmware. MSFS control option occasionally picks it up if I spin the wheel very fast. MSFS control option has the input name option, so it's not an issue. As I move all controls from MSFS to A&O, I run into this small issue. It's not a problem because the trim wheel axis never changes for all aircrafts, so I can keep it in MSFS while all other axis are moved to A&O. It's something you may want to keep in mind for future versions.

So isolating the device did not work?

If Windows / Direct Input will not transmit the axis (or only occasionally) then AAO will not fare any better. It depends on DirectInput.

"keep in mind" - I would need the actual hardware for assessment. I don't think doing this "in the blind" would be possible.