The Unity Cube — Tony “SkarredGhost” Vitillo’s deliberately pointless Horizon Store app — is now one of the first published Quest titles asking for 207 Hz on Meta Quest 3. After Horizon OS 2.7 unlocked extended refresh rates, the free gray cube is suddenly the cleanest way to feel the new ceiling without a PC streamer or a sideload tool.
Road to VR (Sept. 2, 2026) calls it the first fully published Quest game known to hit the new rate. Vitillo’s own write-up on The Ghost Howls (Sept. 1) is more careful — “the first app (or at least, one of the first)” — and that hedging matches what we already covered on the Quest 3 207 Hz / 240 Hz unlock: Virtual Desktop and Quest Games Optimizer are chasing higher rates too, but a store app that is literally one mesh is still the purest smoke test.
Why a useless cube wins this race
Extended rates on Quest 3 shrink the frame budget to roughly 4.8 ms at 207 Hz. Dense games will struggle; a non-interactive cube with hand meshes does not. Vitillo ported the years-old project to a current Unity + Meta SDK build, added hand tracking, and requests 207 Hz after a one-second settle at 72 Hz. Launch it on a Quest 3 running Horizon runtime v2.7 or later, watch a brief glitch, and the OVR Metrics Tool should climb to 207.
Store page: The Unity Cube on the Meta Horizon Store (free). Quest 3 only — Quest 3S does not get the extended path.
What 207 Hz feels like (and what it does not fix)
Vitillo’s first-person notes, quoted by Road to VR, are the useful part. Higher rate feels “more reactive” and “smoother,” briefly odd “like trying VR under a heavy dose of caffeine,” then normal — until you drop back to 72 Hz and the world feels like it is “scattering.” He also flags artifacts the marketing slides skip: a short motion trail / halo when rotating the head, hand tracking that can feel jumpy rather than silkier, and hard drops to half rate near Guardian boundaries. There is almost no performance headroom.
240 Hz remains a Developer Mode / ADB experiment with display scaling, not something store apps can request. Vitillo documents the same two properties we already summarized (debug.oculus.forceDisplayScaling and debug.oculus.refreshRate). On unsupported home scenes it tears; on The Unity Cube it holds, and he could not reliably tell 240 apart from 207.
App Lab epilogue, still doing work
The Cube started as an App Lab stress test: would Meta accept a blank scene with a non-interactive gray box? It did. When App Lab folded into the main store, the same app landed in Horizon browse/search — still free, still “perfect as it is,” still not Early Access. The 207 Hz update is the joke’s second act: the worst game on the store is now the easiest way to sample the best panel mode Meta will ship to consumers on Quest 3.
If you want the API path for your own title, Meta’s Unity display-frequency docs still apply; Vitillo publishes a small wait-and-guard script on his post and notes Vulkan stopped random crashes in his build.
Sources: SkarredGhost — Quest 3 207 Hz / The Unity Cube, Road to VR, Meta Horizon Store, Meta display-frequency developer docs, prior MW coverage of Horizon OS 2.7 extended refresh rates.