JJBZ0053

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?

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.

In place of "Planned obsolescence" I would submit "Accidental Aggravation" Their support of legacy models has be uneven although SU1 Beta helps more than it hurts.

My observations (testing some but not all aircraft, so might not be universal) In 2020 Sim, AAO mapped IE: events working for aircraft I have tested In 2024 Sim, IE: working for native 2024 aircraft but not for legacy (2020) aircraft. Events are listed in AAO window but have no action when used Is this something that Asobo is blocking? Obviously events have changed in the new sim. I see new file events.xml in native builds. Just thought I would mention in case you saw any chance of improvement in next version... Because I know a lot of users are trying to use their purchased 2020 aircraft in 2024. And using IE: seems a quick way to build control map when working well. Also I have not yet found a page explaining how Asobo compiler comes up with IE: event names.

Thanks. Not critical. I can wait.

Is there a solution for AAO to access to FS2024 Scoped variables from AAO Observe Variables or scripts? I saw your discussion in devsupport.