ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.42k stars 1.07k forks source link

Serious Engine Games Regression with latest Proton Experimental #7061

Closed kodatarule closed 1 year ago

kodatarule commented 1 year ago

Compatibility Report

System Information

I confirm:

Symptoms

The games run at 30-40fps, with proton 8.0-3 it's fine.

steam-564310.log

Ennea commented 1 year ago

This appears to affect Unity games, too. Both Valheim and Shadow Gambit run noticeably slower (down to ~60-70 frames per second in Shadow Gambit, as opposed to a very stable 165 – which is my refresh rate – otherwise).

I got an RTX 3080, driver version 535.104.05 as well, Linux kernel 6.4.12.

ShaqibK commented 1 year ago

Can confirm this issue in naraka bladepoint. Gpu power usage dropped significantly and frame rates are now 30-40 from 165. Using any other version fixed the issue. 6800h+3070ti mobile running endeavour os fully updated.

Blisto91 commented 1 year ago

Hi there. Could i get you to try a quick test? Copy the dll files from ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib64/wine/dxvk/ and paste them in to ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib64/wine/dxvk/ overwriting the files already present. Then test if there is still a performance drop on Experimental.

Once you are done you can search for "Proton Experimental" in your Steam library -> right click on it and select "Properites" -> select the "Installed Files" tab -> Click "Verify integrity of tool files". This should bring back Experimental to it's proper state.

Ennea commented 1 year ago

@Blisto91 Yup, this brings back the previous performance. A DXVK regression, then?

Edit: Looks like Philip has already taken care of this here: https://github.com/doitsujin/dxvk/commit/a3fa9c26dce09a4e21935789e4f13bb537b19021

Blisto91 commented 1 year ago

Thank you for the report and testing. The offending commit have been found and reverted in dxvk. https://github.com/doitsujin/dxvk/commit/a3fa9c26dce09a4e21935789e4f13bb537b19021

Blisto91 commented 1 year ago

@kodatarule Are you able to confirm the issue has been solved in current Experimental?

kodatarule commented 1 year ago

Yes it has been resolved now, the issue can be closed.

Blisto91 commented 1 year ago

Cool 👍