Valve has added EARLY support for 32-BIT OpenXR to Proton Experimental, the TEST branch of the compatibility layer that runs Windows games on Linux and SteamOS. The change is a SINGLE line in Valve’s Proton changelog, under the entry dated October 2, 2026: “Added early support for 32bit OpenXR (requires PROTON_USE_WOW64=1 on x86).” It matters to ONE specific group of games, OLDER Windows VR titles built as 32-bit executables, which until now had NO OpenXR path under Proton at ALL. MIXED reported the entry on October 7.
What Changed, and Where
The work lives in wineopenxr, the component that presents an OpenXR RUNTIME to a Windows game running under Proton. On Valve’s experimental_11.0 branch, Valve developer Paul Gofman authored the CORE commit, “wineopenxr: Implement 32 bit support and build 32 bit library,” on SEPTEMBER 14, with a fixup on September 22. TWO CLEANUP commits landed on September 21 and 22, and a FIFTH, also from September 14, moves wineopenxr to OpenXR registry version 1.1.63, up from the 1.1.58 update Gofman made in April.
That puts the code roughly TWO WEEKS ahead of the October 2 changelog stamp. The changelog date marks when the feature reached an Experimental build that owners can ACTUALLY opt into, NOT when it was written.
The Flag Is Required, and It Is Not in the README
NOTHING turns on by itself. Proton reads its runtime options from environment variables, and Valve’s README describes TWO ways to set them: PER GAME, through Set Launch Options in a game’s Properties dialog in the form VARIABLE=1 %command%, or GLOBALLY, by renaming user_settings.sample.py to user_settings.py in the Proton install folder and editing it.
The CATCH is that PROTON_USE_WOW64 does NOT appear in the README’s runtime options table on the experimental_11.0 branch. WoW64 is Wine’s mode for running 32-bit Windows code INSIDE a 64-bit process, and the changelog’s BRIEF parenthetical is effectively ALL the guidance an owner gets. For a 32-bit VR game, the PRACTICAL instruction is PROTON_USE_WOW64=1 %command% in its launch options, with Proton Experimental SELECTED as the compatibility tool.
What Valve Did Not Say
The changelog names NO specific 32-bit OpenXR game that now works, gives NO compatibility figures, and does not say when the feature might move from Experimental into a STABLE release. The current stable build, Proton 11.0-2, was published on August 21 and does NOT include it.
The wording is also LIMITED to x86. Valve says NOTHING about ARM64, the architecture the Steam Frame uses for standalone play, where Proton’s groundwork is arriving separately, most recently with the first ARM64 build of Wine Mono in September. For Linux desktops streaming PC VR to a Steam Frame, the rest of the chain is UNCHANGED: Valve has said SteamVR on a Linux host STILL has to be started by hand, and a 32-bit OpenXR layer does NOT address that.
Other VR Items in the Same Build
The same October 2 Experimental entry carries TWO more VR-specific changes. Blair Witch VR is listed among the titles that are NOW PLAYABLE, and Valve says it FIXED Blue Effect VR not STARTING on some CPUs. NEITHER is tied to the 32-bit work in the changelog.
Proton has CARRIED OpenXR since version 5.13-5, when Valve’s notes said Microsoft Flight Simulator’s VR mode became usable on AMD hardware, and later updates added D3D12 support in OpenXR. Until this change, that support was 64-BIT ONLY.
What to Watch
THREE things will show whether this is MORE than a footnote: whether players REPORT specific 32-bit OpenXR titles launching with the flag set, whether Valve DOCUMENTS PROTON_USE_WOW64 in the README, and whether the feature is CARRIED into the next stable Proton release. Until then, “early support” is Valve’s OWN description, and it is the MOST anyone has confirmed.
Sources: Valve Proton changelog, Proton Experimental entry dated Oct 2, 2026; ValveSoftware/Proton experimental_11.0 commit history (Sep 14 to 22, 2026); Proton README, runtime config options; Proton releases page (11.0-2, Aug 21, 2026); MIXED (Oct 7, 2026).