I was aware that certain turboprops had problems with the condition levers. And I read somewhere that with one of the latest updates of MSFS, these problems had been solved.

Unfortunately with the Analog King Air I bought lately, I can't get the condition levers to work with AAO.

When I map them in MSFS with CONDITION LEVER 1 AXIS, they work.

So I tried to find the event for them in AAO with "Watch Simulator Events".

I got this one when I moved the Honeycomb Condition Lever:

(K:AXIS_CONDITION_LEVER_1_SET)

So I set up an Axis Assignment in AAO "With Select Event:" AXIS_CONDITION_LEVER_1_SET

But the condition lever in the King Air doesn't move. Where is my thinking error ? Thanks for your help!

1. AAO has nothing whatsoever in common with the controller assignments in the sim. AAO is a "SDK Translator", nothing more - and the MSFS controller assignments live outside of that realm unfortunately. It would have been great if Asobo made sure that everything that you can assign in MSFS is also avaliable in the SimConnect API. But they didn't.

2. The events that you see are usually the result of the action, not the cause. It is entirely possible that the condition is set properly by doing this, even if the lever doesn't move (action and animation are two different things)

IIRC the visibile condition lever in the King Air is controlled by a BVar and needs a different approach. You have to either use the AAO InGame Panel and assign the BVar directly in the axis assignment or create a BVar to LVar mapping in AAO.

OK, I found it again.

1. Make sure that the AAO InGamePanel is active in MSFS. See AAO manual for instructions

2. For the condition levers, create an axis assignment like this:

• Enter Variable: B:FUEL_1_Condition_Lever_Set
• Axis min: 0
• Axis max: 2
• Rounding: Int

3. Use "B:FUEL_2_Condition_Lever_Set" for the second one, same settings (you can also bind both to the same phyiscal lever, AAO doesn't mind when you assign more than one thing to a controller)

Edited April 16, 20233 yr by Lorby_SI

Thank you very much, this worked !

I wasn't aware of the inGame Panel, because I hadn't downloaded the latest PDF...

Just one question, in the manual you write

"BVars usually don't have fixed names in the behavior code, so they cannot be found "offline". You
will have to use the Developer mode of MSFS to find out about these input events."

Can you tell me where in I can find these events, once I have activated Developer Mode ? I searched all menus but didn't succeed.

3 hours ago, Otto Groschenbügel said:

Can you tell me where in I can find these events, once I have activated Developer Mode ?

in one of the devmode menus there is "Behaviors" - open that dialog. Then click back into the sim window, position your mouse over a switch or lever in the cockpit and press Ctrl&G

With luck (maybe press that key combo a couple of times?), the dialog will jump to that components' code and you can browse through the behavior defintions - and find the BVar, LVar and HVar names in there. You can disregard O: and I:, we don't have access to those.

BVars usually work like this:
To read its value, you use (B:whatevername)
To write to the BVar you attach an ending that corresponds to the action:
2 (>B:whatevername_Set)
1 (>B:whatevername_Toggle)
1 (>B:whatevername_INC)
1 (>B:whatevername_DEC)

etc. this involves a fair bit of trial&error, unless you can localize it in the behavior code.

Edited April 17, 20233 yr by Lorby_SI

Ah, thanks for your help, its never too late to learn something new.