Quest 3 setup

Open the published HTTPS link in Meta Quest Browser. Choose Enter VR, accept the headset prompt, then use a controller ray and trigger to select a vehicle or pause. Your viewpoint stays stationary.

Arrange the information screens in browser mode before entering VR. Use the headset’s system menu to exit. Recenter uses your current headset position.

Desktop and mobile have an orbitable map and all source controls. Other headsets need immersive WebXR support; support is detected, never assumed.

Actual Quest hardware, frame rate, comfort and hand tracking have not been verified in this development environment. Controller input is implemented; hand interaction is not certified.

Live means live.

The shipped room is a simulation with a fictional circuit and generated vehicles. Importing a file labelled recorded enables historical replay; the source is supplied by the file author and is not independently authenticated.

Imported gaps over five seconds hide the affected vehicle. Movement between nearby samples is interpolated, not an observed continuous path. Sample speed is held until the next sample; no speed is inferred.

There is no connected live feed. No person locations, hidden drone feeds, subscription unlocking or inferred spectator movement.

One hub. Separate rights.

Selected official YouTube replays can use the official embedded player after you request one. Region, age, login and embedding restrictions may still prevent playback. Use the provider link when a player fails.

F1 TV, FIAWEC+, Rally.TV and MotoGP subscriptions remain with their providers. Browser DOM players cannot be copied into WebXR textures; DRM and cross-origin restrictions still apply.

Paid video is not rendered inside the immersive room. Its screens contain timing and source information. You may open supported official apps or browser windows using your headset’s own window management.

From prototype to race weekend.

Ready: source discovery, saved favourites, browser viewing slots, configurable spatial panels, fictional simulation, validated replay import and explicit provenance.

Next: physical Quest acceptance, rights-approved personal telemetry adapter, timestamped source health and user-controlled broadcast offsets. Live-feed tokens would stay on a protected server, never in a public client.

Later: licensed live data, georeferenced tracks, terrain with attribution and event-specific camera integrations. Continuous Dakar GPS, person locations and freely selectable drones remain unavailable without a permitted source.