Skip to content

Add support for a PCM buffer to the gamepad actuator #58

Open
@cabanier

Description

@cabanier

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions