Setup your Quest, Vision Pro, Index, or any WebXR headset to play wilds.ai. Controls, comfort settings, and what to do when the Enter VR button doesn't show up.
8 min read•
Most wilds.ai worlds are VR-playable from any WebXR-capable browser. No app to install, no SDK to download — open wilds.ai in your headset's browser, sign in, click a world, hit Enter VR. You're in. (Some creators opt their worlds out of VR; those still play flat. See Creator opt-out below.)
This guide walks the setup for each major headset, the controls, the comfort settings, and what to do when something doesn't work.
Input: No controllers — gaze + pinch only. The ray cursor follows your gaze; pinch to confirm. Wrist menu is summoned by turning your left palm down.
Hand tracking: First-class. Gameplay that requires fast button presses (realtime-3d combat) may feel awkward without controllers; choose narrative/cinema-mode worlds for the best Vision Pro experience.
Active in any mode but optimized for cinema + narrative. The wrist menu summons when you turn your left palm down. Pinch to confirm any selection. The ray cursor follows your gaze.
The platform defaults are tuned for the median player. If you get motion-sick or want a more immersive experience, your per-persona XR defaults override per-blueprint settings:
Locomotion — Teleport (default, most comfortable) / Smooth (more immersive, higher sickness risk) / Auto (both, pick from wrist menu)
Vignette intensity — Off / Low / Medium (default) / High. Tunnel-vision on motion; higher = less sickness.
Snap turn — On by default (30° discrete turns). Turn off for smooth rotation if you don't get sick.
Sitting OK — On by default. Turn off only if your space requires room-scale.
Change them in the VR shell's Settings panel (see The VR shell). They are saved to your persona and follow you across every world you play.
Fourteen of the eighteen game families render in cinema mode in VR — the flat 2D viewport projects onto a curved screen at a virtual seat. Realtime-3D plays in native mode, and retro (emulator), uploaded web games and incremental games do not run in VR: they play flat. The Quest browser, Vision Pro Safari, and PCVR all render this identically: 1.8m × 1.2m curved panel at 1.5m forward, with the HUD floating to the left of the screen.
What you'll see:
Arcade / Platformer / Roguelike / Crawler / TTRPG / Survival / Strategy-Sim — Phaser or canvas viewport on the curved screen, HUD on the side panel.
Narrative / Visual-Novel / Point-and-Click — DOM-based viewport rendered through a Drei <Html> portal; text + choice buttons all readable.
Board game (non-chess variants) — same cinema treatment; chess specifically has a native 3D mode (see Native mode below).
Racing / Classic recreations / Interactive fiction — the same curved screen; text games read like the narrative viewport.
You play with whatever input device you have — controllers point a ray cursor at the screen, hands pinch on Vision Pro. Same controls as flat mode, just projected on a virtual screen.
Walls + floors + boss + enemies + character all render in 3D around you. You can walk around enemies, dodge boss AOE patterns by physically stepping back, swing your right controller at melee range. Cinematic cameras (combat zoom, death cam) clamp to subtle world nudges (≤0.3m) so head pose stays under YOUR control — the camera never yanks you.
A wood-pedestal table at seated height (~0.9m) with the 48cm × 48cm chess board. 32 low-poly pieces. Point a ray cursor at your piece, click to select; legal-move squares glow cyan (capture squares glow red); click to place. Other board games (hex-settlers, deckbuilder, council-table) stay cinema mode.
Open wilds.ai/app/vr in your headset's browser and press Enter VR to browse and launch worlds without taking the headset off. Turn your left palm down for the wrist menu: Browse (a grid of worlds; pick one for its detail panel, then its play lobby), Characters, Settings (locomotion, vignette, snap turn and sitting, saved to your persona) and Profile. In a browser without WebXR the page runs as a preview, with a link to browse worlds in flat mode.
The Enter VR button doesn't appear on my world's page. Three possible reasons:
Your browser doesn't support WebXR. Open DevTools and check navigator.xr — if it's undefined, your browser isn't capable. Use one of the supported headsets/browsers above.
The creator set the world to opt out of VR.xrSettings.mode: 'off' on the blueprint hides the button. Pick a different world.
The capability probe failed. Hard-refresh (Cmd+Shift+R) and check the browser's <html> tag — it should have a class of xr-vr or xr-ar. If it's xr-unsupported, your browser doesn't have the right capability.
I get motion-sick in smooth-locomotion mode. Switch to Teleport in the VR shell's Settings panel at /app/vr. Bump vignette to High. Snap turn should stay on.
I'm hand-tracking only on Vision Pro and I can't tell what's selected. The ray cursor follows your gaze; whatever you're looking at + pinch = confirm. The wrist menu appears while your left palm faces down; turn the palm back over to close it.
The character looks 2D / flat. That's the default portrait mode — a curved billboard following you at shoulder height with a mood ring + voice ring. The creator may have generated a 3D avatar for the character that hasn't fully rigged yet, or may have set the world to characterMode: 'portrait' intentionally. The 2D portrait is the supported default.
My save game from flat mode loads when I enter VR mid-run. Yes — autosave is shared. Quit a dungeon mid-fight from flat mode, re-enter the same blueprint on a Quest 3, and your run picks up where you left off (HP, position, kills, pickups, all of it).
Performance is choppy on Quest 2. Some realtime-3d worlds with dense scenes push Quest 2's limits. The platform automatically drops resolution + halves particles when it detects frame-time breaches. Try a less-dense world, or upgrade to Quest 3 / Vision Pro.
My character isn't speaking. Check that you've enabled audio for the wilds.ai site in your headset's browser settings. Some Meta Quest builds default audio off for browser tabs.