Satie in WebXR
Keep the web integration and follow the headset’s camera and controllers during the immersive session.
Emulator tested; hardware validation pending
Read as Markdown1. Start with the web integration
Use the Three.js guide first, then ask the agent for satie_setup with topic set to xr. Load the audio before enabling Enter VR; call audio.start() synchronously from that button’s click before awaiting the XR session.
2. Follow the headset
Put the camera and controllers under the same rig. Bind the listener to the camera and update audio inside the XR animation loop.
Three.js · use the existing XR rig and render loop
renderer.xr.enabled = true;
audio.bindListener(camera);
renderer.setAnimationLoop(() => {
scene.updateMatrixWorld(true);
audio.update(camera);
renderer.render(scene, camera);
});- Bind controller grips or other sound-producing objects as hosts. Forward real input events using the names in the scene contract.
- Handle XR visibility changes so hidden sessions suspend audio and visible sessions resume it.
- The page’s mixer is outside the headset. Mix in the desktop view and test the result inside the session.
3. Test on the target headset
The starter has been exercised on an emulated Quest 3. Physical headset latency, Quest Browser, hand tracking and immersive AR have not been validated by that test. Measure the audio clock under load and lower the simultaneous loop budget if playback falls behind. For a native headset app, use its engine integration instead.
WebXR starter · Unity integrationSupport and validation
Quest 3 emulator starter; physical headset validation pending.
Uses the web integration and XR camera. The development mixer remains outside the headset. Measure audio under load on the target headset.
Not yet validated: Physical headset latency
Not yet validated: Quest Browser
Not yet validated: Hand tracking
Not yet validated: Immersive AR