Currently, I am filtering then scrolling through the variables / Activities and selecting the ones that look the most likely.

I then put them in the script and click on test to see if the variable value changes when i click the switch etc in the sim  and re-test

I do the same with the events to see if the switch moves when i test it.

It is a very hit'n'miss approach, not to mention time consuming. After a while i will post something on a forum and hope I get a bite.

Is there a more efficient way of approaching it ?

What other methods do people try ?

Edited May 24, 20215 yr by Sybull
spelling mistake

4 hours ago, Sybull said:

What other methods do people try ?

If the plane is not of the "premium" variety, where the files are encrypted, my own method is to browse through the actual source code files of the aircraft. The only tool I need is Notepad++ and "Find in files". I start searching for the "thing" itself, a part of the real world name (or the label in the VC next to the button) that sounds like a programmer would use it as variable or parts name. "radio", "gear", "standby" or "stby" etc. I make NP++ search for those in the entire aircraft folder recursively, in all files called *.html, *.js and *.xml. Then I analyze all hits to find the part/button/dial that is in the VC. Then it is just a matter of threading my way through the various templates that are in use (again by searching the template name with "find in files", but this time in the entire MSFS Packages folder, because the template definition can be anywhere), until I can piece together the actual code that this control actuates. In many cases it is not just a single event or variable, but instead there is a sequence of commands that must be sent in the right order, to make the plane react the way that it would react to the button press in the VC. Tags like "LEFT_SINGLE_CLICK", "CLOCKWISE", "ANTICLOCKWISE" are the starting points.

Edited May 24, 20215 yr by Lorby_SI

Many thanks for that. Just the sort of tip i was looking for, 👍