- 3 Posts
- 11 Comments
SunlighthellOPBtoSteam Deck@hardware.watch•200/1040 GPU frequency bug is not fixed in 3.5.7 stable.English
1·2 years agoI 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.
SunlighthellBtoSteam Deck@hardware.watch•Steam deck update 3.5.7 still not fix the micro sd card not getting recognized (atleast for me)English
1·2 years agoCannot even apply the update lol, getting stuck at 0% then giving error, restarting or updating apps in discover had zero effect on that
SunlighthellBtoSteam Deck@hardware.watch•SteamOS 3.5.7 Update fixes OLED USB Drive issues.
1·2 years ago200/1040mhz bug?
SunlighthellBtoSteam Deck@hardware.watch•Persistent 200/1040 mhz GPU Clock, Audio Crackling, and Dock DisplayPort Bugs from Steam Deck 3.5 Beta/Preview Affecting OLED Models running 3.5.5. – Valve's Silence Raises ConcernsEnglish
1·2 years agoUpdate: Valve is actively communicating in the GitHub thread, currently working on pinpointing the issues with frequency scaling and audio issues. Valve Employee Nephyrin on GitHub states:
I don’t know where you found “actively communicating” considering that Valve was completely absent from these threads (they answered only after several threads including your popped out on reddit), but his answers seems more like damage control. He stated things that are not true (that 200/1040 bug is just slow drawing from overlay) while you even have video in your post that proves otherwise.
The thing is: probably this bug affects much more people but some of them just don’t really bother with overlay and state that they don’t have it (sorry but people like that are the worst, because they lack any tech knowledge but still voice their opinion), similar to how people pretend they have “smooth” (no stutters) framerate on some games where even people with 7800x3d and 4090 (like Dead Space remake) have issues and when asked to enable RTSS overlay they disappear from thread.
I perfectly understand people’s desire to defend Valve and tbh I think Valve will figure these issues out and actively working to resolve it, still they picked this update for almost a year then suddenly released it with few major bugs only because they wanted to ship OLEDs before holidays in USA. People were also actively downvoting all threads listing these issues as I stated here, like they do with almost every thread listing issues if it’s not made into stupid meme.
SunlighthellBtoSteam Deck@hardware.watch•Persistent 200/1040 mhz GPU Clock, Audio Crackling, and Dock DisplayPort Bugs from Steam Deck 3.5 Beta/Preview Affecting OLED Models running 3.5.5. – Valve's Silence Raises ConcernsEnglish
1·2 years agoBut hey, Pierre tweeted that they attempted to fix not working microphone in 3.5.6 preview, and all this sub was busy downvoting almost all post with these concerns while hyping OLED.
SunlighthellBtoSteam Deck@hardware.watch•Issues happening to those updating to 3.5.5 (stable)English
1·2 years agoI love how community downvote these concerns to hell. TBH my excitement changed to disappointment. Valve pickled this update for almost a year. Obviously (now) waiting for release of second SD revision, only to release it suddenly from preview straight to stable (no beta lol) ignoring several issues (you can check on their tracker). I used to Blizzard doing things like that all the time but not Valve.
SunlighthellBtoSteam Deck@hardware.watch•3.5.5 Stable Updaet - GPU 200mhz - 1040mhz bugEnglish
1·2 years agoWas surprised they skipped beta. Turns out it’s nowhere near “stable”
Yep. For me it starts fine but becomes crackle mess after a while
SunlighthellBtoSteam Deck@hardware.watch•Valve says it is committed to the Steam Deck, has a "road map"English
1·2 years agoValve, where’s 3.5? =(
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.