When watching simconnect events on default airplanes without WASM, all the events mapped from the sim controls page or the external AAO mapping buttons are shown. But on some creator airplanes like Arrow, not all control-generated events appear in the Events window.  My theory is these particular events are taken over by WASM code, replaced, and rendered invisible to both the AAO window and Sim core.

1. Do you know if this is likely explanation for the disappearing events?

2. If simconnect event types and data can be modified by WASM, does the sim, or AAO, make sure that the AAO listener always sees the changes made by WASM - the AAO is at the end of the event client list after WASM?

Thanks again for AAO.  I use the debug windows for hours almost every day to see inside the sim.

 

50 minutes ago, JJBZ53 said:

When watching simconnect events on default airplanes without WASM, all the events mapped from the sim controls page or the external AAO mapping buttons are shown. But on some creator airplanes like Arrow, not all control-generated events appear in the Events window.  My theory is these particular events are taken over by WASM code, replaced, and rendered invisible to both the AAO window and Sim core.

1. Do you know if this is likely explanation for the disappearing events?

2. If simconnect event types and data can be modified by WASM, does the sim, or AAO, make sure that the AAO listener always sees the changes made by WASM - the AAO is at the end of the event client list after WASM?

Thanks again for AAO.  I use the debug windows for hours almost every day to see inside the sim.

 

1. and 2. No. that is not how this works.

1. The default K: events from the SDK (that is what you see on the observer) may be a result of a button press. But they are in 99% of all cases not the direct cause.
2. Cockpit controls in MSFS are actuated with the mouse. Period.
3. That being said, what you can do is to replicate the RPN code that is triggered by a mouse click, drag or mousewheel action. If you are lucky, those are simple BVars or HVars, and sometimes even the odd K-Event. And occasionally you will come across LVars, if the developer makes it so. But LVars need a bit of logic around them, since they are just variables, not events. They have a value, they don't "cause" anything.
4. This has nothing whatsoever to do with WASM. 
5. What AAO is doing has nothing whatsoever in common with what the simulator does with its own controls assignments. Those are completely different and unrelated "logics", even if some of the terminology they use looks similar.

What you are looking for is the behavior code. In MSFS developer mode, open the dialog "Tools->Behaviors". Then click back in the sim, and then hover your mouse over the button, knob or lever that you wish to investigate. Press Ctrl - G. Now the behavior code will show up in the dialog, and somewhere in there you will find the controlling assets, be it BVars, HVars, LVars, K-events or entire scripts. First to check are the components around the mouse control (MouseRect). There are usually some where you can take a look at the mouse code directly and see what a "left single", "drag" etc. do. And that is what you replicate in AAO.

By and large the event observer is useless in MSFS. The aircraft developers are simply not using the default events anymore. None of the BVars, HVars and LVars can be observed that way.

Edited August 2, 20232 yr by Lorby_SI