I started using AAO with just one of my hardware throttle controllers,  a GVL.
When I found that I could move the lever halfway through its travel before the assigned axis (vis AAO) in MsFS started to move, I assumed it was caused by it not having very good default calibration.  I tried calibrating it first via Window's "Devices & Printers" but it didn't alter the situation.

I've now started to assign my other hardware controllers via AAO as well, and I'm getting the same problem with my Honeycomb Bravo Throttle.

I've made sure that they're not mapped to two physical devices at the same time.  The triangles in AAO for trimming the ends of the movement and the centre point work fine where the physical hardware lever can't reach the ends of the slider in the AAO config, but not for when the lever can move the control over a longer range than it uses in the Sim.  (very had to describe this !)

I've compensated for the initial deadzone (the first half of the lever range), by altering the profile slope in AAO, but is there a better way to do it ?

Did you pull the red center triangle all the way to the side? That is usually required with Slider type axis.

Also, you can change the value range that is being sent from the assigned control by manipulating Axis Min and Axis Max. I assume that when you have an aircraft that only uses the "positive" part of a range, you can set Axis Min to 0 instead of -16383 

Thanks Lorby. ✅

Yes, I tried moving the red triangle to various positions, but that seemed to make  the controller's axis to the MsFS assignment's axis even less synchronised.  The half range deadspot was still there, and the remaining actual movement was less proportionate.

The two controllers that have shown this half range deadzone are my GVL throttle, which has a rotary action with hall effect sensors, and the other is a Honeycomb Bravo throttle with rotary levers, which I would assume are pots, rather than hall effect.

Your Axis min suggestion sounds as though that might be it, because of the lever only having any effect after the halfway point.

I guess that could be it taking up the minus value range before it gets to 0.

I'll give it a try and report back.

 

Perfect... 🙂

That's exactly what it was, thanks.

I changed the minimum value to 0 for the axis on the Bravo and GVL throttles, and now the hardware lever and software axis are exactly synchronsied in the 3d cockpit window, without needing to add a slope profile or adjust the triangles.

I'm really getting into it now, I'm able to leave all of my controllers plugged in that I use for various aircraft, and AAO's automatic assignment per aircraft type lets me hop from one to another without the delay  of having to go into MsFS's Control management. To be able to pick and mix various axis and devices as a succinct aircraft "set" is so much better than Asobo's clunky method.

✅✅