want to switch all my configuration to AAO.
The only plane that gives me problems is the TBM with its particularity in terms of the throttle/propeller configuration.
Have you managed to make a configuration that works with LORBY AAO?

I had to use two levers for this, one for throttle, the other for props. Both must be moved in opposite directions, the prop lever must be fully up for the throttle to work and the throttle has to be all the way down for the prop to work. Reverse I have assigned to a button.

The events in use are these

PROP_PITCH_AXIS_SET_EX1
THROTTLE1_AXIS_SET_EX1

But I suppose that there must be a solution with BVars too.

Edited September 27, 20223 yr by Lorby_SI

I tried but does not work consistently.
I think my axis values are not correct.
Do you have a screenshot?

I am also interested in a solution for the Throttle and propeller configuration for the TBM. I have mapped throttle axis to Thrtottle_Axis_SET, and scaled it -16383 to 16383. The lever is not animated, but sends signal to change the torque. Right now I am using the mouse to work the propeller, as I can’t get it to work with axis assignments. I am using the latest AAO, and AAU beta. 

 

Thanks

1 hour ago, jayhawk81 said:

I am also interested in a solution for the Throttle and propeller configuration for the TBM. I have mapped throttle axis to Thrtottle_Axis_SET, and scaled it -16383 to 16383. The lever is not animated, but sends signal to change the torque. Right now I am using the mouse to work the propeller, as I can’t get it to work with axis assignments. I am using the latest AAO, and AAU beta. 

 

Thanks

I don't know if my solution is the correct one, but as I wrote above, I have assigned two separate levers to two separate events. With that I can control the thrust lever in the TBM by pulling one lever up while the other is fully down and vice versa. Technically the lever is controlled by BVars, so whatever we do here is always a work around. The behavior logic associated with this lever is quite complex, and I am still not sure that it can be replicated from the outside that well.

As you have observed, the 3D anmiation of things is not equivalent to the aircraft system being operated. Those don't have to be related at all. 

Edited January 3, 20233 yr by Lorby_SI

On 9/26/2022 at 1:06 AM, Lorby_SI said:

PROP_PITCH_AXIS_SET_EX1
THROTTLE1_AXIS_SET_EX1

is it possible to get Lvar from these events? I am trying to go the Bvar route. I looked in dev Mode and found the Bvars that I think I need.

Bvars
(B:ENGINE_Throttle)
(B:ENGINE_Throttle_Feathering)

 

Thanks
Ibra
 

8 hours ago, jayhawk81 said:

is it possible to get Lvar from these events?

You mean for the Mapping in AAO? Those LVars are invented, you can give them any name you want. LVars don't have to be configured or "defined" anywhere. In this case they only "live" between AAO and the mapping code, nothing else needs to know about them.
Also, be advised that using the AAO InGame Panel you can now utilize BVars directly in your RPN scripts, you don't have to create a mapping. There is a chapter about the InGame Panel in the AAO manual.

But you still have to solve the conflict between the two, since they both want to move the same simulated lever. So I imagine that you need a really complex scirpt (like the code in the behavior logic is) or two separate levers - and in that case you can just use the events listed above.

Edited January 5, 20233 yr by Lorby_SI