VR Software Development for an Open-Air Virtual Museum: Meta Quest Deployment

The Engineering Brief

Nine independent VR environments. Six artists across five countries delivering assets in different formats, at different quality levels, with different lighting assumptions. A single standalone Meta Quest headset per visitor, running without a tethered PC. An outdoor garden as the venue — ambient light, no guaranteed connectivity, battery management for full-day sessions.

That was the brief for «Horizontes Cyborg» at the Museo Evaristo Valle in Gijón. This post covers the technical decisions that made it work.

Standalone VR: Why the Hardware Constraint Changes Everything

Standalone headsets like the Meta Quest run on a mobile Snapdragon SoC with a shared memory budget and no discrete GPU. The platform enforces a hard 72 fps floor — drop below it and the compositor introduces judder that immediately causes disorientation, ending the experience for that visitor.

That constraint cascades into every rendering decision:

• Triangle budget: each environment capped at 500k triangles in-frustum. Artists delivering film-quality meshes needed decimation passes that preserved silhouette without destroying UV seams.
• Draw calls: kept below 150 per frame through static batching and GPU instancing on repeated elements.
• VRAM: capped at 1.5 GB across all loaded assets. Textures compressed to ASTC 6×6 — a format native to the Adreno GPU that achieves 60–75% VRAM reduction versus uncompressed PNGs while preserving perceptual quality on the headset’s display.
• Lighting: real-time dynamic lighting was eliminated from all nine environments. Baked lightmaps, pre-computed ambient occlusion, and lightprobes for movable objects kept frame time deterministic.
• LOD: multi-level detail meshes on objects beyond 8 metres. Environments with large open areas used aggressive distance fog to permit early culling.

Each environment went through a performance audit pass before integration — running on physical hardware, profiling with the Meta Quest GPU and CPU overlay active, and iterating until frame pacing was stable.

Multi-World Navigation: UX for Non-Technical Visitors

The nine environments are discrete scenes, not a continuous world. Visitors needed to move between them without breaking immersion or requiring controller literacy they didn’t have.

The solution was a transit hub — a neutral space visitors return to between environments. From the hub, nine portals display live previews of each destination. Selection uses gaze-and-hold: look at a portal for three seconds to activate the transition. No button press, no menu, no controller familiarity required.

Session management was handled at the application layer: the hub tracks which environments a visitor has visited, dims completed portals, and surfaces a progress indicator. If a visitor removes the headset mid-session, the hub restores state on reconnection so they can continue without repeating environments.

The gaze-and-hold threshold of three seconds was calibrated through testing with first-time VR users. Below two seconds produced accidental activations from natural gaze movement; above four seconds felt unresponsive. Three seconds, with a visible radial progress indicator, produced zero unintended transitions in testing.

Cross-Artist Asset Integration

Six artists delivered nine environments. The formats varied: Unity packages, Blender scenes, FBX archives, GLTF files, and one environment delivered as a Unreal Engine project requiring conversion. Material systems, coordinate spaces, and scale conventions differed across all submissions.

The integration pipeline had four stages:

1. Format standardisation — all source assets converted to a common FBX intermediate with consistent scale (1 unit = 1 metre) and Y-up orientation.
2. Material remapping — PBR materials rebuilt in Unity URP using the source artist’s reference renders as the target. Shader complexity stripped to meet mobile constraints.
3. Validation gate — automated check: triangle count, draw call count, texture memory footprint, and a 60-second runtime profiling session on physical hardware. Any environment exceeding thresholds returned to optimisation before proceeding.
4. Lightmap baking — GPU lightmap baking per environment with manual lightprobe placement for visitor avatar interaction.

The pipeline produced consistent results regardless of source format, and the validation gate caught performance regressions before they reached the physical device fleet.

Field Deployment

The outdoor venue introduced constraints that a controlled lab environment does not:

Battery management: a fleet of Meta Quest headsets running full-day sessions requires a rotation schedule. The application was configured with a battery threshold: at 20% charge, the hub displays a session-end prompt and the headset is flagged for swap. Charging stations and headset sanitisation were integrated into the visitor flow.

Ambient light: outdoor light varies through the day. HDR rendering kept virtual scene brightness perceptually stable regardless of whether the visitor was in sun or shade, preventing the washed-out appearance that occurs when virtual and real ambient light clash.

Connectivity-free operation: the museum gardens had no guaranteed Wi-Fi. All nine environments were bundled into the application build — no streaming, no runtime asset download. Device management (configuration updates, log collection) was handled via a local MDM setup during off-hours rather than over-the-air during operation.

Where This Architecture Applies

The engineering decisions made for «Horizontes Cyborg» are not specific to cultural installations. The same standalone Meta Quest platform, gaze-based navigation, and connectivity-free deployment model are directly applicable to:

• Industrial training — maintenance procedure walkthroughs on factory equipment, deployed to workers on the floor without a PC or network dependency.
• Remote site visualisation — architectural or infrastructure environments for client review at any location.
• XR onboarding — product demonstrations, facility tours, or safety inductions delivered via a self-contained headset fleet.

If you are evaluating VR for an industrial or enterprise application and need a team that has solved the deployment engineering — not just the visuals — see our immersive experiences work or read the full technical case study.