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.
I have the steam deck LE OLED and can confirm the following three games only hit 200 or 1040 mhz on my OLED
-Star Ocean Second Story R
-Armored Core 6
- Forza Horizon
When I lock the GPU all issues with perfomance go away but switching to another game after lock puts the manual clock to 200. Im just at a loss with what to do unless waiting for another update is the only way.
UPDATE: As soon as I set the undervolt values to 0 everything is working back to normal I guess this was my issue so weird it gave that static MHZ with undervolting for any who can confirm this on there end hope this helped.