You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From w3c/gamepad#186:
The Quest Pro controller comes with a new VCM motor for haptics that has a variable frequency and intensity. The OpenXR API is documented here
We'd like to expose this to WebXR developers so they can generate more immersive haptics and would like to propose the following function to the GamepadHapticActuator IDL: Promise<GamepadHapticsResult> playPCM(audioBuffer);
From the feedback, it sounds like some people want a completely new interface but it doesn't match up with our workflow (ie it's based on touch events). How can we proceed? Should we continue to add to gamepadActuator that they want to deprecate?
/facetoface discuss support for a PCM buffer for gamepad actuator
The text was updated successfully, but these errors were encountered:
From w3c/gamepad#186:
The Quest Pro controller comes with a new VCM motor for haptics that has a variable frequency and intensity. The OpenXR API is documented here
We'd like to expose this to WebXR developers so they can generate more immersive haptics and would like to propose the following function to the GamepadHapticActuator IDL:
Promise<GamepadHapticsResult> playPCM(audioBuffer);
From the feedback, it sounds like some people want a completely new interface but it doesn't match up with our workflow (ie it's based on touch events). How can we proceed? Should we continue to add to gamepadActuator that they want to deprecate?
/facetoface discuss support for a PCM buffer for gamepad actuator
The text was updated successfully, but these errors were encountered: