Native Input Mute fixes
A muted movement key could stay stuck down, which pinned the virtual stick to one side and stopped it responding. Fixed, along with three smaller faults in the same subsystem.
Highlights
- A muted key whose release was missed no longer stays stuck down, so strafing with muted WASD responds properly again.
- The mouse is only routed through OmniControl when you have actually selected a mouse input to mute.
- Muting the keyboard can no longer be delayed by mouse movement.
Fixes
- A muted key could be left asserted after you let go, pinning the virtual stick to one direction until you restarted.
- Native Input Mute could briefly stop and restart itself while you moved the mouse.
- Muting could switch itself off for a moment under load.
OmniControl 2.5.7 fixes a bug in Native Input Mute worth updating for if you use it with Drive a Controller.
If a muted key's release was missed, that key stayed marked as held. On a movement axis that is not a small problem: a permanently-held A contests every D, so the virtual stick pinned to one side and stopped responding to anything. Spamming A and D to strafe was the quickest way to hit it. Releases are now always recorded, and the safety net that clears a stuck key works for muted keys again instead of skipping them.
Three smaller faults in the same subsystem went with it. Native Input Mute could briefly stop and restart itself while you moved the mouse, which put a delay on the next keypress. It could also switch itself off for a moment when the app was busy. And the mouse is now only routed through OmniControl at all when you have actually selected a mouse input to mute, so a keyboard-only setup leaves your mouse completely alone.
Note
If you were on 2.5.6 and turned Native Input Mute off because strafing felt stuck, this is the release that fixes it.