fixed Device/LUA commands for Left/Right engine cut-off valves broken

[Havner]

Left/right engine cut-off valves are device.ENGINE_INTERFACE (4) buttons 3009 and 3010 respectively. Values 0.0 and 1.0.

And they kinda seem to work. If you only use mouse or bindable keys you won't see the bug.

The problem is that setting those lever to a specific value doesn't work the way it works for any other switch in Ka-50 and any other DCS module. Usually setting something to value 1 (or some other ON value) turns it on (and respective presses leave it on), setting it to 0 turns it off (and respective presses leave it off).

Here, doesn't matter what value we set, the lever is always toggled. So set it to 1, it turns on, set it to 1 again and it turns off. Funny thing is, that values 0 and 1 properly set mouse clickable points (setting to 0 always leaves the clickable point down, setting to 1 always set it up).

I do realize that this might not be treated as a bug because it cannot be reproduced without external software/hardware, but such things are crucial for cockpit builders, stream deck profiles and advanced switch bindings for switches that hold state. I've been doing such things for a long time and those levers/switches are the only ones that have this problem (and AFAIR it's there since DCS: Ka-50 1.0 standalone when I've been doing old TM profiles).

Please, don't disregard it because of that.

Run this code (on a cold plane), it will cause the levers to move up and down immediately, but it will leave the clickable mouse spots up. Clearly showing the bug.

It should result in both levers being up and stay there.

Quote

lDevice = GetDevice(4)
lDevice:performClickableAction(3009,1)
lDevice:performClickableAction(3009,1)
lDevice:performClickableAction(3010,1)
lDevice:performClickableAction(3010,1)

 

EDIT: There is a way to show this bug without any external help:

• get a hot plane
• turn off one of the cut-off levers (move it down with a click)
• run autostop sequence (LWIN + HOME)

At the end you'll end up with the lever you moved down being in up position (despite the fact that Macro_sequencies.lua set it to 0) with a broken mouse click spot.

Edited April 13, 2022 by Havner

[Flappie]

Reproduced and reported.