Babylon.js WebXR interactions
Plans the transition between browser play and headset play. It connects XR controllers to existing actions and handles rejected entry, tracking interruptions and exit without stranding the player.
babylonjs-webxr-interaction
See how it helpsWhen is it useful?
Use when a Babylon.js experience should support headsets or XR controllers.
What does it help you do?
- Checks secure context and supported devices before defining entry behavior.
- Maps XR controls to shared game commands and preserves intended scale.
- Handles cancelled entry, disconnects and session cleanup while naming outstanding headset checks.
Try asking this
Add a VR visit mode to our puzzle museum. Map selecting an exhibit to both mouse and XR controller, cancel headset entry and disconnect a controller. Restore normal browser controls on exit and distinguish emulator checks from tests on a real headset.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Babylon.js — webxr interaction
Use when the requested Babylon experience includes WebXR sessions or XR controller interaction.
Version and project gate
Inspect package.json and lockfile, Babylon package family and exact version, engine creation, WebGL/WebGPU choice, canvas hosting, loaders, physics plugin version and asset ownership. Keep Babylon Lite and the full engine APIs distinct. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Check secure-context and device/session support before designing the flow. Define entering, leaving and failed XR transitions. Map controller/select intent to the same gameplay commands as non-XR input; preserve scale and comfort requirements and dispose session-owned features.
Deliver
An XR session/interaction contract plus a usable non-XR entry or explicit unsupported state. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A desktop browser preview does not prove headset support, tracking quality or comfort.
Acceptance scenario
Cancel session entry, disconnect a controller, leave XR and re-enter; identify physical-device checks still outstanding. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Ziva. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md