Valve has released SteamOS 3.8.28 to all users, and one line in its General section is the one worth reading twice. The changelog says Valve “Greatly improved VRAM management, improving performance and stability in cases where VRAM is limited”.
Valve attached no figures to that claim. There is no frame rate, no percentage and no memory figure anywhere in the notes.
What Valve's changelog says about VRAM
The VRAM entry sits directly beneath a second graphics item. Valve says it “Updated Mesa graphics driver to a new major release, containing many ray-tracing performance improvements, as well as other performance and functionality improvements”.
Valve does not name the Mesa version. The notes say only “a new major release”, so the exact number is not published.
Both entries live in the General section, which Valve uses for changes that apply across the whole branch rather than to one device.
The line first appeared in a beta build three months earlier
The wording is not new. It appeared word for word in Valve's SteamOS 3.8.20 Beta notes, posted on June 30, 2026.
That beta post separated its two new items, the Mesa update and the VRAM change, from a list of fixes already on stable. The VRAM work was beta-only at that point.
Stable users then waited about 12 weeks for it. SteamOS 3.8.28 is the first stable build since 3.8.16 on July 17, 2026, and Valve's scope note says the notes “contain all changes since the previous SteamOS 3.8.16 stable release”.
So this release bundles roughly ten weeks of beta channel work into one push. Most SteamOS Beta users have had the VRAM line since late June.
Which machines actually receive it
The General section covers the shared x86-64 SteamOS branch. That means the Steam Deck, the Steam Machine and the third-party handhelds Valve supports.
The same notes name the Deck directly elsewhere, fixing “a rare Steam Deck issue where fan speed would revert to BIOS control until a reboot”. The Steam Machine also gets its own Firmware 108 section, covering a wake-after-sleep bug and degraded CPU performance after waking.
Non-Valve devices get a separate section naming MSI Claw, OneXPlayer, Lenovo Legion Go and AYANEO Pocket S2 fixes. Those handhelds run the same branch, so the General changes reach them as well. The release also carries the sleep and resume performance fix for systems with AMD discrete GPUs.
One caveat on wording. These are APU designs whose graphics share one physical memory pool with the CPU, but Valve never frames the change that way and does not explain the mechanism.
Steam Frame is not part of this release
This is the part that is easy to get wrong. The Steam Frame runs its own SteamOS branch, versioned 0.x, independent of the 3.8.x line used by the Deck and the Machine.
Valve's own headset post is titled “SteamOS 0.3.0 (for Steam Frame) has just been released for all users”. That build arrived on September 17, 2026, and brought faster charging and graphics work to the headset. Its full changelog contains no VRAM management line.
The only Frame item inside 3.8.28 is “Preliminary support for the Steam Frame Wireless Adapter”. That is a driver on the PC, Deck and Machine side for the streaming dongle, not a change to the headset's operating system.
The headset branch has already moved on by itself. Valve posted SteamOS 0.4.1 Beta for Steam Frame on September 26, 2026, covering spectator view, a dominant-eye setting and dashboard fixes.
What Valve has not published
No performance data exists for the VRAM change. Anyone promising a specific frame-rate gain is going past the changelog, which offers one qualitative sentence and nothing more.
Valve has also not said which games benefit, or how much of any gain comes from the Mesa update rather than the memory work. The Mesa version number remains unlisted.
This may also be a short-lived newest stable. SteamOS 3.9.2 Beta went out the same day, with the 3.9 line rebasing on Linux 7.2 and moving Desktop Mode to Plasma 6.7.3, and Valve has given no date for 3.9 reaching stable. All of the above was checked on September 26, 2026.
Discussion (0)
Be the first to comment.