sImWatcher what tech. to set variables?

That decision is up to you :wink: But it has been done, and discussed in several threads. This one includes links to the (at least) other two (large) threas about WASM + SimConnect + “client events”:

Note that - by nature - such a WASM module is most likely going to be aircraft specific, needs to be installed in the Community folder (of course) and the “client event IDs” that you have to define (in order to report back/receive to/from your client application) may collide with other such WASM modules - or so I understand (roughly).

Also, if the aircraft changes its “local variables” (L:vars) names you need to “keep up” and adapt your WASM module accordingly.

But all has been discussed in great detail in those threads.

1 Like