Meta’s Horizon OS v2.9 has been in the Public Test Channel since the week of September 28, and the HEADLINE features are now well documented: a spatial window manager Meta calls Display Evo, the RETURN of classic home environments, and a system QR scanner. Meta’s own release thread on its community forums tells a LESS polished story. Only SIX comments sit under the post, but they describe a DEVELOPER-facing AUDIO regression, a headset that would NOT boot, and a STORAGE error on a 512GB Quest 3.
What testers reported
- Audio: one developer flagged a “CRITICAL bug” in which immersive apps’ audio is now “window-spatialized by default,” listing a NaN pose, added reverb and a −2 dB drop. The post links a FORMAL report in Meta’s developer feedback system. A second developer replied that they see the SAME issue and called it critical because their project “is releasing in very few weeks.”
- Display and boot: another tester said v2.9 WORKED at first, then produced VISUAL errors after sleep, including a black void in place of menus on photos and a screen that duplicated vertically. The same user later wrote that the headset would not BOOT and that a FACTORY RESET was the last option. They listed build 5264196.1340.520.
- Storage: that tester also reported that on a 512GB Quest 3, installs FAILED once free space reached 413GB, with the system asking them to clear room for an 8GB app. They asked whether this was a v2.9 bug or failing storage; the thread contains NO answer.
A third commenter said they had SEEN NOTHING different and that everything worked. Meta has NOT replied in the thread, and none of these reports has been CONFIRMED by Meta as a known issue.
Why the audio report matters
The window manager is the BIGGEST change in v2.9. UploadVR and VR.org BOTH describe windows that now open into the room, group and stack. If the system is also treating IMMERSIVE apps’ audio as if it came from a POSITIONED window, that is the kind of side effect that could reach players if it ships to the STABLE channel unchanged. For a studio about to LAUNCH, a reverb and level shift it did not author is a REAL problem, which is why the second developer’s reply carries weight.
What to do with this
The PTC is OPT-IN, and Meta SAYS v2.9 features roll out GRADUALLY to enrolled headsets; the last general release was v2.7, and NOTHING here has a stable date. Meta’s thread asks testers to post each bug in its OWN forum thread tagged “PTC v2.9” and to file bug reports. Developers shipping SOON should TEST their audio on a v2.9 PTC headset now rather than wait for the stable build. Everyone else who relies on a Quest daily has a SIMPLE option: stay on the stable channel until Meta addresses these reports.
Sources: Meta Community Forums, v2.9 PTC Release Thread; Meta Quest release notes; UploadVR; VR.org.