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.

  • wichu2001@alien.topBEnglish
    1·
    1 year ago

    do people really feel the performance affected, or do they see 200/1040 on overlay and are like “yup i have it too”?

    • Televana@alien.topBEnglish
      1·
      1 year ago

      Yeah I went from playing Skyrim docked @ 1080p/60fps to 32 fps after the update, the performance hit is brutal.

    • JudgeZetsumei@alien.topBEnglish
      1·
      1 year ago

      Definitely felt it. I had to open the overlay to see wtf was going on because cyberpunk was a locked 30fps(LCD model) and now it’s all over the place (OLED model).