Proton 5.13-6 RC testing

[aeikum]

Hello. We've put together a new 5.13 build for you to test.

In the Steam client, the Proton 5.13 app should have a "next" beta branch which you can choose to start testing the 5.13-6 release candidates (note that the name of the build in the Steam Settings dialog will not be updated). I will post changes here when we push new builds. The source for the latest RC build is available on the proton_5.13-next branch in these repositories. This branch may receive forced updates.

In this issue, we are interested only in problems that are new to the 5.13-6 RC builds. If you find new problems in the "next" branch, please confirm that the problem does not occur in on the "default" branch before reporting it here.

Here is the tentative changelog. As always, this changelog has not yet been verified by our QA staff, and can change before the final release as we add or remove features during RC testing.

-Fix No Man's Sky in VR mode
-Fix Cyberpunk 2077 world sound issues
-Fix black screen on focus loss in DOOM Eternal (and Disgaea removed in rc3)
-Nioh 2 is now playable
-Fix sound in Dark Sector
-Fix controller support and hotplugging in Yakuza Like a Dragon, Subnautica, DOOM (2016), Virginia
-Better support for PlayStation 5 controllers
-Fix voice chat failure in Deep Rock Galactic
-Fix Need for Speed (2015) hang on launch
-More fixes for game input being active while the Steam overlay is up

[alosarjos]

I'm assuming that "Proton Experimental" is getting this patched too? I'm a bit confused on which Proton version should I test

[kisak-valve]

Hello @alosarjos, that's not a safe assumption. The testing instructions for Proton 5.13-6 RC is in the opening post and Proton Experimental is an independent build of Proton. There's no requirement for Proton Experimental to be on the same update cadence as a new release candidate.

[CSahajdacny]

Where can I report Proton Experimental regressions?

[kisak-valve]

Hello @CSahajdacny, if your issue is related to a call for specifically targeted testing like #4568, then you can add a note there, otherwise, you can add a note to the compatibility report of the affected game with the build date of Proton Experimental and how it differs from the mainline build.

[eth0OS]

-Fix voice chat failure in Deep Rock Galactic

It's working great with pipewire 0.3.21!

[gardotd426]

Fix black screen on focus loss in DOOM Eternal

Nope. Still very much black screen on focus-loss in Doom Eternal. I was super hyped over this fix, too :(

Happy to help debug any way I can.

[aeikum]

@gardotd426 Are you on Nvidia or AMD? There might be an outstanding Nvidia issue.

[gardotd426]

Yeah I'm on Nvidia, but one would think they would have said "Fixes black screen on focus-loss for AMD." if it was only fixed for AMD. Doom Eternal is the only game this happens in, which sucks since it's among my most-played games.

[aeikum]

That's exactly the kind of feedback we want for these RC testing issues. I'll be more clear in the final changelog. The nvidia issue is diagnosed, but we don't have a fix for it yet.

[gardotd426]

No worries, glad I could help in some way

[Elmapul]

(and Disgaea removed in rc3)
why its striked nad what does it mean "removed in rc3" ?

[aeikum]

The change which fixed Disgaea broke A Hat in Time, so we removed that change in the 3rd release candidate.

[Elmapul]

how can i force install the change that fixed disgaea? or at least install the older version wich worked except for the fullscreen issue?
i dont even have a hat in time yet...

[evopls]

-Nioh 2 is now playable

Just to get an idea, when giving this version a try what should I be looking out for in terms of differences? The game was playable on 5.13-5 already it seems. After a dozen or so hours of checking the RC I'm not noticing any changes compared to the issues already present in 5.13-5 (ingame videos not playing & infrequent crashes).

[aeikum]

@evopls The DXVK config is no longer required.

[aeikum]

Thanks all for your testing and feedback. Proton 5.13-6 has been release, so I'm closing this bug.

[nutta-git]

@aeikum still pinned on issues