New version of World of Tanks unplayable due to extreme CPU usage about dxvk

[doitsujin]

Does this work better with wined3d? The game spawning 500 threads really doesn't sound like anything dxvk related so I'd expect it to be just as bad.

[43615]

I've set the d3d* and dxgi overrides to "builtin", is that the correct way to try that? Getting about the same performance, except the launcher doesn't render. The thread spawning behavior is the same.

Does that mean it's a deeper issue with Wine? Where could I get help with that?

[mbriar]

I've set the d3d* and dxgi overrides to "builtin", is that the correct way to try that?

Yes, but you can also just double check by enabling the DXVK HUD, which obviously shouldn't show up with wined3d.

Where could I get help with that?

wine bug tracker, but i assume you're already using esync or fsync? Without those, poor multithreaded performance is pretty much expected.

[43615]

double check by enabling the DXVK HUD

Yeah, just thought of that myself. I did it right then.

esync or fsync

I've never messed with those. Setting the WINE[EF]SYNC variables doesn't change anything.

[mbriar]

Upstream wine doesn't have fsync or esync, so setting the env vars won't do anything on a wine upstream build. You need wine-staging for esync or a proton-based wine build for fsync.

[43615]

I've already tried the Steam version through Proton Experimental as well as standalone Proton, which should come with fsync enabled. Same issue there.

Also just tried wine-staging 9.8 with esync enabled, no difference either.

Logically speaking, these shouldn't matter since the game worked fine previously.

Closing and moving to Wine places for help.