SteamOS icon indicating copy to clipboard operation
SteamOS copied to clipboard
verified publisher icon ValveSoftware

Gaming mode manual GPU clock setting carries over into desktop mode

Open Sunspark-007 opened this issue 1 year ago • 3 comments

Your system information

  • Steam client version: 1725654351 Fri, Sep 6 16:08 UTC -08:00
  • SteamOS version: 3.4
  • Opted into Steam client beta?: Yes
  • Opted into SteamOS beta?: No
  • Have you checked for updates in Settings > System?: No

Please describe your issue in as much detail as possible:

I thought when in desktop mode settings set in the Performance QAM would not carry over from the gaming mode, but they do. I noticed it when I finally got around to checking the GPU frequency statistics, etc. and noticing on a reboot that it seemed locked to a specific number without changing.. then I noticed that this # was the same number set in gaming mode for manual GPU frequency.

Steps for reproducing this issue:

  1. Set a manual GPU clock in gaming mode.
  2. Switch to desktop mode.
  3. Launch system monitor or mission control, and look at the GPU frequency clock. If set to automatic it should show 200 MHz, but if it is not on automatic then it will be locked to the number set in the slider.

Sunspark-007 avatar Sep 09 '24 23:09 Sunspark-007

One important thing to mention also, automatic functions poorly as well. It goes between 200 MHz and 1 GHz. If you want it to go higher, let's say 1600 MHz, you need to manually set the clock in gaming mode first. Desktop mode is capped at 1000 MHz otherwise.

Sunspark-007 avatar Sep 10 '24 17:09 Sunspark-007

Is there a reason you're still on SteamOS 3.4? SteamOS Stable has been on version 3.5.x for nearly a year now and the Preview branch is on SteamOS 3.6.12. Both of which have addressed this bug as far as I know. Might be worth contacting Steam support if you're unable to update for some reason.

matte-schwartz avatar Sep 10 '24 19:09 matte-schwartz

The reason is because 3.5 when it came out was very problematic for many people and this situation lasted for a long time with many complaints about clocks, and other issues etc. After x time I was like, well 3.6 is in preview, it'll be out soon enough, and then that started getting delayed more and more because of concerns like the data bug (addressed), etc. I will update to 3.6 if it's stable enough. :)

I'm not the only one, there's a few other people using 3.4 out there as well. I never expected it to take so long, I get the feeling Valve doesn't have many FTEs allocated to the project.

Sunspark-007 avatar Sep 10 '24 23:09 Sunspark-007

In 3.6.20 it still stays at the 1 GHz setting. Shouldn't it spike to 1.6 if needed?

Sunspark-007 avatar Dec 05 '24 02:12 Sunspark-007