gamepad plugin has a noticible input delay #7921
Comments
|
On my system it only measures a 2ms difference in timing - much less than a single frame at 60 FPS (~16ms). However I think the design of the input handling may have added an extra frame of latency. I've adjusted the design and increased the polling rate for the next beta which should mean that gamepad input is processed as soon as possible. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
The gamepad plugin introduces a rather large input delay. In main.js I implemented the gamepadAPI to compare.
Attach a .c3p
gamepadTest.zip
Steps to reproduce
Observed result
there is an input delay caused by the gamepad plugin, in the console you can visually see the logging of the gamepad plugin lagging behind, additionally you can see a different time is logged
Expected result
The gamepad plugin is as fast as the gamepadAPI
More details
Affected browsers/platforms:
First affected release:
System details
View details
PASTE HERE
The text was updated successfully, but these errors were encountered: