Valve closed bug report thread on github while issue still persists in latest “stable” steamos 3.5.7.
From the thread on github with bug report you can see two things:
-
Bug exists since 3.5.1 preview
-
Valve denying this is a bug. Instead they tell people that it’s only affecting gpu clock display in performance overlay and try to convince people that it’s not affecting performance.
I don’t know why they do this but you can easily check that Valve is not telling truth and this is in fact affect performance in many games. You can confirm this either by locking gpu to 1600 mhz or by rolling back to 3.4 steam os where bug is not present.
This behavior rising concerns, because 3.5 Steam OS is far from “stable” if you compare it to 3.4. Issue affects both LCD and OLED steam decks.
It would be nice to get coverage and noise from channels like Gamers Nexus but as of now I don’t see that any major youtube tech channels picked up this issue.
Valve does need to look at this and then explain - in way more detail - what’s causing the behaviour people are experiencing. Simply saying “none of this is related and we can’t replicate the bug” isn’t going to convince anyone.
However, having gone through the Steam threads too many people are saying for example “BOTW now runs badly now”, and that doesn’t help Valve engineers. Emulators - especially Yuzu and Ryujinx - are in a constant state of flux and numbers pulled from those are going to be side-eyed by the engineers.
People need to start posting more videos of MULTIPLE of their STEAM games running well on 3.4 and then running badly on the current 3.5 build with the overlay open. Valve needs to be shown data from a source they can 100% replicate.