Settable Avars and XMLTools C:SIMVARS

A 2D gauge that uses settable Avars (e.g., Fuel Tank Right Main Quantity, Payload Station Weight, etc) works with one aircraft, but not another. It seems the same Avars that are directly settable with the first a/c are not with the 2nd a/c for some reason.
If I use the XMLTOOLS C:SIMVARS functionality with the Avars all works as expected with the 2nd a/c. My understanding is C:SIMVARS will only write to Avars that are settable 'in the first place', so I don't understand why using C:SIMVARS works but using the Avars directly does not with the 2nd a/c (using P3dv4.4).
Thanks,
Al
 
Last edited:

Heretic

Resource contributor
Settable A: vars can only be manipulated via SimConnect when using a new class, which is exactly what XMLTOOLS' SIMVARS class provides. That the rest of the variables have human readable names is just a provision by Aces to make things easier. otherwise, you'd have to write to memory offsets, akin to FSUIPC.
 
I've now taken the approach that when it comes to writing to settable A:vars, to be safe I should use the XMLTools C:SIMVARS:vars approach.
However, why code like:
(M:Event) 'LeftSingle' scmp 0 == (A: PAYLOAD STATION WEIGHT:4, Pounds) 25 + (>A: PAYLOAD STATION WEIGHT:4, Pounds)
worked fine for setting the weight for all the Payload stations in one a/c will just have to remain a mystery, I guess.
Al
 

Heretic

Resource contributor
I've now taken the approach that when it comes to writing to settable A:vars, to be safe I should use the XMLTools C:SIMVARS:vars approach.
However, why code like:
(M:Event) 'LeftSingle' scmp 0 == (A: PAYLOAD STATION WEIGHT:4, Pounds) 25 + (>A: PAYLOAD STATION WEIGHT:4, Pounds)
worked fine for setting the weight for all the Payload stations in one a/c will just have to remain a mystery, I guess.
Could be P3Dv4 specific behavior or a custom module for the aircraft in question retaining the "A:" prefix for interaction with SimVars.
 
Top