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:

  1. Bug exists since 3.5.1 preview

  2. 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.

  • TrenchmanBEnglish
    1·
    1 year ago

    I’ve noticed it’s not just 200 or 1040? Like I’ve seen instances of it being at 604 or 400 ish. I think there’s more to this issue than meets the eye and part of it might just be efficiency improvements that MangoHUD is not reporting correctly.