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.
Sure it behaved normally on all OS versions up to 3.4 and now it will cause issues. Definitely the case. Also “without sufficient evidence” I guess original thread and several videos which valve decided to ignore but asking for new videos is not “sufficient”
Valve simply shipped unfinished OS build because of OLED.
Like someone on github said I don’t see how reporting issue (which is live for more than a month) on per game basis would help.
You don’t see how it would help, but thing is, you aren’t an OS engineer. The people at Valve, however, are. So if they say they would like that info, it likely means they do in fact see how it could help.