AR/VR Performance Tuning
Performance decides whether an AR or VR experience feels smooth or uncomfortable. Slow frames create judder, blur, and tired eyes. Tuning keeps the frame rate steady so users stay comfortable and focused on the content.
Understand the Frame Budget
Every frame must finish inside a fixed time. Divide 1000 milliseconds by the refresh rate and you get the budget. A 90 Hz headset gives you about 11.1 milliseconds per frame. A 72 Hz headset gives 13.9 milliseconds, and a 120 Hz headset gives 8.3 milliseconds. Missing the budget causes dropped frames that users feel immediately.
Diagram: 90 Hz Frame Budget
Total budget: 11.1 ms | Game logic 2 ms | Physics 1.5 ms | Rendering 6 ms | Safety margin 1.6 ms |
Measure First
Profilers show which tasks eat time. Unity, Unreal, and headset makers provide tools that display frame time, draw calls, and memory use. Fix the largest cost first. Guessing wastes hours, and measuring points straight to the problem.
Key Optimization Techniques
Reduce Polygons
Fewer triangles mean less work for the graphics chip. Hide detail that players never see, and use simpler shapes for distant objects.
Level of Detail
Level of detail (LOD) swaps a detailed model for a simpler version as the object moves away. A tree that fills the view uses thousands of triangles. The same tree in the distance uses a few hundred.
Cut Draw Calls
Each separate object sends instructions to the graphics chip. Combine meshes, share materials, and use batching so the chip receives fewer, larger jobs.
Compress Textures
Large images use memory and bandwidth. Compressed formats and sensible sizes keep scenes sharp and light.
Bake Lighting
Real-time lights and shadows cost a lot. Baked lighting stores light information in textures ahead of time, which suits objects that do not move.
Occlusion Culling
The engine skips drawing objects hidden behind walls. A closed room renders only what fits in the room.
Foveated Rendering
Headsets with eye or fixed foveation reduce detail in the outer view and save processing power.
Real Example
Picture a virtual city with 500 buildings. The first test runs at 60 frames per second on a headset that needs 90. The profiler reveals that thousands of small props create too many draw calls. The team merges street props, adds LOD to distant buildings, and enables occlusion culling. The scene reaches 90 frames per second with no visible loss.
Mobile and Standalone Headsets
Standalone headsets and phones carry less power and produce heat. Long sessions slow the chip down to stay cool. Target lower polygon counts, simple shaders, and moderate texture sizes. Test sessions of 20 to 30 minutes to catch heat-related slowdowns.
Optimization Checklist
| Area | Action |
|---|---|
| Models | Use LOD and remove hidden faces |
| Textures | Compress and resize |
| Lighting | Bake static lights |
| Code | Avoid heavy work inside every frame |
| Memory | Reuse objects instead of creating new ones |
| Testing | Profile on the target device |
Why Performance Matters
Smooth frames protect comfort, keep immersion intact, and earn better user reviews. Developers who plan performance from the first day avoid painful rework near launch.
Common Mistakes
Teams often add detail first and test performance last. Others test only on a powerful computer and ignore the target headset. Some leave unused objects active in the scene. Early profiling, device testing, and regular cleanup prevent all three problems and keep projects on schedule.