hz-unity-code-review

Unity Code Review for Meta Quest

When to Use

Use this skill when reviewing Unity C# code or project settings that target Meta Quest headsets. This includes:

• Reviewing scripts for VR performance issues
• Checking rendering pipeline configuration and settings
• Ensuring adherence to Quest-specific best practices
• Identifying common VR development pitfalls
• Validating input handling for controllers, hands, and eye tracking
• Auditing memory usage and GC allocation patterns

Key Review Areas

1. Rendering Pipeline Configuration

Quest applications must use the Universal Render Pipeline (URP) with specific settings optimized for mobile VR. The Built-in Render Pipeline is not recommended for new Quest projects.

Critical settings to verify:

• Single-pass multiview must be enabled (Player Settings > XR Plug-in Management > Oculus > Stereo Rendering Mode)
• Vulkan should be the primary graphics API
• Linear color space is required for correct lighting
• HDR should be disabled in URP asset settings
• Post-processing should be minimal or disabled

2. Draw Call Budgets and Batching

Quest has draw call budgets that vary by workload complexity. Every draw call has CPU overhead that directly impacts frame timing.

Metric	Quest 2 / Quest Pro	Quest 3 / Quest 3S
Draw calls (busy simulation)	80-200	200-300
Draw calls (medium simulation)	200-300	400-600
Draw calls (light simulation)	400-600	700-1000
Triangles per frame	750K-1M	1M-2M
SetPass calls	< 50	< 80

Enable and verify:

• Static batching for non-moving geometry
• GPU instancing for repeated objects
• SRP batcher for URP materials
• Dynamic batching for small meshes (< 300 vertices)

3. Shader Complexity

Mobile GPUs on Quest cannot handle desktop-class shaders. Review all materials for:

• Use of URP/Lit or URP/Simple Lit instead of Standard shader
• Custom shaders that minimize texture samples and ALU operations
• Avoidance of real-time shadows where possible (bake instead)
• No screen-space effects (SSAO, SSR, screen-space shadows)