Assuming a switch or control not found in the simconnect standard list:

For native MS2024 aircraft the best approach seems to be mapping IE: events. And AAO finds the IE: names.  
It is not explicit but is clear AAO maps to the EventName_Set binding. This is perfect for a toggle switch.  And indeed works fine for switches.

But I have seen some controls that would be better served by mapping to EventName_Inc or _Dec. Example is a rotary knob.

Currently I have to write a complex script to calculate the new value for the _Set.
I wonder if it is possible to have the script parser see the override of the added _Inc.

Clearly if all of the possible bindings were listed in the selection list, the list would grow much larger.  Maybe need a "show all variations" check box? 

Using the built-in behaviors developer tool I have confirmed that the template the creator used implemented the _Set, _Inc, and _Dec. It seems that Asobo is pretty consistent about this.  

3 hours ago, JJBZ0053 said:

Assuming a switch or control not found in the simconnect standard list:

For native MS2024 aircraft the best approach seems to be mapping IE: events. And AAO finds the IE: names.  
It is not explicit but is clear AAO maps to the EventName_Set binding. This is perfect for a toggle switch.  And indeed works fine for switches.

But I have seen some controls that would be better served by mapping to EventName_Inc or _Dec. Example is a rotary knob.

Currently I have to write a complex script to calculate the new value for the _Set.
I wonder if it is possible to have the script parser see the override of the added _Inc.

Clearly if all of the possible bindings were listed in the selection list, the list would grow much larger.  Maybe need a "show all variations" check box? 

Using the built-in behaviors developer tool I have confirmed that the template the creator used implemented the _Set, _Inc, and _Dec. It seems that Asobo is pretty consistent about this.  

_Inc and _Dec are not an "override", they are the bindings of the IE:, the "BVars". You can access those in AAO too.

• (B:inputeventname) is for reading the value
• (>B:inputeventname_Set) (>B:inputeventname_Toggle) (>B:inputeventname_Dec) (>B:inputeventname_Inc), etc.  are for writing (there are many more, the developers can just invent them - it is not possible to show them in the AAO list, because the app has no way of determining their existence - not from encrypted behavior files anyway)

BVars are also in the AAO selection list for the IEs (Tab "MSFS IEs" on the standard event selection dialog). You can open an IE entry in the selection list, and find the most common BVars as sub-elements of the IE that you can also doubleclick. With the SEL/MAN switch on the button assignment dialog you can also enter BVars manually. Assuming that you are using the latest AAO version. 

You can always type any item into a script at any time. AAO doesn't have to know about it in its database to use it. Those lists are just for convenience.

Warning: BVars are currently not working in the MSFS 2024 Beta. Or rather they were broken a couple of weeks ago, I haven't checked back with the Beta since then.

Edited September 27, 2025Sep 27 by Lorby_SI

You're right of course - the expand-list triangle was there where you said.

I have been in the habit of double clicking one line too soon and ignoring the available drop down. 

Is double click on the line ending with the (>IE:2:) useful in some circumstances? 

Or maybe the double click should open the expanded list?

 

btw. in many cases the behavior of an IE can be controlled with the value that you are sending. Inc/Dec are sometimes mapped to -1 / 1 or 0 / 1. But there is no rule that it has to be this way.

6 minutes ago, JJBZ0053 said:

You're right of course - the expand-list triangle was there where you said.

I have been in the habit of double clicking one line too soon and ignoring the available drop down. 

Is double click on the line ending with the (>IE:2:) useful in some circumstances? 

Or maybe the double click should open the expanded list?

 

You need both options, selecting the IE and selecting the BVars. And remember that you can just type in the BVar into the Button assignment manually, using the SEL/MAN slider. The BVars in the list are just the most common ones - you have no guarantee that they will work or that there aren't others too. You will have to check the behavior code for that.

Quote

Is double click on the line ending with the (>IE:2:) useful in some circumstances? 

Using the IE directly is the preferred method, the BVars are more of a detour. Which did go wrong in the MSFS 24 Beta, so "beware".

Btw. the list of IEs are read at runtime from SimConnect. The :2 means that SimConnect is telling AAO that this IE requires two parameters... Not sure why that is the case with so many IEs now or why they work with just one. Or if we are supposed to supply two. There are no further instructions in the SDK documentation that I can see.

Edited September 27, 2025Sep 27 by Lorby_SI