Gamepads with low polling rates have axes stuck

Expected behavior

Shifting quickly between opposite directions on an axis (up to down, left to right) should register the old axis direction as unpressed and the new axis direction as pressed.

Actual behavior

On slower polling controllers (like the SFC30 on Linux) the MelonJS engine sometimes does not catch an intermediary 0 state that unpresses the old axis direction before pressing the new axis direction.

Steps to replicate (should work with any controller)

• Hold one direction on an axis on the gamepad.
• Trigger a breakpoint at line 285 of src/input/gamepad.js (final line of binding axes iteration function)
• While breakpoint is stopping code, release direction and press opposite direction on same axis
• Resume code

If done correctly, the engine will report both directions as being pressed, with the only solution to release the axis back below the pressed threshold.

[parasyte]

Thanks for the report! Sorry it took so long for me to understand what you were experiencing.

[jdkendall]

You work fast, @parasyte ! Looks good to me, just tested it out and my gamepad is working flawlessly now. Thank you! 😃