xrizer, the open-source layer that lets SteamVR-era OpenVR games run on ANY OpenXR runtime WITHOUT SteamVR, SHIPPED version 0.6 on October 8, its FIRST tagged release in 199 DAYS. Maintainer Supreeeme opened the notes with an apology: “Wow it’s been 7 months since the last release! My bad.” The release thanks two contributors for fixes that got “some games working (most notably the latest version of Half Life Alyx).”
TWO days later, a user FILED issue #448: Half-Life: Alyx, launched through Steam with xrizer 0.6 on the WiVRn runtime, “crashes immediately with a panic” because GetPosesForFrame “is not yet implemented.” As of October 18, that function is STILL a todo!() stub on xrizer’s main branch, and the issue has NO REPLIES.
Why xrizer Matters
Most PC VR games were built against Valve’s OpenVR API, which normally means RUNNING SteamVR. The xrizer README describes the project as “a reimplementation of OpenVR on top of OpenXR,” so those games can talk DIRECTLY to runtimes such as Monado or WiVRn, the OPEN-SOURCE stack that Linux VR users lean on to STREAM to standalone headsets. That matters MORE this month, as Linux VR users weigh Valve’s OWN SteamVR Linux support against the open-source route.
The README is CANDID about MATURITY. It calls xrizer “currently immature,” warns that “many things are likely broken,” and points people who want “a more mature solution” to OpenComposite, the older project that some of xrizer’s code is based on. The repository is GPL-3.0 licensed, written in Rust, and had 335 GitHub STARS, 88 forks and 150 OPEN issues and pull requests on October 18.
Among Linux VR users on X, the pitch is about TAKING SteamVR out of the loop:
@Sarxis_Cat @2Pish181332 If you don't do anything particularly special on your pc you could try a linux distro + monado+ xrizer.
Essentially leaves steam vr out of the equation giving you a far better experience.— Loki H (@Loki_Hellheim) October 2, 2026
What 0.6 Actually Changes
GitHub’s compare view counts 28 commits from NINE contributors between v0.5 and v0.6. The USER-FACING list is SHORT, and MOSTLY plumbing:
- System OpenXR linking. xrizer PREVIOUSLY ALWAYS bundled the OpenXR loader statically. A change from contributor SpookySkeletons makes DYNAMIC linking to a system-installed loader the DEFAULT, which the notes say is “nice for packaging xrizer in repositories.” STATIC builds remain AVAILABLE behind a
static-openxrfeature flag. - An input-profile refactor. Supreeeme REBUILT how input profiles are defined internally. The notes promise “no discernible difference to a user” but WARN that “there may be bugs that appear as a result.”
- Game fixes. The compare log includes NEWER OpenVR interface versions, a Touch Plus controller profile, Knuckles binding fixes, scroll bindings, and a change that lets OLDER games requiring raw play-space boundaries run.
The release ALSO formalizes a new AI policy, first posted September 24. It BANS pasting raw LLM output into issues, comments, pull request descriptions or REVIEW replies (“If you didn’t want to write it, I don’t want to read it”), while allowing AI-assisted pull requests “as long as you generally understand what is going on.” Supreeeme WRITES that he does NOT personally use AI to develop xrizer, and that rule-breaking issues or PRs may be IGNORED or CLOSED.
The Alyx Gap
Half-Life: Alyx is the BENCHMARK most Linux VR users care about, and the RECORD on xrizer’s tracker is MIXED. Beyond issue #448, issue #435, opened September 24, reports in-game HANGS, FROZEN hands and controller DISCONNECTS on WiVRn with Touch controllers. On October 11, Supreeeme ASKED the reporter for a LOG, and the reporter said it would take until later in the week. An OLDER report that players cannot throw objects in Alyx has been OPEN since January 16.
The compositor is where the STUBS sit. A pull request from an account named ntg-agent, #445, PROPOSED replacing the REMAINING todo!() bodies in the compositor interfaces “so apps calling them no longer abort the process.” It was opened October 9 and CLOSED without being merged about seven hours later. On October 11, Supreeeme committed his OWN implementation of one of those calls, GetLastFrameRenderer. GetPosesForFrame, the call NAMED in the Alyx CRASH, was NOT part of that commit.
A Broken Download Link
There is a SMALLER papercut for NEW users. The README’s “Latest release” link points to an asset named xrizer-release.zip. The v0.6 release instead ships xrizer-v0.6.zip plus a separate dependencies.zip, so on October 18 that README link RETURNED a 404. The release PAGE and the NIGHTLY link STILL work.
Download counts are MODEST across the board. On October 18, the v0.6 zip had 272 DOWNLOADS, against 2,348 for v0.5 over nearly seven months. Those numbers EXCLUDE distribution packages and the nightly builds the README labels “bleeding edge,” so they UNDERCOUNT real use.
What to Watch
The NEXT signal is whether GetPosesForFrame gets a REAL implementation, and whether issue #448 and the Alyx hang in #435 close against a TAGGED release rather than ONLY the nightly. For now, xrizer 0.6 is a PACKAGING and housekeeping release with a CLEAR contribution policy. Its own notes CLAIM the latest Alyx works, and its own issue tracker shows that claim is NOT yet settled for EVERY setup.
Sources: xrizer v0.6 release notes (October 8, 2026); xrizer repository and README; v0.5 to v0.6 compare; xrizer issues #433, #448, #435, #281 and pull request #445; GitHub releases API (read October 18, 2026); @Loki_Hellheim on X.
Featured image: Meta Quest 3 headset, front view, photo by Roy.wonder.cohen via Wikimedia Commons, CC BY-SA 4.0. Quest headsets are among the standalone devices WiVRn streams PC VR to.