top of page
Running at 72fps
When we tested the full experience on the headset, it crashed.
Frame rates dropped as low as 11fps, and the headset ran out of memory.
Testing nine rooms on one headset would take too long,
so I turned the whole team into a test lab.
I wrote a simple guide anyone with a headset could follow to capture performance data, and developed a fast iteration loop of testing, fixing and rebuilding.
By the premiere, every room ran at 72fps.
11 → 72fps
frame rates
~25 → ~18ms
GPU time in the corridors
31 builds
in 39 days
Everyone's a tester
I didn't have time to test all nine rooms myself. So I wrote a performance testing guide that allowed anyone with a headset, even with no experience, to record OVR Metrics and logcat data from each room and fill in a short report. I used AI to help sift the data, then dug into the captures and the Unity Memory Profiler to pinpoint where each problem lay.
Test, fix, repeat
Everyone with a headset tested each build, reporting bugs and UX issues as well as frame rate, running through every floor and flat multiple times. Each time, I found the cause, fixed it, and sent a new build straight back out: 31 builds in 39 days.
Looking where it counts
over 90%
GPU
Every capture showed the GPU working at over 90%. Foveated rendering, which draws the edges of your view at lower detail where you won't notice, was toggled off by default for Quest in Unity. Switching it on cut GPU time in the corridors from about 25ms to 18ms per frame, lifting the performance floor across the whole experience.
Sharper isn't always better
1.2 → 1.0
Resolution
Early on, I added a Renderscale script to the player rig that rendered everything at 1.2 times resolution for a crisper image. Testing showed it was the single biggest cost in the whole experience. Setting it back to 1.0 gave the biggest performance jump of the project, and on its own brought some rooms up to 72fps.
Paint only where it matters
1.80 → 0.83 GB
RenderTexture memory
Using the Unity Memory Profiler, I traced the #Instagirl freeze to the spray paint: every paintable surface reserved its textures as the room loaded, painted or not. Pavel, who built the mechanic, rewrote it so that surfaces only take up memory once you paint them and release it after five minutes. Together, we limited painting to walls and photos, and the RenderTexture memory fell from 1.80 GB across 275 objects to 0.83 GB across 27.
The last room paid for the rest
12fps
Molded by Society
Molded by Society, usually the last room users reached, ran at just 12fps. The cause? Rooms load and unload additively, meaning that leaving a room didn't free its textures, meshes and lightmaps, so GPU memory filled up room by room. I added a clean-up on every room change, so instead of stacking up, memory now recovers each time you leave a room.
One mesh, huge cost
~20 → 3 or 4
clothes piles
While going through every asset in wireframe view, I spotted a clothes pile with an extremely dense mesh. It was used in #Instagirl and stacked about 20 times in Molded by Society. It was remade far simpler, and I cut the stack to three or four. This one swap dramatically improved performance in both rooms.
Seamless room loading
41 shaders
277 variants
Every shader and material in Becoming (41 shaders, 277 variants) was captured through Unity and preloaded at startup. The app takes a little longer to open, but rooms load far more smoothly throughout the experience.
bottom of page
