I am using AAO and Stream Deck Mobile to create a Steam Deck Profile for the Cirrus SR22T in MSFS 2024. I've installed the AAO Stream Deck Plugin.

The issue I'm having is that there doesn't appear to be a variable to detect whether or not the Structural Deice switch has been pressed or not. The on and off actions of the Stream Deck button work to operate the switch, but the switch itself does not change on the Stream Deck. All the other switches I've created work fine.

Any ideas or suggestions?

1. Activate MSFS Developer Mode

2. Open "Tools->Behaviors"

3. Click back into the sim

4. Hover the mouse over the button/knob/lever that you are interested in and press "Ctrl - G"

5. Check the "Animation" part - this tells you what variable or code is controlling the animation of the component in the 3D model (which makes it visibly click up/down, turn etc.).

6. In this case you will see that the switch is moved by the variable "(L:XMLVAR_DEICE_MASTER, Bool)" => use that as the Read variable on the StreamDeck

This goes for the actuation of the component too - check out the "Mouserect" and "InputEvent" parts of the behavior code. The InputEvents can also be found in AAO, on the event selection dialog, tab "MSFS IEs". Please not that the IEs and their bindings, the BVars are only visible while you are actually connected to the sim and sitting in the cockpit - they are read from the sim at runtime.

Edited September 6Sep 6 by Lorby_SI

10 hours ago, Lorby_SI said:

1. Activate MSFS Developer Mode

2. Open "Tools->Behaviors"

3. Click back into the sim

4. Hover the mouse over the button/knob/lever that you are interested in and press "Ctrl - G"

5. Check the "Animation" part - this tells you what variable or code is controlling the animation of the component in the 3D model (which makes it visibly click up/down, turn etc.).

6. In this case you will see that the switch is moved by the variable "(L:XMLVAR_DEICE_MASTER, Bool)" => use that as the Read variable on the StreamDeck

This goes for the actuation of the component too - check out the "Mouserect" and "InputEvent" parts of the behavior code. The InputEvents can also be found in AAO, on the event selection dialog, tab "MSFS IEs". Please not that the IEs and their bindings, the BVars are only visible while you are actually connected to the sim and sitting in the cockpit - they are read from the sim at runtime.

Thank you. That worked. Microsoft sure doesn't make things easy.

1 hour ago, mkel2010 said:

Microsoft sure doesn't make things easy.

Not really their fault. Aircraft developers can and will use all options at their disposal. They should probably be using the SDK variables and events, but they don't have to. All that Microsoft/Asobo do is provide those options for creative solutions, in many cases for the better. The Ctrl-G thing is pure gold - no other simulator gave us access like this into the aircraft developers' brain.

Edited September 6Sep 6 by Lorby_SI