Something I learned the hard way on Quest: chasing triangle counts while ignoring draw calls is a trap. A scene with 200k triangles in 50 draw calls will run better than 100k triangles in 500 draw calls — the CPU cost of submitting draws is what kills VR frame rates, and VR renders everything twice.

The checklist, in the order I run it:

• Batches under 150 (Stats panel). Combine meshes, bake one atlas, SRP Batcher on, Single Pass Instanced rendering on. Multi-Pass literally doubles your draw calls.
• Tris under ~750k visible. Simplify the worst offenders first — Profiler's Rendering module, sorted by triangles.
• LOD everything beyond arm's reach. 2–3 levels, aggressive cutoffs. In a headset, distant detail is genuinely hard to see.
• Textures capped: 1024 environments, 512 props, ASTC always. Oversized textures burn fill rate for detail nobody can display.
• Zero realtime lights. Bake lightmaps, light probes for dynamic objects, shadows off or cheapest.
• Kill overdraw. Alpha-blended particles and stacked transparent layers are the usual white-hot spots in overdraw view.
• Fixed Foveated Rendering on. Up to ~28% pixel shading savings, nearly free, via the Meta XR SDK.

Then verify on-device with OVR Metrics. The editor lies about mobile performance — a build that looks fine in the editor can still miss 72fps on the headset.

Full checklist with the details: https://kashi45248-prog.github.io/Blackbox_creations-/tutorial-meta-quest-72fps-mesh-optimization.html