Valve shipped SteamVR 2.19.1 to the beta channel on November 2, and the headline is a sharper picture on every headset that streams from a PC. The update replaces how SteamVR renders foveated and non-foveated frames, raises the default streaming resolution, and stops running a GPU benchmark to pick that resolution in the first place. It also reworks SteamVR’s Linux packaging and adds three OpenXR extensions, according to the official SteamVR announcement.
The most visible change is the default resolution. Steam Link previously ran a GPU performance test to choose a recommended render resolution for each system, then streamed at whatever that test decided. SteamVR 2.19.1 drops the test and sets a fixed default of render scale 1.5, targeting roughly 1.4 times the headset’s panel resolution. The practical result is a higher, more consistent baseline: two PCs driving the same headset now get the same default instead of two benchmark-dependent numbers. Valve also bumps the default encoded video size on its own Steam Frame headset from 1152 to 1216, a separate lever that controls how much detail survives the trip over the wire.
Under the hood, the sharper image comes from a new system-layer rendering pipeline. SteamVR now renders foveated and non-foveated views directly from their source textures, which removes an intermediate render texture and one resampling pass from the chain. Fewer passes means less detail is lost between the frame a game produces and the frame the headset displays. Valve pairs that with a higher-quality filter for downsampling color before encoding, better brightness preservation along edges between strongly saturated colors, and sharper peripheral detail outside the foveated region. Text and interface elements across the dashboard, third-party overlays, the theater screen, and SteamVR Home all render crisper as a result.
Valve included a before-and-after comparison in the announcement, with 2.19 on the left and 2.18 on the right. Anyone can reproduce the same A/B test at home: on the host PC, Steam Link > Advanced > Stream Quality offers a “Legacy” mode that reproduces the previous image, so the old and new pipelines sit one toggle apart. Users who already tuned Steam Link’s encoded video size or render resolution by hand keep those settings; Valve does not overwrite them, and those users have to switch the options back to Auto to pick up the new defaults.
The settings page itself gets two new controls. A “Preferred Foveated Sharpness” option under Steam Link adjusts the size of the sharp foveated region for the SteamVR interface, trading a narrower, sharper focus area against a wider, slightly softer one. A new “Ultra” tier for overlay render quality applies the improved filtering to the interface and third-party overlays. The rest of the home environment also got polish: the play area floor grid has better anti-aliasing, aurora color movement is calmer during theater transitions, and stars in the construct now keep a minimum brightness so the space never fades to pure black.
Control, tracking, and privacy fixes
The update adds per-application refresh rate overrides and corrects eye view poses for projection layers to include the eye-to-head offset, two changes that matter most to people who mix high-refresh displays with standard ones. SteamVR also improves head motion prediction and eye-tracked foveation alignment during rapid head movement. On the privacy side, when an eye-tracking headset connects, SteamVR now asks before sharing eye-tracking data with PC applications, rather than exposing it by default.
Valve also cleared out a batch of long-standing annoyances: incorrect frame timing at startup, a possible cause of Error 17, IPv4 and IPv6 address comparison bugs when selecting network links, and the laser mouse dragging that grip presses or brief tracking loss could interrupt. Settings sliders no longer extend past their tracks on out-of-range values, Advanced-only sliders hide correctly, and per-application settings now read “Not Supported” when Motion Smoothing is unavailable. Meta Quest owners get a fix for the 72 Hz notification that stayed on screen in Battery Saver mode, and the HTC Focus Vision can now pass face-tracking data over OSC through its face-tracking accessory. Several crashes are fixed, including one during shared resource manager shutdown and another in the web handler on malformed requests.
A bigger Linux change
The Linux side gets the most structural work. SteamVR now runs under the Sniper runtime, the container-based runtime behind Steam Runtime 3, while keeping the scheduling priority SteamVR needs for low-latency tracking. In practice, non-Proton OpenXR games can now launch without SteamVR already running, and the OpenVR and OpenXR runtimes can run inside Flatpak, bubblewrap, and other sandboxes. Valve added a 32-bit OpenXR symlink that Proton can use, and enabled every Render Quality option that was previously disabled on Linux.
The Linux work sits next to Valve’s broader push this fall, from the SteamOS 3.9.5 release with its Linux 7.2 kernel to continued Steam Frame and Steam Deck work. A SteamVR that runs cleanly inside sandboxes and launches OpenXR titles without a separate startup step removes friction for anyone running PC VR on a Steam Deck, Steam Machine, or a non-Valve Linux box.
Developers get three new OpenXR extensions. XR_KHR_composition_layer_cylinder is supported on PC and Steam Frame, XR_FB_composition_layer_image_layout lands on Steam Frame, and XR_EXT_stationary_reference_space is available across the board. None of these change what players see today; they widen the API surface VR applications can rely on, which matters most for engine-level support in the months ahead.
How to get it
SteamVR 2.19.1 is on the beta channel, so it does not reach every headset automatically. Opt in through SteamVR’s properties in the Steam client, then install the update. It follows the 2.18 stable that shipped in late October, and it continues the line of work from the SteamVR 2.17 update that added USB streaming and its own round of Linux fixes in September. Valve routes bug reports to the SteamVR Bug Report forum rather than announcement comments, and asks for a system report where possible.
Because this is a beta, expect less testing than a stable release. The update is aimed at people who want the new streaming pipeline now rather than when it lands in a stable 2.19 build, and the Legacy toggle makes it easy to fall back if anything looks wrong.
