It’s a pretty bad bug, and to have it at launch of the OLED too really stinks. If you are using and LCD model you should be able to roll back to before 3.5 and for anyone with an OLED model we are stuck with it since we need 3.5 or newer for this model.
I hope Valve are treating this as a priority, but it does make me worry slightly since the reading up I have done on this is showing that the big has been present for quite some time in preview / beta.
Is this the same thing as the GPU downclocking to 200 and the CPU to 400mhz? I get this on my LCD deck typically only when the battery is at 10%
I got my OLED model yesterday, and sure enough the bug is happening in my unit. I went straight to setting the GPU clock manually and that has fixed it for now, thankfully. At least in the two games I’ve tried so far. (Sekiro and OTXO)
I’m having this bug after 15-30 minutes in Gladius, but 1.5 hr CP2077 is stable as usual.
Definitely something messed up with the software.
Does this happen on Windows? I don’t use SteamOS on my LCD (just because a lot of my games wouldn’t work due to anticheat) They do now, but never bothered going back after the Windows 11 driver update that fixed a lot of the issues specifically for Windows.?
Somehow I never heard about the bug before 3.5 released to Stable, and I used it on Preview for months. Valve may not have realized the scope of the problem until it reached Stable.
We got a few comments on the GitHub page about this from Nephyrin, a Valve developer, but not a definite “we’re working on this.”
There’s active discussion on the Steam forums, too, but still no Valve response and there’s a lot of argumentative back-and-forth among users. The problem is that it doesn’t occur on all units.
My guess? Valve is working on this, but they haven’t found any reliable way to re-create the bug, which is the first step in debugging. They’re staying silent because saying “We have been unable to reliably reproduce the issue” will confuse users into thinking they’re denying the problem, but saying “We’re working on it” will mislead users into believing that a fix is right around the corner.
The workaround for the time being is to manually set the GPU clock. I know, it sucks. I wish I could offer better advice, but I haven’t run across any and I can’t troubleshoot it myself because I haven’t encountered the issue.
Having this issue and the issue with flash memory not being found through the USB
Yeah it sucks. But nothing we can do right now beyond setting manual frequently. Apparently it was also seen on the Ally too which is interesting.