Re: [w3c/gamepad] Add device orientation support (Issue #211)

kvnloo left a comment (w3c/gamepad#211)

For gyro aiming, sampling frequency and timestamp semantics are probably as important as units.

Chromium's ordinary Gamepad path currently polls at ~250 Hz. If motion data joins that path, implementations should expose the sample timestamp rather than making applications assume it was sampled when `getGamepads()` ran.

That allows prediction/filtering based on actual sensor age, which matters directly for motion-to-photon latency.


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

Message ID: <w3c/gamepad/issues/211/5941897257@github.com>