1 hour ago, Lorby_SI said:

Go to Hardware->Device Blacklist and move everything into the list on the right with the "Ignore" button that isn't a game controller that you use with AAO. That includes all keyboards and mice. 
AAO is very keen on making all devices available that it can find. But there are some(many) that pretend to be a game controller but really aren't. And those can cause problems.

That would be highly aircraft dependant. What aircraft are you assigning this to? And with what kind of hardware? 

When using a button, the "classic" approach is using "THROTTLE1_DECR" with "Repeat" set to fast for the key down and "THROTTLE1_CUT" for key up. (and subsequent indexes for the other thrust levers)

In general there is no connection between aircraft systems and animations. It is prefectly possible to do one but not the other. So in your case one would have to analyze the behavior code how exactly the lever "ticks".

Especially with the throttles it is often important to use axis events, not variables. ("THROTTLEn_AXIS_SET_EX1" etc.)

I totally get it that different aircraft operate in different ways. I was just looking for general principles, and indeed if it at all possible to do in AAO. I have set up reversers, prop feather/reverse and condition cut out in msfs which seem to apply to multiple aircraft and animate the levers appropriately. The lever positions beyond the detente are buttons, the hardware is a Turtle Beach Velocty Flight Yoke and TQ.
Never mind if it can’t been done. Or if it can be done then I’ll never fly again but spend my time configuring! will just have to stick with hybrid profiles.

6 minutes ago, NigeUK23 said:

if it can’t been done

Just about everything can be done in AAO. It is just a question of how to do it. I've never seen a thrust lever not animate (except for the FBW A380), that's I why I was asking about the aircraft that you are trying to do this with. There is always something.

You cannot compare the controller logic in MSFS with what AAO is allowed to do through the SDK. Those are two unrelated and completely different "logics". Some names of inputs may sound similar in both, but they are not similar in any way.

Edited November 14, 20241 yr by Lorby_SI

Understood. By ‘can’t be done’ I really mean that the effort involved would be disproportionate to the result (cost to benefit analysis! 😜).
I already have what I need by using the msfs profiles, so the work involved in getting both the correct control for every aircraft I use and also the animation to go with it will be too much on top of configuring the stuff that is relatively straightforward.

I do see that AAO will be useful for more granular control over some aircraft functions, and I do like the saitek panel integration and the web stuff!

Thanks again for your input.

 

1 hour ago, NigeUK23 said:

straightforward.

This is the most "default" assignment for reversers to a button, and I have yet to see an aircraft where this doesn't trigger the animation as well.
Be mindful of the "Repeat Fast" setting.

This will deploy the reverser for as long as the button is pressed, and stow it when the button is released. You would typically use this on hardware TQs that have a "button-detent" at the bottom of the thrust lever range.
 

Edited November 14, 20241 yr by Lorby_SI

Perfect! That’s exactly what I needed!

 

Thank you