Valve released two beta builds timed to land a minute apart, signaling that it now treats the Steam Frame glasses and the PC's SteamVR runtime as a single connected system. The most concrete change targets the "Error 17" streaming connection fault, but Valve warns the fix only works if you update both SteamOS 0.4.3 and SteamVR 2.18.2, since an update on one side alone leaves the bug intact. Other highlights include up to 12% better battery life, eye-openness data exposed via OSC with a later OpenVR SDK upgrade, and a wireless adapter fix for users in certain countries. You can opt into either beta through the Steam client or the Frame's update settings, and should report issues in the SteamVR Bug Report forum rather than the news thread.

Valve ships paired SteamVR and SteamOS beta updates for the Steam Frame

Valve released two beta builds, and deliberately timed them to land a minute apart. The two posts cross-reference each other directly, which is a clear signal that Valve now treats the glasses and the PC runtime as one connected system rather than two separate products.

If you follow the Steam Frame, you probably want to see that kind of coordination. The device isn't a standalone machine. It's a streaming display and input peripheral that leans on the same software stack powering SteamVR back on your computer. A streaming fix on the glasses is often dead weight unless the matching SteamVR build is also running on the host. That's the gap Valve is trying to close.

Fixing the connection on both ends

The headline item is the ongoing fight against "Error 17," the connection fault that cuts VR streaming mid-session. This update pushes more fixes into it, but Valve spells out the catch plainly: Steam Frame users have to opt into SteamOS 0.4.3 or higher to actually see fewer error 17 problems. On the PC side, you need SteamVR 2.18.2 or later. Update only one and the bug survives in the gap between them.

It's a genuinely cross-device fix, and that's a sign the platform is growing up.

There's also an eye-tracking angle worth watching. SteamVR now surfaces eye-openness data through OSC when streaming from the Frame, though that path also needs SteamOS 0.4.3. In a later release, eye openness moves to the OpenVR SDK, which is the more useful piece since it lets PC developers build against eye state directly. As an aside, OSC is the protocol music and art folks use for live-show automation, so it's a slightly unusual home for eye-tracking data.

Oh, and a hotfix killed a green- or black-screen glitch tied to SteamLink on Linux.

Battery, eyes, and global Wi-Fi

For a wearable, battery life is everything, so it makes sense that it leads the SteamOS changelog. Valve claims up to a 12% improvement in power efficiency during both streaming and local gameplay. Results vary depending on framerate and content, which is a fair caveat, but a double-digit gain is still a double-digit gain.

Valve also added a small accessibility tweak: limit eye tracking to a single eye through VR Settings => General => Track Dominant Eye Only, once you flip on show advanced settings.

Then there's a wireless adapter fix for users "in some countries," which almost certainly means region-specific Wi-Fi channel or regulatory differences that previously broke streaming. A targeted patch like that is what separates a genuinely global product from one still tuned for a single market.

Notice the mirror work. Controller-binding fixes for games like Google Earth VR and Thumper, plus dashboard recentering, throttling selection, and grab/resize focus improvements, show up in both changelogs. The SteamOS post even states plainly that "this OS release includes SteamVR (2.18.2)." The two updates are engineered as a pair.

The bigger picture

Taken together, these read less like patch notes and more like one coordinated rollout. The Frame's whole bet is that the future of immersive computing is connected—glasses streaming from a PC and tracking your eyes on the same software as SteamVR. Shipping matching builds at the same time and telling you both must be installed makes that point unmistakable.

Is it a bit much to coordinate two betas down to the minute? Maybe. However, at the same time, the alternative is a broken streaming experience nobody wins, and at least this way the fix actually sticks. Head here to the Steam News page if you want to read both posts straight.

How to opt in

Open the Steam client, head to SteamVR Properties, and check the Beta tab for SteamVR. For the Frame, go to Settings => System => System Update Channel and pick the Beta channel. If either update misbehaves, Valve wants you to post in the SteamVR Bug Report forum with a system report attached. Replies in the news thread itself aren't tracked for bug reporting, so go ahead and save your complaints for the forum.

Here here to the SteamOS 0.4.3 (Beta) for Steam Frame announcement and here to SteamVR Beta 2.18.2 announcement.