Please release SteamOS source code

Originally posted by mathew2214 | Mr.RAM card:

Please release SteamOS source code

https://gitlab.com/evlaV/jupiter-PKGBUILD

Here is the mirror.

Originally posted by The Asgorian Bugsong:

Originally posted by Kas:

Still doesn't fixed game mode huge performance degradation in 4k (especially 4k120hz) resolution. It was worked fine before 3.5 goes to stable in all the branches (including 3.6 branch). Now it broken anywhere. Valve please fix this

What game did you see the performance regression in the most, or more specifically what game did you test out on 3.5

It’s everywhere, even steam shell itself (library, store and other pages).

It works very weird now. Looks like it have 30fps cap, because it will never go above 30 anywhere in game mode (library, any game etc). It also works with kind of x0.5 coefficient with limiter (still caped to 30fps)
For example, when I choose 120fps/hz in limiter, it caped 30fps.
60fps/120hz limit is also caped to 30fps.
40fps/120hz limit will be caped to 20fps.
30 -> 15
24 -> 12
20 -> 10.

It is VERY annoying regression, because now I have to choose 1080p120hz and can’t use 4k anymore. But just before 3.5 releases (oled merged to branches) it was OK.


It also works without any issues in 4k120hz in desktop mode.

I tried with all the branches (stable, beta, main = 3.6)

what about Wi-Fi issue in 3.5.7? Did they fix it?

Originally posted by deaddoof:

Originally posted by mathew2214 | Mr.RAM card:

Please release SteamOS source code

https://gitlab.com/evlaV/jupiter-PKGBUILD

Here is the mirror.

Is that an official valve repo?

Originally posted by Kas:

Originally posted by The Asgorian Bugsong:

What game did you see the performance regression in the most, or more specifically what game did you test out on 3.5

It’s everywhere, even steam shell itself (library, store and other pages).

It works very weird now. Looks like it have 30fps cap, because it will never go above 30 anywhere in game mode (library, any game etc). It also works with kind of x0.5 coefficient with limiter (still caped to 30fps)
For example, when I choose 120fps/hz in limiter, it caped 30fps.
60fps/120hz limit is also caped to 30fps.
40fps/120hz limit will be caped to 20fps.
30 -> 15
24 -> 12
20 -> 10.

It is VERY annoying regression, because now I have to choose 1080p120hz and can’t use 4k anymore. But just before 3.5 releases (oled merged to branches) it was OK.


It also works without any issues in 4k120hz in desktop mode.

Very strange, make a report for it here then.

https://github.com/ValveSoftware/SteamOS/issues

Originally posted by mathew2214 | Mr.RAM card:

Originally posted by deaddoof:

https://gitlab.com/evlaV/jupiter-PKGBUILD

Here is the mirror.

Is that an official valve repo?

No. You should read the repo. The mirror is criticizing Valve.

Originally posted by RealChris:

please address and fix discover app crashing trying to get updates in desktop mode

You can update by opening the terminal and doing "flatpak update" then hit <enter> and confirm with "y"<enter>. This is more reliable anyway as Discover often gets stuck while updating.

Originally posted by The Asgorian Bugsong:

Originally posted by Kas:

It’s everywhere, even steam shell itself (library, store and other pages).

It works very weird now. Looks like it have 30fps cap, because it will never go above 30 anywhere in game mode (library, any game etc). It also works with kind of x0.5 coefficient with limiter (still caped to 30fps)
For example, when I choose 120fps/hz in limiter, it caped 30fps.
60fps/120hz limit is also caped to 30fps.
40fps/120hz limit will be caped to 20fps.
30 -> 15
24 -> 12
20 -> 10.

It is VERY annoying regression, because now I have to choose 1080p120hz and can’t use 4k anymore. But just before 3.5 releases (oled merged to branches) it was OK.


It also works without any issues in 4k120hz in desktop mode.

Very strange, make a report for it here then.

https://github.com/ValveSoftware/SteamOS/issues

Already did https://github.com/ValveSoftware/SteamOS/issues/1219

Originally posted by Kas:

Originally posted by The Asgorian Bugsong:

Very strange, make a report for it here then.

https://github.com/ValveSoftware/SteamOS/issues

Already did https://github.com/ValveSoftware/SteamOS/issues/1219

Alright then, just wanted to make sure.

Originally posted by The Asgorian Bugsong:

Originally posted by Kas:

Already did https://github.com/ValveSoftware/SteamOS/issues/1219

Alright then, just wanted to make sure.

Seems like no one works with that.

Wondering if there someone to check 4k120 also

Originally posted by Johnnyoo9:

what about Wi-Fi issue in 3.5.7? Did they fix it?

nope, still won’t connect to my non mesh 2.4ghz network

I’ll need to test it some more, but 3.5.9 appears to have fixed the 200/1040MHz bug. My issue was more about the games crashing and then displaying the “verifying installation” message, but the devs may be zeroing in on the cause of this bug. Thanks.

Unfortunately, the crashing issue is still present. Same as before. The game will freeze, go black, return to the frozen screen, go black again, display the “verifying installation” message and progress bar, then finally showing the Steam Deck logo and then boot animation and returning to the library.

I just submitted the system report directly after the crash, under this same account/profile, so hopefully that can help.

It does seem like some progress is being made.

*update

Scratch that. It does appear that the frame rate bug is still present.

While the crashing is still present, progress does appear to have been made. It seems to take longer for the crashes to happen. Before, it was anywhere from 5 seconds to 5 minutes. Now, it seems to be able to go for at least 5 minutes before crashing.

The developers are definitely on the right track with this latest patch, and I applaud them. Everyone still affected needs to keep testing out different games and settings with these patches, provide as detailed descriptions as they can, and submit the system reports directly after a crash. Do so over at GitHub as well.

How to recreate the FPS cap bug:

-Disable “enable unified frame limit management“.
-Set lower frame rate and screen refresh rate in performance quick settings. (Note: do is before launching game).
-Play Skyrim Special Edition
—The FPS counter will likely show 60, instead of what you had previously set it at.

So far, the bug only appears to affect global settings. A workaround is to enable game profiles and set the desired setting for each individual game.