https://bugs.winehq.org/show_bug.cgi?id=46416
Berillions berillions@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |berillions@gmail.com
--- Comment #23 from Berillions berillions@gmail.com --- (In reply to Sveinar Søpler from comment #22)
(In reply to themainliner from comment #20)
Comment 18 should read:
"I'm concerned that *without* DXVK wine-staging cannot launch WoW at all...
I tested WoW with wined3d and d3d11. I used latest wine-staging GIT 65e6bb8111acfc6d7fb08f209bb01348150c14d4 from today, and i would say that you need to use D3D11-Legacy mode in WoW.
I got in with the "new" d3d11, but it was less than a slideshow tbh. Dunno if i would eventually crash if i had hung around long enough? With d3d11-legacy, it was more or less as expected. 20'ish fps in Boralus vs. 80 with d3d12 and 100'ish with DXVK (and the "new" d3d11).
Wine-staging-4.3 crashed with the error you stated bove when i tried D3D11, but worked with D3D12 AND recent dxvk 1.0.1.
So, to reiterate: D3D12 -> Works with wine-staging-4.3+ and recent vkd3d D3D11 -> Works with wine-staging-4.3+ if you use DXVK 1.0.1 D3D11 -> Does NOT work with wined3d AT ALL (Unplayable or crashing). D3D11-Legacy -> Works with wine-staging-git 65e6bb8111acfc6d7fb08f209bb01348150c14d4 D3D11-Legacy -> Does NOT work with wine-staging-4.3 (Crash upon login).
@Sveinar Søpler : I have a different issue with WoW and VKD3D. The login works correctly but i choose a character who is in BFA region like Zul'Dazar, WoW crashes with Error 132. But if i choose a character who is in old region like Orgrimmar/Kalimdor, the game works without issue.