- From: Rik Cabanier <notifications@github.com>
- Date: Wed, 10 Dec 2025 22:42:00 -0800
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 11 December 2025 06:42:04 UTC
cabanier left a comment (w3c/gamepad#186) > We could explore adding another haptic effect type if it's common enough to warrant it and can be implemented in an interoperable manner across a range of gamepads. > > What are you thinking? That would be great! We could expose it as either a straight waveform as I proposed earlier or build something on top of the [haptic amplitude](https://www.internalfb.com/intern/staticdocs/internal_openxr_spec/#XR_FB_haptic_amplitude_envelope) OpenXR extension. I think either works for Quest although I suspect that Google would prefer the latter. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/186#issuecomment-3640470847 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/issues/186/3640470847@github.com>
Received on Thursday, 11 December 2025 06:42:04 UTC