As an indie developer who migrated a Unity project to URP in a single day, Meta's PCVR Link stack and broken Beat Saber promises are a complete technical failure
I’ve been trying to access the Beat Saber level editor on PC via Meta Horizon / AirLink, but the user experience is downright unplayable. We are talking severe visual artifacts, unmanageable encoder latency, broken pairing protocols, and complete connection drops—even on a high-end PC setup.
What makes this utterly unacceptable is the contrast in performance. I can run heavy VR titles like BeamNG.drive smoothly through SteamVR over the network without issue. Yet, Meta’s proprietary desktop software and AirLink UI can’t even maintain a stable connection baseline.
As an indie developer, I converted my own Unity story-driven game to URP in just a single day. Knowing firsthand how straightforward Unity's Render Pipeline migration is, observing a multi-billion-dollar corporation drag its feet for months over promised URP ports and "performance optimizations" for Beat Saber while leaving the PCVR AirLink pipeline bloated is mind-boggling. Instead of maintaining a lean, high-throughput streaming pipeline, Meta continues to stack bloated background services, telemetry, and unnecessary UI layers onto a legacy PC codebase.
This isn't a hardware bottleneck on the user's end; it’s an architectural debt problem across Meta's entire PCVR stack—from the AirLink handshake protocol to the stream encoding itself. When a solo-developer app like Virtual Desktop consistently outperforms a tech giant's native solution by a lightyear, your engineering priorities are fundamentally broken.
Deliver on your URP/performance promises, fix your PCVR stack, strip the background bloat, and give us a functioning, low-latency ecosystem.