SteamVR 2.17.10 Fixes AMD Linux Crashes and Changes CAS

Valve has moved SteamVR 2.17.10 to the stable channel with a compact set of fixes that matter disproportionately to Linux VR users and Steam Link streaming. The September 18 hotfix fixes two separate crash issues affecting AMD GPUs on Linux, according to Valve’s release notes.

Valve does not identify the affected Radeon models, Mesa versions, distributions, or exact crash conditions. That makes the fix important but deliberately narrow: the changelog confirms two AMD-on-Linux crash paths were corrected, not that every SteamVR stability problem on Linux has been solved.

The timing is notable because SteamVR 2.17, released September 10, expanded Linux wired-headset support and made several streaming changes around the Steam Frame launch. A regression that can crash SteamVR on AMD Linux systems therefore cuts directly across Valve’s broader effort to make Linux a more credible VR host platform.

SteamVR 2.17 introduced Contrast Adaptive Sharpening before Steam Link video encoding. Version 2.17.10 changes the default: CAS is now off unless the user enables “Sharpen image before encoding” under SteamVR Settings and Steam Link.

Valve also narrows where the filter runs. CAS now applies only to VR game content, excluding the SteamVR dashboard, overlays, and desktop view. That distinction is sensible for a streaming pipeline because a sharpening pass intended to recover perceived detail in rendered game imagery does not necessarily improve text-heavy interfaces or desktop content, and it can make compression artifacts or high-contrast edges more obvious.

Valve does not publish image-quality measurements, encode-efficiency data, or a performance explanation for changing the default. It would therefore be speculation to claim the switch was made because CAS measurably hurt latency, bandwidth, or visual quality. What is confirmed is simply that Valve changed both the default and the surfaces to which the filter applies.

The hotfix also repairs the per-application Motion Smoothing “Force Always-On” option, which Valve says was being ignored. This is separate from the Steam Link CAS change: Motion Smoothing controls frame presentation behavior, while CAS is a sharpening pass in the streamed image path.

For users who intentionally force Motion Smoothing for a particular title, 2.17.10 should make the stored per-app choice effective again. Valve does not attach a benchmark or broader performance claim to the fix, so it should be treated as restored setting behavior rather than a general SteamVR performance improvement.

For developers, Valve changes the frame_controller_valve OpenXR interaction profile component name from “bumper” to “shoulder” to better align with the OpenXR specification. Valve explicitly keeps accepting suggested bindings that use the older “bumper” name for backward compatibility.

That compatibility promise matters more than the terminology change itself. Existing applications do not need to be treated as suddenly incompatible because they used the old suggested binding, while new integrations can move to the revised component name.

SteamVR 2.17.10 is not a feature release, but its Linux fixes land at an important point for Valve’s platform. Steam Frame and Valve’s renewed SteamOS hardware push make the quality of the Linux VR host stack more consequential than it was when Windows was effectively the default SteamVR environment.

Two fixed crash paths do not establish parity with Windows, and Valve still has substantial compatibility work ahead across drivers, headsets, compositors, streaming, and games. The useful signal is more modest: a launch-period AMD Linux regression reached the stable hotfix quickly, while Valve simultaneously tightened Steam Link image processing and preserved backward compatibility in the new controller profile.