Values of variables in the simulator

[spark smelt]

post a screenshot of the config you are using to set the values

[dark agate]

Some Lvars are used as controls and are changed to effect control changes, but some Lvars are used as output only. These Lvars are monitored and controlled by the internal processes of the simulator. These cannot be used for input.

The ATR aircraft is pretty well covered in Hubhop/Mobiflight. Did you get these variables from the Mobiflight presets?

this is what is listed in Hubhop for FGCP NAV and FGCP VNAV buttons:

Forgot there is yet another type of behavior. In some aircraft like the ATR in this case, you set the control Lvar to 1 and the sim returns it to 0 immediately. This is what is happening here, but note it is in both Lvars mentioned (I am looking at the ATR in the sim right now).

[dark agate]

There are other output Lvars in this aircraft.

I havent tested all of them, but I believe these are the FGCP mode indicator Lvars.

[undone gyro]

Here is the button configuration

I tested these variables, in fact I checked in the behaviors window if any other variable besides MSATR_FGCP_VNAV changes when I press the button. Unfortunately, as I described, it changes to 1 for a fraction of a second when the button is clicked and then returns to 0, even though the aircraft somehow knows that lnav is on or off, but I don't know how the aircraft has status information since the MSATR_FGCP_VNAV variable always returns to 0.

In the hubhop there is information about (L:MSATR_FGCP_STAT_VNAV, bool) with the description that it is responsible for the vnav indiscator, but when using variable 1 (>L:MSATR_FGCP_VNAV), MSATR_FGCP_STAT_VNAV remains at 0

The only way I have come up with is to create a press with a condition and set MSATR_FGCP_STAT_VNAV to a specific value. Let's say we are launching an aircraft, and vnav is disabled so MSATR_FGCP_STAT_VNAV is set to 0. I click the button and switch at the same time

1 (>L:MSATR_FGCP_VNAV)
1 (>L:MSATR_FGCP_STAT_VNAV)

and at the next press I check if MSATR_FGCP_STAT_VNAV) === 0 then 1 (>L:MSATR_FGCP_STAT_VNAV) else 0 (>L:MSATR_FGCP_STAT_VNAV)

I don't like this solution, but I don't have any other, and I'm afraid that during the flight some situation may occur that will disconnect my vnav and at that moment the vnav will not work but the indicator will still be set to 1.

The situation is strange in that, for example: MSATR_FGCP_NAV - (LNAV) is set to 1 (according to the hubhop and it worked like toogle) but there is also the variable MSATR_FGCP_STAT_NAV which, when switching the MSATR_FGCP_NAV variable, is set to value 4 (when enabled) or to value 0 (when disabled). I cannot understand why the same does not happen (automatically) for VNAV. Is this a bug that this aircraft has? And how, even though the value for VNAV always returns to 0, the aircraft knows it is on/off. Am I missing something?

[dark agate]

I am no expert in avionics, but I think that you probably need to have a flight plan registered in the CDU and be flying in order for STAT_VNAV to activate.

[undone gyro]

I have it set up. As a rule, I configure all these buttons when flying with a flight plan 😦

[dark agate]

I tested on the ground also, and pressing the onscreen VNAV button with the mouse does not activate VNAV either. So the behavior with the Lvar is consistent with the Sim.

[undone gyro]

I think I've found it (I didn't notice it before), when during the flight you set a specific altitude you want to reach and you click on the VNAV button, the plane starts IAS mode after a while and at the same moment another variable is modified which gets the value of 2 - (L:MSATR_FGCP_STAT_ALT) when the plane reaches the desired altitude the value of this variable returns to 1.