Der Artikel kann nur mit aktiviertem JavaScript dargestellt werden. Bitte aktiviere JavaScript in deinem Browser und lade die Seite neu.
Both of the Linux fixes Valve said were coming to SteamVR have arrived, in a beta. SteamVR beta 2.18.3, posted on October 10 at 00:50 UTC, lists them together under Steam Link: “Fixed colors being greyer than they should be when using certain AMD GPUs” and “Removed requirement for VK_KHR_maintenence_9 on Linux to allow for compatibility with older graphics drivers”.
An opened Steam Frame accessories box from Valve. The two fixes sit on the PC side of a Steam Link VR session rather than in the headset. Image: Valve
Valve then went back to the reports to say so. On October 10 at 07:36 UTC, a SteamVR developer at Valve added one line to a bug report the company had closed a week earlier: “This should be fixed in 2.18.3”. The account is danwillm, whose GitHub profile describes him as developing Steam Link and SteamVR.
The Vulkan requirement is gone, and Valve misspells it
Issue 941 was opened on September 7 at 20:34 UTC by an owner whose Steam Link VR session died at device creation with VK_ERROR_EXTENSION_NOT_PRESENT on an Nvidia 580 series driver. The missing piece turned out to be a Vulkan extension the older driver branch does not carry, and Valve closed the report on October 3 with a commitment: “We have removed the requirement for VK_KHR_maintenance9 and this will be available in the next SteamVR beta update.”
The release note spells the extension VK_KHR_maintenence_9. The extension is VK_KHR_maintenance9, which is how the developer spells it on the tracker and how the Vulkan loader reports it, so anyone searching Valve’s notes for the real name finds nothing. It is a typing slip in a changelog rather than a fault in the build, and the promise it is delivering on dates from October 3.
The grey AMD picture closed on October 10
The colour fault had its own report. Issue 953, opened on September 19 about a duller, flatter Linux picture than the same hardware produced on Windows, was closed as completed at 05:33 UTC on October 10 after one of the people on it reported the build had put the colours right. Valve keeps the scope narrow in the note itself, which says “certain AMD GPUs” and names no model, and the company had pointed at a video encoder bug on AMD 9000 cards as the likely cause on October 7.
A third report is still open and is being handled more cautiously. On a crash report filed on October 7 about the SteamVR compositor dying when a Proton game connects on a Radeon card, the same developer wrote at 05:52 UTC on October 10: “Please could you try 2.18.3 beta and let us know if it works for you? There were some related fixes in it and I believe they might resolve your issues.”
That hedging runs through all of it. “Should be fixed” and “might resolve” are as far as Valve goes, and it is asking owners to confirm rather than announcing the faults closed. All three reports and the release note were read at 21:37 UTC on October 10.
Still a beta, and no date for stable
2.18.3 carries two more Linux lines beyond the pair Valve promised: “Fixed game crash when an invalid texture size is submitted” and “Fixed OpenXR games crashing on launch if SteamVR wasn’t already started”. The second means an OpenXR title can start without SteamVR running first.
None of it is on the stable branch. Valve’s SteamVR news feed, read at 21:36 UTC on October 10, still tops out at “Introducing SteamVR 2.17” from September 10 at 21:55 UTC and “SteamVR Hotfix 2.17.10” from September 18 at 17:28 UTC for stable releases, with every 2.18 post since titled “SteamVR Beta Updated”. Valve names no date for 2.18 leaving beta, which leaves Linux owners with a fix they have to opt into to get.
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.