Der Artikel kann nur mit aktiviertem JavaScript dargestellt werden. Bitte aktiviere JavaScript in deinem Browser und lade die Seite neu.
Valve closed the report that a Steam Frame cannot start a PC VR game on an ordinary Linux desktop on September 27, with the fix unreleased, and neither of the two updates it shipped on October 1 lists it. Pick a VR title from inside the headset on a Linux PC that is not running SteamOS and SteamVR never starts, so the game is killed after 40 to 60 seconds while the headset waits on its “opening game” panel.
Every report of this failure comes from a desktop Linux host rather than SteamOS or Windows. Image: Valve
The workaround has not changed either: start SteamVR on the PC first, then launch the game from the headset. Streaming a flat, non-VR game over the same adapter link works normally, which is what makes the failure easy to walk into.
Valve closed the thread before the fix existed
The report on Valve’s SteamVR-for-Linux tracker was opened at 06:32 UTC on September 25 and closed at 08:07 UTC on September 27 by danwillm, whose GitHub profile describes him as developing Steam Link and SteamVR. “A fix for the original issue is currently being worked on, as a result I’ll close this issue but will try to respond here when it is live in a steamvr release,” he wrote. No such reply has appeared.
Two days earlier he had set out the position that Linux owners must start SteamVR by hand: the issue is “known and we are working on a fix”, with no exact ETA, and for now owners should make sure SteamVR is launched before starting a game.
Two missing pieces leave the headset waiting
The owner who filed it traced the failure to two gaps, with logs. The Steam client’s 32-bit watchdog cannot load the vrlink driver because only a 64-bit build ships, logging that the driver library is “not found on filesystem (for this architecture)”, so Steam never starts SteamVR for the headset in the first place.
The second gap sits in Proton, whose OpenVR bridge connects to a running vrserver but will not launch one, logging “Not starting vrserver for VRApplication_Background application”. A Windows VR game under Proton then falls back to a flat window until the timeout removes it, and the report found the OpenXR path no better: with nothing running, the runtime comes back as unavailable rather than being started.
The report also turns up an undocumented Steam launch flag, -vrlinkforceenable, which it says lets the Frame attach to an already-running SteamVR but does not make Steam start SteamVR for a game launched from the headset. Valve has not recommended it.
A second owner reproduced the same logs on Linux Mint with an Nvidia card on September 26, and the original reporter retested on September 28 after swapping his display card for a Radeon RX 9070 XT and reported no change. Every report here is from a desktop Linux host rather than SteamOS, a Steam Machine or Windows.
Neither October 1 release mentions it
SteamVR beta 2.18.2 and SteamOS 0.4.3 for Steam Frame went out a minute apart on the evening of October 1, and between them they cover streaming reliability, battery life, eye tracking and controller bindings. Nothing in either note starts SteamVR for a game launched from a headset.
Valve’s desktop Linux work on the Frame has been arriving in pieces, with SteamOS 3.8.28 bringing preliminary adapter support without VR streaming in late September. Valve said on September 25 that it had made a note of this one, and the note is still all there is.
Note: Links to online stores in articles can be so-called affiliate links. If you buy through this link, MIXED receives a commission from the provider. For you the price does not change.