Proton Experimental adds early 32-bit OpenXR support, and it needs PROTON_USE_WOW64
Proton Experimental has picked up 32-bit OpenXR, which is what an older Windows VR game compiled as a 32-bit executable needs before it can find a runtime under Proton at all. Valve's Proton Experimental changelog, stamped 2026-10-02 and read at 22:33 UTC on October 6, gives it one line: "Added early support for 32bit OpenXR (requires PROTON_USE_WOW64=1 on x86)."

SteamOS is the Linux host Proton's compatibility work lands on first. Image: Valve
Early support is Valve's own hedge and the changelog does not go past it. No game is named, no success rate is given, and nothing is said about when or whether the work leaves Experimental.
No headset is named either. What the entry covers is the game executable rather than the hardware at the other end of it, and a 32-bit build is a property of the game.
Valve requires a flag its own README never lists
Nothing switches itself on here. Proton reads its runtime options from environment variables, and Valve's own README tells owners to put one into the Set Launch Options box in a game's Properties dialog, in the form "PROTON_USE_WINED3D=1 %command%".
For every game at once, Valve points instead at renaming "user_settings.sample.py" to "user_settings.py" inside the Proton installation in a Steam library and editing that. Either way it is a deliberate act, not something a 32-bit VR title picks up by being launched.
That README lists 25 runtime environment variables, from PROTON_LOG through to PROTON_USE_XALIA, and PROTON_USE_WOW64 is not one of them. Valve requires a variable its own documentation never explains, which leaves "requires PROTON_USE_WOW64=1 on x86" as the whole of what an owner is told.
Four wineopenxr commits carry the work
On Valve's experimental_11.0 branch, the change arrives as four commits from Paul Gofman: "wineopenxr: Implement 32 bit support and build 32 bit library.", "wineopenxr: Use UNIX_CALL_CHECKED in manual calls.", "wineopenxr: Build without WINE_NO_LONG_TYPES." and "wineopenxr: Update to 1.1.63 registry version."
wineopenxr is the component that presents an OpenXR runtime to a Windows game running under Proton, and until now it was built only as a 64-bit library. The last of those four commits brings it up to OpenXR registry version 1.1.63, which is the version of the OpenXR specification registry the layer now matches.
Those commits are about 10 days older than the changelog stamp, so October 2 is the day the work became something an owner could switch on rather than the day it was written.
Experimental is not the Proton most owners are running
Proton Experimental has to be chosen in a game's compatibility settings before any of it reaches a title. The newest stable release is Proton 11.0-2, published on August 21, and Experimental carries every change in it on top of its own.
Valve's wording is also specific about the architecture: the flag is needed "on x86", and the changelog says nothing about ARM64. That is the architecture a Steam Frame runs standalone, and Proton's Arm groundwork has been arriving separately, most recently as the first ARM64 build of Wine Mono in the September 21 Experimental update.
For a Linux desktop, the practical ceiling is still everything else in the chain. Valve has confirmed that VR streaming to a Steam Frame from a Linux host needs SteamVR started by hand, and a 32-bit OpenXR layer does not touch that. What the changelog promises is support, early support, and not one word about how any of it performs.