vkd3d-proton icon indicating copy to clipboard operation
vkd3d-proton copied to clipboard

Death Stranding: performance regression with vkd3d v2.5

Open Nachtraaf80 opened this issue 2 years ago • 4 comments

I picked up Death Stranding after a while and noticed severe framerate drops when there's alot of floating billboard markers (blue cargo markers) on the screen. I don't remember there being such drops before so I started testing several Proton versions and finally compiled proton-tkg with vkd3d version 2.5. Valve's official Proton 6.3-7, Proton Experimental and newer versions of Proton -GE or -tkg all have the regression. The last version I tested that ran well was Proton-tkg 6.14 from August 12th.

I have no clue how to further debug or profile this issue, so if you need additional information please provide instructions how to obtain relevant information.

Proton-tkg 6.14 - vkd3d 2.4 git (August 12) Screenshot_20211019_150340

Proton-tkg 6.19 - vkd3d 2.5 Screenshot_20211019_150752

Nachtraaf80 avatar Oct 19 '21 13:10 Nachtraaf80

Can you try to bisect this if possible?

Also, please try to avoid changing more than one thing at a time, would be interesting to know if Proton-tkg 6.14 in combination with vkd3d-proton 2.5 works fine.

doitsujin avatar Oct 19 '21 13:10 doitsujin

So I tried building proton-tkg 6.14 from source, figuring it would pull in the latest dxvk and vkd3d versions but I ran into some git conflict error which I'm clueless about. So I got the bright idea to just copy both lib/wine/vkd3d-proton and lib64/wine/vkd3d-proton folders from the 6.19 build to the 6.14 build. The game did run and showed the same regression afterwards.

Screenshot_20211019_184739

I assume by bisect you mean try to pinpoint which commit caused the regression? I'm sorry but I have no clue how I would best go about such a task. I tried figuring out the closest date to the commit that caused the regression by trying out as many Proton versions as possible, but the 6.16 both GE and TKG versions gets stuck at 99% loading. The earliest version I managed to run where I noticed the regression is 6.17-tkg from 11 september. So I concluded that a commit somewhere between august 12 and september 11 caused the regression.

Nachtraaf80 avatar Oct 19 '21 18:10 Nachtraaf80

I can reproduce this, i'll get the bisect done..

Oschowa avatar Oct 19 '21 20:10 Oschowa

It seems to be caused by upload_hvv which is now enabled by default. VKD3D_CONFIG=no_upload_hvv restores perf for me.

Oschowa avatar Oct 19 '21 21:10 Oschowa