SteamVR beta 2.19.1 takes aim at the blur between your gaming PC and your headset: small text, fine coloured details and the dashboard you keep leaning towards to read. Valve released it on 2 November, with a useful qualification for anyone who has already tuned Steam Link. Your manual resolution settings survive the update.
To try the new defaults, those overrides need to go back to Auto. That makes this a good moment to check your settings before deciding whether the beta has helped. Valve also provides a Default-versus-Legacy switch, so you can compare its new streaming approach with the previous one on your own setup.
What SteamVR beta 2.19.1 changes
Valve’s release notes describe improvements across streamed VR games, desktop streaming, the SteamVR interface, third-party overlays and the theatre screen. The changes include better colour filtering before video is encoded, improved detail around saturated edges and sharper images outside the central foveated region.
Foveation concentrates image quality in a particular area of the view. Here, Valve is also changing how the system interface is drawn: it can use the original image textures directly, cutting out an intermediate image and another scaling step. The intended result is cleaner text and interface detail along the way.
That reaches beyond a single game adding support. Our earlier coverage of Half-Life: Alyx and PC foveated rendering concerned a game-specific update. This beta works on SteamVR’s streaming and interface machinery, which can affect the menus and overlays surrounding many games.
Steam Frame gets a higher default encoded-video size, moving from 1152 to 1216. Valve also raises the recommended rendering resolution for streamed PC VR applications and removes the GPU performance test that previously selected that recommendation. Higher defaults are a quality choice; they are not evidence that your PC has suddenly gained spare graphics power.
Check Auto, then compare Default and Legacy
The two controls answer different questions. Auto lets you try the new default resolution values. Default and Legacy let you compare the new streaming-quality implementation with its predecessor. Changing one is not a substitute for checking the other.
First, note any encoded-video size or render-resolution values you set manually. Valve says those values are preserved. Reset them to Auto if you want to evaluate the new defaults; keeping a record makes it easier to return to your previous setup afterwards.
For the quality comparison, use the host PC’s Steam Link settings, then Advanced, then Stream Quality. Default selects the new approach; Legacy reproduces the previous streaming image quality. Use a familiar scene with readable text and coloured detail, and change one setting at a time so you can tell what made a difference.
Valve has not supplied a universal frame-rate gain or a promise that every PC can run the higher values comfortably. If your existing configuration was carefully balanced, preserve it before experimenting. The sensible test is whether the picture improves while your own games remain comfortable to play.
The beta is optional. Valve links its SteamVR beta instructions from the announcement. Owners comparing Steam Frame with Meta Quest 3 should read this as a software change to streaming, rather than a new hardware specification or a reason to replace a working headset.
A sharper interface, with more control
Another new option, Preferred Foveated Sharpness (System UI), trades a narrower, sharper area against a wider one for the SteamVR interface. The “System UI” part matters: this is not a blanket control for every game’s graphics. Eye-tracking headsets also gain a prompt asking whether PC applications can receive eye-tracking data.
Linux users receive separate compatibility changes, including support for Steam Runtime 3 clients and launching non-Proton OpenXR games without first starting SteamVR. Valve’s continued software work also gives context to our reporting on Index support after hardware production ends. A new headset cycle does not make the software underneath it incidental.
The best feature here may be the ability to compare. A sharper streaming pipeline is welcome; a visible fallback makes it easier to judge without guessing. Check your old overrides, try the new values deliberately, and let the headset view settle the argument.



The conversation
Be the first to join the conversation.