You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When HID devices (e.g. Winwing FCU) provide encoders, those are rendered as buttons. Those buttons have "on release", "on hold" and "on long release" bindings. Since those encoders do not send release events, "on hold" actions may cause unexpected behavior, including the MSFS2020 WSM binding crashing
Steps To Reproduce
Connect a HID device with encoders, e.g. a WinWing FCU
Assign an action to "on hold" on one of the encoders
Assign the same action to another input
In the sim, turn the encoder
Use the other input to execute that same action
Expected behavior
It is either not possible to assign "on hold" actions to encoders, or such actions are ignored
Actual behavior
The on hold action is apparently sent and never released, causing the WASM plugin to crash if a press from another source is received
Details
MobiFlight Version: 10.2.2.2
FlightSim: MSFS 2020
AddOn: Any plane, peripheral that acts as HID joystick with encoders supported by MobiFlight
Additional context
Found by accident (incomplete update of older MCC file) during development of VKB plugin. Later confirmed on WinWing FCU.
The text was updated successfully, but these errors were encountered:
Describe the bug
When HID devices (e.g. Winwing FCU) provide encoders, those are rendered as buttons. Those buttons have "on release", "on hold" and "on long release" bindings. Since those encoders do not send release events, "on hold" actions may cause unexpected behavior, including the MSFS2020 WSM binding crashing
Steps To Reproduce
Expected behavior
It is either not possible to assign "on hold" actions to encoders, or such actions are ignored
Actual behavior
The on hold action is apparently sent and never released, causing the WASM plugin to crash if a press from another source is received
Details
Additional context
Found by accident (incomplete update of older MCC file) during development of VKB plugin. Later confirmed on WinWing FCU.
The text was updated successfully, but these errors were encountered: