Re: [w3c/gamepad] Arbitrary buffering of API calls is causing issues (#46)

> Is the 8ms polling interval for the Xbox controllers documented somewhere? That might make a more compelling case.

I can't find any official documentation for it. I've observed an 8 ms refresh rate when testing both Xbox 360 and Xbox One controllers with the default USB drivers on Windows 10 and Ubuntu. Microsoft may change it by updating the driver in the future. The default polling rate for most USB input devices seems to be 8ms since it works with older USB hardware revisions.

> I'm not really sure how we solve this with XInput, to be honest, since it doesn't provide a notification API.

I agree that there is no optimal solution with XInput. Applications using XInput must poll the API at an even higher rate than the driver poll rate to get even remotely accurate timing. The only power-friendly solution I can think of is to adaptively increase the XInput polling rate when the Gamepad API is frequently called.

> In Chrome at least, it is unlikely that code would be accepted that requires increasing the timer frequency above the default 16ms due to concerns about battery.

Those timers shouldn't be firing at a high rate unless you have a gamepad connected and pressed a button on it. Seems like a low risk for mobile devices.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/46#issuecomment-258375592