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.
Dude, seriously, my deck is unusable after this update, even on menus the fps drops hard.
Ignoring this issue pre-Stable was bad, pushing it to Stable was bad, and this conveniently timed move to splinter critics into offshoot threads is also bad. It’s not going to go the way they hope unless they deliver a fix quickly.
Yeah Red Dead runs like ASS for me now unless I manually lock the gpu, and you can only do that in gamemode so Desktop is strictly for browsing and Factorio now.
The annoying thing for me which I’ve seen another user mention is when you manually set GPU to 1600mhz it for some reason makes all other games default to 200mhz and you have to manually set them as well. When they are at 200mhz it runs super shit.
Same issue as well.
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.
Valve does need to look at this and then explain - in way more detail - what’s causing the behaviour people are experiencing. Simply saying “none of this is related and we can’t replicate the bug” isn’t going to convince anyone.
However, having gone through the Steam threads too many people are saying for example “BOTW now runs badly now”, and that doesn’t help Valve engineers. Emulators - especially Yuzu and Ryujinx - are in a constant state of flux and numbers pulled from those are going to be side-eyed by the engineers.
People need to start posting more videos of MULTIPLE of their STEAM games running well on 3.4 and then running badly on the current 3.5 build with the overlay open. Valve needs to be shown data from a source they can 100% replicate.
This post, and the comments on the previous post, are worded in a bizarre way that somehow tries to imply Valve is attempting to hide the issue, or purposely not fixing it.
At least 3 Valve developers already commented about it - several people already provided clean captures of the issue. They already claimed to be working on it.
If you look at the thread on GitHub, there’s also a lot of noise, unnecessary comments and redundant videos. So yes, closing the issue and fixing it internally is a good move.
What else do you expect them to do? Broadcast an apology on live television? Replace your Steam Deck with a gold bar? Personally send a DM to every Redditor?
Right? Like what is the conspiracy here? Is Valve plotting something sinister against us via the deck or something? lol
The Deck is how they distribute Bill Gates’ mind-controlling COVID vaccine, now that people picked up on the 5G towers. Riddle me this, who did Gaben work for before founding Valve??
Wak up sheeple!
I don’t think you really have a hard time understanding why hardware sellers do their best to quiet issues that might cost them money until they decide it will cost them less money to address them.
I am still experiencing this issue, I have tried many attempts to recreate the problem to figure out what might be causing it(low battery, pushing GPU, pushing CPU, and even certain segments in a game that frequently ran into this problem) but I still can’t figure out why. It’s very frustrating to experience as it ruins the experience, and I am sad to see this post about valve not addressing this issue
do people really feel the performance affected, or do they see 200/1040 on overlay and are like “yup i have it too”?
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).
Yeah I went from playing Skyrim docked @ 1080p/60fps to 32 fps after the update, the performance hit is brutal.
Redditors: spam GitHub issue making it useless
Valve: close original issue and open multiple other more specific ones
Redditors: surprised pikachu face
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.
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.
I’m getting it on the OLED model in Cyberpunk 2077, The Surge 2, and TOTK in yuzu. Performance has been hit quite badly with tons of microstutters.
I ran Cyberpunk side by side LCD Vs OLED, exact same SteamOS build, exact same graphics settings in both, (game video, game graphics, deck QAM) and on the OLED where I have this issue the frame times are all over the place and it is visibly stuttering whereas on the LCD deck it is a locked smooth consistent 30fps
The clock speed flickers rapidly to 200mhz and back up and now and then also gets locked at 1040mhz whereas on the LCD it adjusts the GPU clock speed in a more normal manner.
Yeah same here. LCD is basically stutter free on cyberpunk2077, OLED drops sometimes into the teens. Makes no sense. Please update me if getting a new deck fixes it for you!
Please, record a video of the exact test you described and just send it to Valve.
I have already recorded a video and intend to do that as part of an RMA process.
“Just send it to valve”. So I can’t post my experience of this in a thread literally discussing this issue?
You can, do you see me stopping you? It simply won’t achieve anything.
I noticed this bug tonight on borderlands three. Game runs much better when I manually change the gpu clock. Hopefully this is fixed soon. Kind of a bummer.
All games will run slightly better if you let them drain your battery as fast as possible