TL;DR:
- XR headsets render two eyes at high framerates with limited GPU power — 3D assets that run fine on a desktop will drop frames in a headset.
- Each headset platform has different polygon and texture budgets; visionOS is more generous than Quest standalone.
- PBR materials (albedo, roughness, metallic, normal maps) are the universal standard — avoid baked lighting that won’t match the real environment.
- LOD (Level of Detail) systems, texture atlasing, and draw call reduction are the main levers for performance headroom.
Creating 3D content for XR is harder than it looks. The same asset that renders beautifully in Blender’s viewport will cause frame rate problems on a standalone headset. The constraints are real: headsets render at 90–120fps across two high-resolution displays simultaneously, from hardware running on battery power with thermal throttling to manage.
Understanding the constraints is the first step to creating content that actually works well in a headset.
Why XR Performance Is Different
Desktop games can afford high polygon counts and complex shaders because they have a discrete GPU drawing a single viewport at 60fps. XR adds several compounding constraints:
Two eyes, double the cost: stereo rendering draws the scene twice per frame. Some engines use techniques like instanced stereo rendering to reduce this overhead, but the baseline is roughly 2x the render cost compared to a flat display.
High frame rate requirement: dropping below 72fps in a headset causes visible stuttering that many users find nauseating. Most platforms target 90fps for immersive experiences. The render budget per frame at 90fps is 11ms. That’s everything: geometry, textures, shaders, physics, application logic.
Limited GPU power: standalone headsets run on mobile SoCs. The Meta Quest 3 uses a Snapdragon XR2 Gen 2; Samsung Galaxy XR runs on a Snapdragon 8 Elite. These are powerful mobile chips, but they’re not desktop GPUs. A scene that runs at 90fps on a PC may run at 20fps on Quest standalone without optimisation.
Passthrough XR adds texture sampling cost: any experience using colour passthrough as the background adds continuous texture sampling overhead before your content is drawn.
Polygon Budgets by Platform
These are practical guidelines, not hard limits — the right budget depends on your scene complexity, materials, and draw calls:
| Platform | Total Scene Budget | Per Character/Hero Asset | Per Background Prop |
|---|---|---|---|
| Apple Vision Pro (visionOS) | 500K–1M+ tris | 20K–50K tris | 5K–15K tris |
| Meta Quest 3 (standalone) | 150K–300K tris | 5K–15K tris | 1K–5K tris |
| PC VR (SteamVR/linked Quest) | 1M–2M+ tris | 50K–100K tris | 10K–30K tris |
| Android XR (Samsung Galaxy XR) | 200K–400K tris | 10K–20K tris | 2K–8K tris |
Apple Vision Pro’s M-series chip has significantly more headroom than standalone Android XR headsets. Content designed for visionOS will need substantial polygon reduction to target Quest standalone — plan your pipeline accordingly if cross-platform deployment is a goal.
PBR Textures: The Right Workflow
PBR (Physically Based Rendering) is the universal standard for real-time 3D across all platforms. A standard PBR material uses:
- Albedo/Base Colour: the base colour without lighting information. Do not bake ambient occlusion or shadows into the albedo for XR — the baked lighting will look wrong in different real-world lighting conditions.
- Roughness/Metallic: combined into a single 2-channel texture or separate maps. Roughness controls surface texture from mirror-smooth (0.0) to completely diffuse (1.0). Metallic is binary for most surfaces (0 or 1) with exceptions.
- Normal map: encodes surface detail that affects lighting without adding geometry. The highest-value optimisation available — a well-crafted normal map can make a 500-tri mesh look like it has 50,000 triangles.
- Ambient Occlusion (AO): contact shadows baked per-object. Keep this separate from albedo so it can be optionally disabled or multiplied at render time.
Texture resolution targets for standalone XR:
- Hero assets (things users inspect closely): 1K–2K per texture set
- Background props: 512×512 or 1K, consider texture atlasing
- Terrain/environment: 2K with tiling patterns to avoid resolution waste
Compress textures for the target platform: ASTC for Android XR, ASTC or ETC2 for Quest, ASTC or BC7 for visionOS. Uncompressed or PNG textures in a production build waste GPU memory and bandwidth.
Level of Detail (LOD)
LOD systems swap high-polygon versions of assets for simplified versions when the object is far from the camera. The engine handles the switching automatically based on screen coverage.
Most 3D engines (Unity, Unreal, RealityKit) have built-in LOD support. A typical LOD chain:
- LOD0: full-resolution, full-texture, nearby
- LOD1: 50% polygon reduction, normal maps carry visual detail
- LOD2: 25% of original polygons, simplified texture
- Impostor/Billboard: 2D plane at furthest distances (for trees, distant buildings)
For XR, set LOD transitions more aggressively than desktop defaults — at arm’s length, small objects don’t need the same detail they’d have on a desktop display.
Draw Calls: The Hidden Cost
Draw calls are instructions the CPU sends to the GPU: “draw this mesh with this material.” Each draw call has overhead regardless of how simple the mesh is. A scene with 500 simple cubes using 500 different materials can perform worse than a scene with 50,000 polygons all sharing one material.
Practical reductions:
Texture atlasing: combine multiple small textures onto a single large texture sheet. Multiple props using the same atlas can share a single draw call via GPU instancing.
GPU instancing: if you’re drawing the same mesh multiple times (trees, rocks, building modules), use instancing. One draw call handles all instances.
Static batching: combine non-moving meshes in the scene into a single mesh at build time, eliminating per-object draw calls at runtime.
Shader complexity: custom shaders add per-pixel processing cost. Use the platform’s optimised standard shaders wherever possible, and profile custom shaders carefully.
Profiling Tools
Don’t guess — measure. Every platform provides profiling tools:
- visionOS: RealityKit Profiler in Xcode, Instruments
- Meta Quest: Meta XR Simulator, OVR Metrics Tool, Android GPU Inspector
- Unity: Frame Debugger, Profiler window, Rendering Statistics overlay
- Unreal Engine: Stat commands, GPU Visualizer, XR performance mode
Run the profiler before shipping. The typical discovery is one or two overlooked assets with 10x the expected polygon count, or a texture that wasn’t compressed, or a shader that’s running per-pixel operations that should be pre-baked. These are fixable problems; the profiler finds them.