3.5.5 is without a doubt the biggest troll that Valve has ever released.
Github, Reddit and the Steam comments are full of reports of the new fatal 200-1040 MHz GPU bug, which was also brought to Stable with 3.5.5.
And as if that wasn’t enough, no, speakers that worked perfectly before are now crackling like crazy.
And no, that’s not all, the great absolutely overdriven Srgb color mode also applies to your external monitor, which is absolutely, ABSOLUTELY unacceptable.
The Microphone, that has been working perfectly on 3.4x is also now completely unusable.
3.5.5 shouldn’t have been put out like this, and is the biggest Disappointment this year.
That being said, Valve should add a Downgrade function.
You must log in or register to comment.
3.5.5 broke my whole system. I had to re-image the whole operating system.
works on my machine
Seems to vary. It’s fine on my LCD Deck but my OLED deck is unplayable unless I turn on manual GPU clock
The complaints on github are for the preview, not stable. I had the bug for preview but no longer with stable. I trust the programmers over some dude on reddit.
No, the most recent comments on github also cover the stable release. I personally waited for 3.5 to come to stable (have never touched the preview channel) and have had this bug and others over the weekend. Ended up downgrading back to 3.4.11.
The worst bit is this bug has been reported for at least a month and valve has not even acknowledged it yet
I legitimately can’t launch anything since I updated to 3.5.5, and 3.5.7 hasn’t fixed it
I can’t use warpinator with my sd card anymore after the update
I’m surprised this isn’t being talked about more on this sub - as soon as I updated to 3.5.5 on Friday the performance was noticeably worse, and then I saw the GPU clock constantly switching between 1040 and 200 mhz and realised something was up. Have gone back to 3.4.11 and all is fine again
Plus WiFi issues, issues with dualsense connection which was working fine before, dock not displaying on external screen etc. Also the update failed the first time and I had to force the deck to reboot to try again.
Also surprised none of the youtubers have mentioned it. Either it’s not affecting that many people and we’re just unlucky or they’re deliberately ignoring it for /some/ reason. Seems like they rushed 3.5 to stable in time for the oled release, just hope they get on with fixing this stuff now. For now I’m staying on 3.4!
I’m sure this won’t go down well in this sub, but imo updates shouldn’t be pushed to stable with this many bugs still in them!