https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #43 from Sveinar Søpler cybermax@dexter.no --- (In reply to Andrew Wesie from comment #39)
(In reply to Sveinar Søpler from comment #38)
I cannot get WoW to start with that and vkd3d nor wined3d (d3d11) (dxvk not tested)
I followed the lutris script and disabled d3d12, nvapi, and nvapi64 using winecfg. WoW crashes if I don't disable those DLLs on my system. But this is not related to this bug since I had the same problem on Wine staging 4.8.
Are you able to run WoW with wine staging 4.8 with the same prefix you are using for testing?
WoW runs fine with wine-staging-4.8, and wine-staging-4.9 w/your previous patch: https://bugs.winehq.org/attachment.cgi?id=64567&action=diff in the same wineprefix.
I have not tested todays GIT, but i did test with the two patches in mention here without success.
I also was able to run WoW with some GIT commit + a patch (https://bugs.winehq.org/show_bug.cgi?id=47255#c10), but had issues with "camera-warping" when mouselooking, so that was playable for me. There is no "camera-warping" issues with -4.8 or -4.9 with your patch (nor have i had those issues in the past).
nvapi/nvapi64 is disabled in dll-overrides, but i do use virtual desktop and vkd3d. Have not tested with dxvk tho.
Ill try another GIT pull when i get home tonight and see if recent commits have made a change for me. I configure wine with the default enabled MingW-W64, as disabling this had some issues with msvcr (that probably is fixed now).