protonscr

Winlator dx9 regression at 2.5.x builds

dxvkclosed
doitsujin/dxvk#4489 · opened 2024-11-25 by Succubussix · updated 2024-11-26 · 5 comments · github
SSuccubussix 2024-11-25 github

System information

  • GPU: Adreno 735
  • Driver: Turnip 25.0
  • Wine version: 9.2
  • DXVK version: 2.5.1
  • Box64: c30a392 ( action build artifact )
  • App: Simple d3d9 test environment

DXVK 0.4 ~ 2.4.1

Screenshot_2024-11-25-15-41-10-494_com winlator

DXVK 2.5 ~ 2.5.1

Screenshot_2024-11-25-15-42-14-753_com winlator

What happened? :'( wheres my cute 4 digit fps.

KK0bin maintainer 2024-11-25 github

Duplicate of #4484

It appears to be an issue with Winlator/the Termux X11 stack. We don't support that as a target platform and regular systems are fine as far as I know (Nvidia, AMD, Qualcomm Linux).

I cannot reproduce the issue, I use a Google Pixel as a phone which has an ARM Mali GPU.

Maybe you can bisect it down to the individual commit that regressed performance.

SSuccubussix 2024-11-25 github

Maybe you can bisect it down to the individual commit that regressed performance.

welp I tried.. I use git graph to visualize it when d3d9 starts to dip on winlator. because its easy i just right click and checkout

image

--- tested

56b7c8cd41ea17c0656f9485730fea5d55b3db62 - failed  
5ad84563dd8f7df9905c74f86d47012fc5dfee82 - failed
b4ed1081058be5361784f686aa07b194057dd8a6 - failed
f9a99e81f4d0e9b74dde4a4f55a329383190acf5 - failed
27539fc83847c74e619307c606309234d8a3b2e0 - failed
1ee60048c0af5fedae9af8890db2c2c9a0beeb09 - passed
4c0cbbef6abe2b1a9e8c358be0caf207c907a5d2 - passed
cc22ccfc5c8054710212563a3724779f6f6d5cae - passed
4a00623c40586b3f42d872679ac366b66d88b4b0 - passed
500c86c054d27bbd07370058bf8d4971948500f7 - passed
f76fb75956b0a135fbbc84f0e5e412a46b007bb1 - passed
763b82b1e482e3bce13f5226ead308d731703b72 - passed
a044c639f79d23f86f59c3fb7f77f3a6e3b23caf - passed

failed means its under 400 fps
passed means its over 1.5k+ fps xD

i dont know i guess i will just skip 2.5.1 for now..
it all start on [dxvk] Use timeline semaphores for GPU synchronization commit.

Ddoitsujin maintainer 2024-11-25 github

Yeah someone worked out that this is almost certainly caused by turnip having to emulate timeline semaphores when running on top of the proprietary Qualcomm kernel driver. It's not really viable for us to revert back to the old path, so future versions of DXVK will remain slow on this platform.

Hhisham2630 2024-11-26 github

Yeah someone worked out that this is almost certainly caused by turnip having to emulate timeline semaphores when running on top of the proprietary Qualcomm kernel driver. It's not really viable for us to revert back to the old path, so future versions of DXVK will remain slow on this platform.

what about an environment variable or an option in config file to disable that timeline semaphores?

KK0bin maintainer 2024-11-26 github

what about an environment variable or an option in config file to disable that timeline semaphores?

Too much maintenance overhead to keep both paths around.

Nothing extracted yet.