Hi,

I noticed while creating my AAO script for the stream deck, that the APU START button is controlled via the "AIRLINER_APU_START_Toggle" B-variable or the Input Event "AIRLINER_APU_START"

Problem is, the button is stuck in the on position and I can't find any other variable to release it except clicking on it with the mouse. Not a big issue but I had issues before where buttons are stuck and this created the wildest problems later on in the flight.

Maybe this is something you might consider to fix in a later patch.

Thanks.

EDIT: this also concerns the External Power switches and I guess all toggle-only buttons.

Edited September 16Sep 16 by Soho

2 hours ago, Soho said:

Hi,

I noticed while creating my AAO script for the stream deck, that the APU START button is controlled via the "AIRLINER_APU_START_Toggle" B-variable or the Input Event "AIRLINER_APU_START"

Problem is, the button is stuck in the on position and I can't find any other variable to release it except clicking on it with the mouse. Not a big issue but I had issues before where buttons are stuck and this created the wildest problems later on in the flight.

Maybe this is something you might consider to fix in a later patch.

Thanks.

EDIT: this also concerns the External Power switches and I guess all toggle-only buttons.

Hi,

I'm not entirely sure if this will help, but I've attached a forum thread for your viewing.

Thanks!

Hi Kyle,

thanks, haven't found the thread.

The problem is, as another user in that thread already stated, that the toggles are not returning to the 0 position if pressed.

But you can merge the posts if you like.

I have already posted this issue on Discord. It basically affects all relevant switches and controls. Toggle switches are not affected, but the issue occurs with all controls that can be pushed or pulled.

It is particularly annoying with the AP DISC button on the sidestick. As soon as the button is activated via external hardware, the button in the cockpit remains permanently stuck in the pressed position. After that, it cannot be activated again via the hardware because the cockpit button still appears to be pressed and does not return to its original position.

Only when the button is then pressed directly in the cockpit using the mouse does it correctly return to its original position after being pressed. Because of this, assigning these buttons to external hardware is currently practically impossible, which is really unfortunate.

In addition, I noticed another issue with the FCU (Autopilot Panel):

When I assign the SPD, HDG, ALT and VS rotary knobs via Axis and Ohs and, for example, turn one of them to the right (INC), the knob visibly rotates in the cockpit and the individual click sounds can also be heard.

However, when I turn the same knob to the left (DEC), the corresponding value on the display changes correctly, but there is no visible rotation of the knob and no click sounds can be heard.

So the function itself is executed correctly and the corresponding value changes, but with DEC both the visual knob animation and the audible feedback are completely missing.

Hi everyone,

Team is working on updating the LVAR's. Hoping it makes it into one of the upcoming patches/updates.

Thanks for your patience!