Development of Content Updates and New Levels for VR Games

Development of Content Updates and New Levels for VR Games

Content updates for VR games are not just 'add a new room'. We solve this task daily: each new level must fit into existing technical constraints — draw call budget, memory limits, physics and tracking behavior. New content that ignores these limits breaks performance on devices where older levels ran stable. Contact us for a free project assessment.

The Main Pitfall When Adding Levels

The most common scenario: a developer creates a new scene, visually impressive, tests on a powerful PC with Quest 2 via Link — everything works fine. Then tests in standalone mode — 45 fps instead of 72, compositor reprojection every other frame, motion-to-photon latency with hand trails. The reason: the same optimization practices used in the original scenes were not applied to the new level.

Specific case: a new level for a shooter with dynamic shadows from three light sources. In old levels, shadows are baked in lightmap (Progressive Lightmapper, Mixed lighting mode). In the new one, they forgot to switch to Baked and left Realtime. On Quest 2, three realtime shadow casting lights guarantee GPU timing failure. Profiler showed 12 ms on shadow pass alone with a total budget of 13.8 ms per frame at 72 fps.

How to Avoid FPS Drop on New Levels?

The golden rule: don't rely on luck. We impose strict budgets: for Quest 2/3 standalone — no more than 100,000 vertices, 50–70 unique materials, draw calls within 150–200. For PC VR, the headroom is larger but still capped. Building lightmaps in HDRP takes 3 times longer than in URP but yields more realistic lighting. If your project is already on URP, stay on it for new levels.

How the New Content Development Process Works

Start with a technical specification including budgets. Then a grey-box (whitebox) version of the level for gameplay and tracking testing. In VR, whitebox testing is especially important: scale that looks readable on a screenshot can feel completely different with the headset on. Narrow corridors can cause discomfort that isn't obvious until tested in the headset.

Geometry of new levels is optimized using the same principles as the project's original scenes: LOD groups for static objects, Occlusion Culling bake for enclosed spaces, Mesh Combine where multiple static objects never change independently.

Integration with Existing Game Architecture

A new level is not only visual content. It includes integration with progression systems, save data, audio, spawn logic. In Unity via Addressables or AssetBundles, new content loads asynchronously to avoid freezing on first scene load. SceneManager.LoadSceneAsync() with LoadSceneMode.Additive is standard for VR, where instant black screen on scene change breaks presence.

For projects with continuous online or live service model, content updates often go through Remote Config — gameplay parameters of the new level load from the server without app rebuild. Unity Remote Config or Firebase Remote Config allow changing spawn rates, enemy counts, timers — everything that doesn't require new code.

Testing Before Publishing an Update

Regression testing of old levels is mandatory. New code or shared systems modified for new content can break behavior in existing scenes. Automated playtests with Unity Test Framework plus manual runs on target devices.

Performance baseline: each new level must pass Unity Profiler with GPU frame time measurement in worst-case scenario (maximum enemies/objects on screen). For Quest platform — Snapdragon Profiler for detailed GPU timing analysis.

What's Included in New Content Work

We are a team of VR engineers with 7+ years of experience, having completed 40+ VR projects. Order content update development — get a consultation and precise timeline estimate.

According to Unity documentation, the Addressables system reduces memory load by asynchronous asset loading on demand.