[Regression] Massive FPS drop in dxvk with the latest commits
Can you try running it with the option dxvk.enableDescriptorBuffer = False?
You can pass that either as a Steam launch option like this: DXVK_CONFIG="dxvk.enableDescriptorBuffer=False" %command% or by creating a dxvk config file.
That worked, but that would be a bad experience if an update gets out with this issue.
Before:
~100fps with huge framedrops while moving
~60fps with huge framedrops while moving
After:
~155fps with smoother frame changes while moving
~80fps and smoother frame changes while moving
I also noticed a small boost with that option in 2.6.2 (not sure if it really does something, but I tried it twice, i get 10-20 fps more in the first scene in the screenshots (135 to 155)
* GPU: Quadro M4000 * Driver: 570.153.02 (proprietary)
Interestingly, I am using the same driver on a 4070 and haven't noticed much variation. Since the Quadro M4000 is a Maxwell card, perhaps the changes impact older Nvidia hardware to a far greater degree.
That's my theory too. I suspect Pascal and older cards are affected, but I do not own or know someone who owns a Pascal card. I have an M2000M in a laptop that I will test this on too and see how it fares.
Sigh. Guess we'll revert descriptor buffer enablement on Intel / NV then, just a shame because it's a huge cpu-bound improvement across the board.
Cant you selectively disable it, for example only for Pascal and older if it's beneficial to newer gen hardware?
We have no way to detect Pascal (or any specific architecture, really).
Or actually, scratch that, we kind of do - can just check for mesh shader support. But in general I am not a huge fan of architecture-specific workarounds like this.
I was testing a few proton forks for some game fixes and I noticed a huge frame drops across all of my tested games (Zenless Zone Zero, Control...). After some digging, when I switch back to Release 2.6.2 of dxvk, the FPS returns to normal values, however when using the latest commit builds, I lose around 1/3rd of the baseline FPS (regardless of the wine/proton version).
Sample of FPS Drops on tested games:
Software information
Control: Medium settings, no motion blur
ZZZ: Low, x0.8, no motion blur, no bloom
System information
2.6.2 and e4989d1masterApitrace file(s) and Log files
ZZZ Apitrace https://files.catbox.moe/qlcqiu.log
Control would lock up kde/plasma when it reaches the 3D scene when using WineD3D.