I’ve read trough the topic and I am happy to see the ideas around this advance.
Please, take a look at his work, it might be inspiring and certainly helpful.
Hello @ll,
to get you started more quickly, here a few pointers:
Before you connect AAO to MSFS, go to “Scrpting->Read HVARs from sim” and let it collect all HTML variables and associated tags. Once collected, they will be accessible in the group “HTML-variables” in the assignment treelist. Repeat this process after each sim update or when you get new aircraft that were made to MSFS specs
With all sims, after the app is connected to the sim you can run “Scripting->Read LVARs from sim”. Th…
— also:
Hello @ll,
AAO version 2.01 has been released today.
The „endless“ setting for MIDI encoders has been fixed. When it is activated, it will make the app repeat the command that has been assigned to a control when it is at the stops (rotary with stops or a slider). For example, when you adjust the AP altitude, you could use a slider. This will work normally in the range that it can travel, and at the stops it will just continue counting up/down until you move it the other way again
SimConnect E…
— additional stuff also useful to me for my project:
Those are usually the generic ones, AS1000_x, AS3000_x. Search for PFD or MFD
A few words about these H Variables. They are not fixed literals, like a variable name. Instead, the simulator constructs the actual variable name at runtime from “building blocks” (calles “tags” in AAO).
In the MSFS model/animation XML code you will find things like this:
<CLOCKWISE_CODE>(>H:#KEY_PREFIX#_RANGE_INC)</CLOCKWISE_CODE>
<ANTICLOCKWISE_CODE>(>H:#KEY_PREFIX#_RANGE_DEC)</ANTICLOCKWISE_CODE
Dependin…
All the best,Milan Putnik mr.sci.eng.