On github Valve employee was denying bug, telling people that it’s only bug in performance overlay (like it simply slow to draw frequencies in between 200-1040) but was proven wrong in the same bug report thread. Demonstration of this bug presented here.
I just tested it myself and you still get major performance issues with gpu set to auto. “Allow tearing” setting has no effect on this. Even if game can go above 1040 mhz by itself it drop frequencies and frames hard on auto because occasionally it switches to 200 mhz or 1040 in scenes where it should not do that.For example Code Vein is not able to hold stable 60 FPS but able to hold stable 50, with locked GPU you will get flat line on frame time graph. With auto you will get major dips.
I guess we’re stuck with “unstable” stable OS 3.5.5 - 3.5.7 for a while because holidays starting in US.
You must log in or register to comment.
For what it’s worth, I think there are two bugs going on with the GPU clock at the moment.
For some people it’s effecting performance, for others it’s purely visual (which seems to be the group I’m in).
I’ve just updated and I’m still seeing the exact same behaviour (visually jumping between 200 and 1024) as before though, so whatever their temporary fix was, it’s hasn’t worked.
I doubt it. It’s more likely game dependent. In Dark Souls Remastered I have zero issues it seems despite gpu sitting at 200/1040 all the time.
Don’t doubt it. Does my GPU jump between 200 and 1040? Yes, but it also clocks up to 1600 without any issues. I has so far not had any problems with any game I tested.
The scenario shown on the video, it just doesn’t happen to me. The GPU does not get stuck at 1040, it’s doing fine.
Unfortunately for me, me LED Deck runs cyberpunk better than OLED, which is a stuttering mess. I’m sad.
And if you set it to 1600 manually?
Thanks for teying to help, yeah i tried that. Getting a locked 30 feels impossible on OLED. OG deck ran cyberpunk at 30 easily, and stutters were non-existent.
Possibly, I could just be lucky that I’ve not found a game yet that seems to have taken a performance hit on my end.
But even Forza Horizon 5, a game that I would assume would become absolutely unplayable if it dropped down to 200, manages to drop to 200 for multiple seconds at a time and maintain the same frame times that I had in 3.4 for me.
Any steps to avoid this?
Set a manual GPU frequency via the QAM (quick access menu->power->Manual GPU clock)
I’m not upgrading to 3.5 until I see most bugs squashed. Still rocking 3.4.11
Is why my steam Deck clock speeds refused to stick and why binding of Isaac was dipping into the teens??
Easiest way to test is to manually set the GPU frequency to 1600 and test.
I think there are two bugs here we are associating together in error.
- Steam OS fails to properly balance power between the GPU and CPU, when the GPU is left to auto clock. Some games are effected by this more than others. This issue seemed to me to exist in 3.4 as well.
- New to 3.5. Now when the GPU is clocked at or below 1040, instead of reporting the right frequency. SOMETIMES, it reports in intervals of 200 and 1040 instead.
These are my observations on my deck. I may be off base but I think I’m at least close here.
If it were a reporting ossue, shouldn’t it still occur when fo4cing the GOU to a frequency between those two values? If you do that, it shows the number you set it to.
Not necessarily. If you force your GPU clock to 200 mhz, do you ever get frame rate dips as low as those settings produce? If not, I think it’s safe to assume you GPU isn’t actually operating at that clock speed. Also I found this post from a YEAR ago that is talking about issue number 1 and how manual settings must be used to achieve the best frame rates. I am very confident these are two separate issues.
You’re aware the CPU and GPU are the same thing in the Deck yeah?
They’re on the same chip but they are absolutely not the “same thing.”
Who cares I can’t even remote play to dek because it ignores display ress in docked mode and default to 800p even when x11 is reporting 1080p monitor connected with main screen disabled.
sooo, what version does the oled deck arrive? should we just stay in the previous version?
Oled needs 3.5
Is there a way to revert back to a previous version without loosing data?
Taken directly from the steam community
"Note: To revert back, you need to have updated from 3.4.x directly to 3.5.x, no in between.
When shut down, press the 3 dot menu, then press the Power button. Let go of the Power button, keep the 3 dot button pressed.
You will be presented with a new boot menu, choose “Previous A”
you need to do one step more at the end, because if you don’t do it, the moment you shutdown or restart your deck, its going to go back to the 3.5.5, so , in order to avoid that, you need to tell the system that the current BOOT/IMAGE is the priority, and for that, you just have to execute this command in the konsole from the desktop (you will need to create a sudo password before):
sudo rauc status mark-active booted
That way you will keep the current boot/so version even after a shutdown.
What was the version before 3.5.5 on stable? I just want to go back to the previous
3.4.11
On steamOS 3.5.5 LCD model, this bug occurred notably in games like Darksiders 3, sniper elite 4, Shadow of War, deus ex mankind divided - as well as the steam Home Screen. It caused severe stutters/frame pacing issues and audio crackling.
Surprising, the bug did NOT occur in Darksiders Warmastered edition for me - the gpu could automatically scale to any frequency in this game. I wonder why.
I quickly reverted to steamOS 3.4.11 and everything seems to be normal now. No performance issues.
I feel that they might have pushed the 3.5.5 update just to get the OLED versions running. I wonder if the GPU lock was a way for valve to push OLED battery life - but that’s just a speculation.
For some reason , after updating to 3.5.7 my wifi just doesn’t connect…can’t even do any thing
Probably should let them know on the github thread that the fix didn’t do anything, the more people that tell them about it, the more likely they’ll be to have to do something
Since 3.5.5 all my games crash and reset the Deck after a few minutes. It’s made everything unplayable.
Was looking into this bug the other night and noticed that the bug didn’t seem to be there when using the ps3 emulator RPCS3. The gpu used the full range between 200mhz and 1040mhz. Was getting numbers in between these. Very strange but it may be just visual for some and cause performance issues for others.
Got this bug in days gone when enabling sync interval 2 for locked 30 fps. The game perfoms really bad and ui shows only 200 and 1040 mhz gpu. Sometimes it works for couple of seconds, but then goes back
Use this GitHub to express your problem, use proof settings everything that can help
Update, seems like staff closed the original issue report