Valve has shipped ANOTHER SteamOS beta for Steam Frame, and this one carries EXACTLY ONE NEW line. SteamOS 0.4.5, posted to the Frame beta channel at 02:15 UTC on October 7 (10:15 p.m. ET on October 6), promises “improved color clarity during VR streaming” and calls the problem it fixes a “headset chroma REGRESSION.” That word MATTERS. It means an earlier build made streamed COLOR worse, and Valve’s notes do not say WHICH build, WHEN it started, or what owners should have NOTICED.
What the 0.4.5 Notes Actually Say
The SteamOS 0.4.5 Beta post on Valve’s Steam Frame news hub lists a SINGLE item under “New in 0.4.5”: “Improved color clarity during VR streaming (fixed headset chroma regression).” EVERYTHING else in the post is a CUMULATIVE recap of earlier 0.4.x betas. Owners still have to OPT IN under Settings > System > System Update Channel; the STABLE channel does NOT get it yet.
Chroma is the COLOR half of a video signal, carried separately from brightness. Streaming encoders COMMONLY store it at LOWER resolution than brightness to save bandwidth, so a chroma fault tends to show up as softer edges on SATURATED colors, SMEARED text on colored backgrounds, or tints that look slightly OFF. That is general background on video compression, NOT Valve’s diagnosis. Valve gives NO symptoms, NO affected GAMES, and NO description of what changed inside the streaming pipeline.
The timing narrows the window only a LITTLE. SteamOS 0.4.4 landed at 23:14 UTC on October 5, roughly 27 HOURS before 0.4.5, and its notes said NOTHING about COLOR. Neither did the 0.4.1, 0.4.2, or 0.4.3 notes. So the regression went IN without a changelog entry, and came OUT with one.
A Second Color Fix Shipped the Same Evening
Three hours earlier, at 23:23 UTC on October 6 (7:23 p.m. ET), Valve pushed a Steam Client update for Frame to ALL users, not just the beta channel. Most of it is HOUSEKEEPING: Settings now shows the user-visible serial number instead of the SoC serial, the Guided Tour appears for EVERY new account, the Wireless Adapter’s manual setup shows the CORRECT Wi-Fi channels in all regions, and the Streaming Menu gains a spectating indicator with a STOP button.
Buried under its Remote Play heading is ANOTHER color line: “Improved color accuracy when streaming an OpenGL game.” Valve does NOT connect it to the headset chroma fix, and the two notes describe DIFFERENT paths. One covers VR streaming into the HEADSET; the other covers REMOTE PLAY of OpenGL titles. Still, it means Valve shipped TWO separate streaming-color corrections to Frame owners within roughly THREE hours, and explained the cause of NEITHER.
The PC Half of the Streaming Fix Is Still a Beta
The 0.4.5 recap repeats a CAVEAT that has now sat in Valve’s notes for a WEEK. The “Error 17” streaming fixes only FULLY work if the PC is ALSO on SteamVR 2.18.2, which Valve says is “available on the SteamVR [beta] branch.” Valve posted 2.18.2 to that BETA branch on October 1. As of October 7, SteamVR’s own news feed shows NO newer build, beta or stable; the most recent STABLE entry is the 2.17.10 hotfix from September 18.
In PRACTICE, a Frame owner who wants the full set of streaming fixes is running TWO betas at once: SteamOS 0.4.5 on the headset and SteamVR 2.18.2 on the PC. We have covered that pairing before. What is NEW is that the headset side keeps MOVING while the PC side has stood STILL for six days.
Five Betas in Eleven Days
Valve’s Frame news hub shows the 0.4 beta line moving FAST. SteamOS 0.4.1 posted on September 26 (UTC), 0.4.2 on September 29, 0.4.3 on October 1, 0.4.4 on October 5, and 0.4.5 on October 7: FIVE beta builds in about ELEVEN days for a headset that LAUNCHED on September 17. GamingOnLinux and LinuxCompatible BOTH reported the 0.4.5 build on October 7, and LinuxCompatible likewise identified the color fix as its ONLY new item.
The 0.4.5 post also quietly REFILES earlier items. The presence-sensor sensitivity setting, which 0.4.4 billed as its HEADLINE addition, now sits under the recap’s “Power” heading alongside the claimed battery gains of UP TO 12 percent. Valve’s caveat on that battery figure is UNCHANGED: results “vary depending on framerate and content.”
What Owners Should Do
If you stream PC VR to a Frame and colors have looked WASHED or SMEARED over the past week, 0.4.5 is the FIRST build that CLAIMS a fix, and it is a REASON to try the beta channel. If you stay on stable, nothing in Valve’s notes says the regression ever reached you; Valve simply does NOT SAY. Either way, the useful TEST is concrete: compare small colored text and saturated UI elements before and after the update, on the SAME game and the SAME network.
The bigger QUESTION is disclosure. A one-line fix for a regression that never appeared in ANY changelog leaves owners UNABLE to tell whether the problem they saw was this one. Until Valve publishes WHICH build introduced the chroma fault and when 0.4.5 reaches STABLE, the ONLY reliable record is the beta notes themselves, and they are SHORT.