VALVE has drawn a LINE under one of the most POPULAR ways to stream PC VR on LINUX. Closing a FRESH bug report on its SteamVR for Linux tracker, the Valve member account kisak-valve wrote that “the current point release of ALVR is not supportable on SteamVR’s side.” The reply went up at 22:18 UTC on October 14 (6:18 p.m. ET), roughly THREE and a half minutes after the report was filed, and the release it refers to, ALVR v20.14.1, is now FIFTEEN months old. MIXED first reported the exchange on October 16; we CHECKED the underlying GitHub threads ourselves.
What Valve Actually Said, and What It Did Not
The WORDING is NARROW, and it MATTERS. Valve did not say ALVR is BLOCKED, deliberately BROKEN, or permanently unsupported, and it has announced NO SteamVR change aimed at the app. The SCOPE is the CURRENT point release, on SteamVR’s side. For its reasoning, kisak-valve linked to a June 25 comment on issue #901 by tracker contributor Packetdancer, who argued that ALVR “does not use normal SteamVR APIs.” In an earlier June 17 post on the same thread, Packetdancer wrote that “instead of functioning like a normal HMD driver in SteamVR, ALVR tries to slice open chunks of SteamVR,” so ANY internal SteamVR change can BREAK it. As MIXED points out, that is a contributor’s READING, not a formal company STATEMENT, even though Valve’s account CHOSE to cite it.
For context, ALVR is the OPEN-SOURCE streamer that Quest and Pico owners use to send PC VR from their OWN machine to a STANDALONE headset, and on Linux it is one of the MAIN alternatives to Valve’s built-in Steam Link VR driver. Its GitHub releases show v20.13.0 on March 11, 2025, v20.14.0 on June 30, 2025, and v20.14.1 on July 14, 2025, with NO stable release since.
The Report Was Really About Valve’s Own Driver
The DETAIL that complicates the HEADLINE: the person who filed issue #1017 had TESTED BOTH ALVR and Steam Link VR, on a Pico 4 over Ethernet, an Nvidia GeForce GTX 1070, and Gentoo Linux. In a follow-up, they wrote that Valve’s own driver “is the main focus of my report.” On SteamVR 2.16.6, Steam Link VR FAILED to create a Vulkan device with VK_ERROR_EXTENSION_NOT_PRESENT. On the 2.18.3 BETA the headset is DETECTED, but streaming STILL dies with VK_ERROR_DEVICE_LOST, an Nvidia Xid 13, and a timeline synchronization ASSERTION in vrcompositor.
Twenty-five minutes after the first reply, kisak-valve REDIRECTED that half of the problem: “With ALVR taken out of the mix, then you’re most likely looking for the issue being tracked at #1005.” Issue #1005, opened October 10 by a GTX 1080 owner on Nvidia’s 580 drivers whose SteamVR beta session CRASHED, remains OPEN. According to MIXED, Valve reviewed those logs and wrote that the vrcompositor output “looks like something for a SteamVR dev to ponder.” OLDER Nvidia cards keep APPEARING in these reports, which is worth WATCHING regardless of where anyone lands on ALVR.
The Long Tail of Error 303
NONE of this is NEW for Linux users. Issue #901, “SteamVR 2.16.6 and ALVR result in 303,” has been OPEN since June 3 and carries 29 comments as of this writing, still labeled bug and Need More Information. On ALVR’s side, issue #3294 collects reports from Arch, Debian, Xubuntu and CachyOS users who say that DOWNGRADING SteamVR to its “previous” beta branch RESTORES streaming. A separate report, issue #910, argues the OPPOSITE causation: its author says their ALVR driver files were UNCHANGED since November 2025 and that sessions BROKE the moment a SteamVR update landed on June 22, 2026. Both READINGS can be TRUE at once. An app that LEANS on SteamVR INTERNALS will break when those internals MOVE, and whoever moved them is the only party that can SEE it coming.
User FRUSTRATION shows up outside GitHub, too. Even before this week, owners were describing ALVR as HARD to keep running:
@udiWertheimer @markgurman Hoping that we’re a step closer to full SteamVR support on Vision Pro with the release of the Steam Frame. But I’ll be using my Frame for gaming until that’s the case because I’m not savvy enough to do all of this and ALVR was too finicky for me. Such a shame.
— Hunter (@LHuntorr) October 5, 2026
What Linux PC VR Players Can Do Now
- Expect no Valve FIXES aimed at ALVR v20.14.1. Reports that HINGE on that build are likely to be CLOSED, as #1017 was.
- Test Steam Link VR on its own. If it also fails, the problem belongs in Valve’s tracker without ALVR in the setup, which is EXACTLY what kisak-valve asked for.
- The “previous” SteamVR branch is the WORKAROUND ALVR users cite most often, with the obvious TRADE-OFF of MISSING newer fixes.
- Check driver floors. ALVR’s own Linux troubleshooting wiki lists Nvidia driver 535 or newer and CUDA 12.1 or newer as REQUIREMENTS.
The Metaverse Watcher Take
This is not Valve DECLARING war on a community project; it is a support DESK refusing to debug a stack it does not CONTROL. The real PRESSURE point is TIMING. Valve is POURING engineering into SteamVR and SteamOS for the Steam Frame, and every one of those updates is another CHANCE to break a tool that, per Valve’s cited explanation, works by REPLACING pieces of SteamVR rather than CALLING its APIs. Fifteen months without a stable ALVR release makes that GAP WIDER each month. The ball is now in the ALVR maintainers’ COURT: a new stable build that behaves like a NORMAL SteamVR driver would TURN “not supportable” back into an ORDINARY bug queue. Until then, Linux users who want Valve’s HELP should LEAD with Steam Link VR.
Sources: MIXED; SteamVR for Linux issues #1017, #1005, #901 and #910; ALVR releases, ALVR issue #3294 and ALVR Linux troubleshooting wiki; @LHuntorr on X. GitHub details checked October 16, 2026.