Hey all. We've put together a new 7.0 Release Candidate build for you to test.
In the Steam client, the Proton 7.0 app should have a release-candidate beta branch (look for Proton 7.0 in your Steam Library, right click -> Properties... -> BETAS) which you can choose to start testing the 7.0-4 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_7.0-rc branch in this repository. This branch may be force pushed.
We are interested only in issues that are new to the 7.0-4 RC builds. If you believe that something broke please confirm that the problem does not occur with the "none" branch before reporting it here.
The changelog is tentative - it 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.
Has the EAC issue with Paladins been fixed, been hearing people say it worked for about a week or so before it regressed and started booting peeps off steam deck and Linux in general.
@deathxxx123
Does Proton experimental bleeding edge have this fixes also?
Yes. Most of the changes, if not all, trickle bleeding-edge -> experimental -> stable.
Bleeding-edge or anything based on it should not be used by non-developers. All the changes go there without being really tested and the submodules (dxvk, vkd3d-proton) are bumped automatically. Breakages may occur at any time and it may start requiring newer version of drivers than the ones available in various distributions. Experimental gets lots of sanity checking and also gets tested with all of the games that were fixed in the previous releases (see https://github.com/ValveSoftware/Proton/wiki/Changelog).
@waspennator
Has the EAC issue with Paladins been fixed, been hearing people say it worked for about a week or so before it regressed and started booting peeps off steam deck and Linux in general.
Right. I don't see the EAC .so anywhere in the game directory. I think that our fix coincided with one of the EAC grace periods after a game update and that's why it has worked for us. I'll remove it from the list. Thanks!
https://store.steampowered.com/app/444090/Paladins/
Could you change the deck rating on the store page back to unsupported as well, think it got prematurely marked as playable a few days after said fix made the game "work" for a week
@minuteworld1 Search for Proton 7.0 in you library. If you click on the top bar it turns into search prompt. You may need to switch to "tools" tab to see Proton listed. The steps from the original issue description apply after that.
@waspennator I've mentioned this to the people in charge of the ratings. Thanks!
Paladins no longer work and broke about a week after it was fixed. It's still labeled as playable.
Paladins no longer work and broke about a week after it was fixed. It's still labeled as playable.
Already made a post about it and they said they are working on adjusting the deck rating for it.
Does
Proton experimental bleeding edgehave this fixes also?
it still has dxvk v1.10.1...
Paladins no longer work and broke about a week after it was fixed. It's still labeled as playable.
Already made a post about it and they said they are working on adjusting the deck rating for it.
Oh. =(
Im confused, wouldn’t btfrs already be de duplicating the prefix files if enabled? Or is this something else?
@iGom bleeding-edge tracks DXVK master. See the latest: https://github.com/ValveSoftware/Proton/tree/experimental-bleeding-edge-7.0-21771-20220805-pf97544-w03b0ff-d2fe616-vd00d03. The next experimental will also update to DXVK master.
@Bitwolfies btrfs is not smart enough to do that by itself. You either need some deduping program that scans files or use copy_file_range() system call for copying files. This changelog entry is about the latter, see https://github.com/ValveSoftware/Proton/commit/d141d538bc631bdd5025666aef4dcef4790c5b40. Note: Steam Runtime creates a lot of bindmounts and we copy_file_range() files across multiple mounts of the same FS. For this to work kernel 5.18 or newer is required.
it still has dxvk v1.10.1...
It ships DXVK master. Current DXVK development code is based on 1.10.1, the other point releases were created from a separate branch.
one piece pirate warriors 3 has these odd textures during cutscenes and whatnot. and some shadows in the distance of some levels are buggy. but other than that, fully playable
Hello there,
I'm not sure if it is there right place but here we go:
Since the new proton version release, Multiversus (a video game on steam) doesn't work anymore with the "Proton experimental".
When I start the game it crash and then a pop error appears with "A D3D11-compatible GPU (Feature level 11.à, Shader Model 5.0) is required to run the engine."
As a temporary fix I can force the use of a specific Steam Play compatibility tool and choose "Proton 7.0-3", which does work for Multiversus, but is there a way for me to fix this and jump back on the experimental one ?
If this is not the place for this can you guys redirect me to the good one please ?
Hello @minuteworld1, are you showing a regression in behavior from Proton 7.0-3 or just the current state of the game? We want to focus on regressions introduced by the release candidate in this issue report.
Hello @Foxtr0t, the minimum video driver version for the DXVK build inside of Proton Experimental has changed to mesa 22.0 or NVIDIA 510.47 depending on your video card. This is unrelated to the Proton 7.0-4 release candidate. If your system has a current video driver, then please add a note to #6031 as @Benibla124 suggested.
Hi again, Thank you @Benibla124 and @kisak-valve :)
Indeed Proton Experimental has moved to newer driver, hence my issue. I updated my driver and it fixed my problem. Thank you very much @kisak-valve
Have a wonderful day
Hello @minuteworld1, are you showing a regression in behavior from Proton 7.0-3 or just the current state of the game? We want to focus on regressions introduced by the release candidate in this issue report.
Hello @Foxtr0t, the minimum video driver version for the DXVK build inside of Proton Experimental has changed to mesa 22.0 or NVIDIA 510.47 depending on your video card. This is unrelated to the Proton 7.0-4 release candidate. If your system has a current video driver, then please add a note to #6031 as @Benibla124 suggested.
current state of the game. i think the texture issues are a regression from 7.03. if not, ill do better testing next time
I don't know if this is the place, but stable Proton (include 7.03 / 7.04 )does not work with any game with Manjaro + Nvidia with current updates. Lastest kernel + lastest Nvidia driver. But Proton experimental and GE-Proton is working with any game.
With Pop!_OS 22.04 i can use all Proton's. Only difference for now is Nvidia driver. Stable for POP and lastest beta for Manjaro.
I don't know if this is the place, but stable Proton (include 7.03 / 7.04 )does not work with any game with Manjaro + Nvidia with current updates. Lastest kernel + lastest Nvidia driver. But Proton experimental and GE-Proton is working with any game.
With Pop!_OS 22.04 i can use all Proton's. Only difference for now is Nvidia driver. Stable for POP and lastest beta for Manjaro.
may be a nvidia driver regression, worth a separate bug
