WoW not working with new patch 8.15

Just do a fresh battle.net installation. Backup your WoW folder from your Lutris’ battle.net prefix (and don’t install WoW inside it next time, if you had - use symlinks or another way to not store the game inside Lutris’ prefix), remove it and reinstall. Then login back to your battle.net app, choose path to WoW and you are good to go. You may probably want to change DirectX settings in-game to Legacy DirectX 11.

Otherwise just follow nopies’ instructions: in Lutris’ battle.net configuration change DXVK to Manual and apply this to your prefix as suggested in the post.

2 Likes

I tanked a 2 hour raid last night on 8.1.5 using tkg-4.2, DXVK 1.0, esync enabled. I didn’t change the graphics engine, it is still on DirectX 11.

I’m running in windowed mode if that makes a difference.

I reinstalled using the new script they posted 8 hours ago or so. So far so good, I am getting good fps.

I tried to execute

WINEPREFIX=~/Games/world-of-warcraft/ ./setup_dxvk.sh install

But I got an error “Failed to resolve C:\windows\system32”

I think the new Lutris installer script address the issue though.

hears a link to my youtube showing it works https://youtu.be/DQ9_NN9empQ

Looks promising. A few ppl solve their 8.15 issue by applying this patch. Do you know how to apply this patch on lutrics???

I ran into this issue as well and its a relatively easy fix.

  1. Download the patched dxvk here
  2. Open up ~/.local/share/lutris/runtime/dxvk/
  3. Create a new directory for this new dxvk release. You can name it anything. I chose wow-test, but you can pick anything.
  4. Extract the dxvk patched version downloaded above into this new directory your created in step 3. You want it to have the x32 folder, x64 folder and the setup shell script in there.
  5. Go into the game settings in lutris and change the dxvk version to manual, and type over the word “Manual” that shows up with the name you gave that directory. So in my case I typed in “wow-test”

You are done, and things should work perfectly again.

Just in case it helps here is my directory listing of what I created:

[andrew@schotty-tower-wired wow-test]$ pwd
/home/andrew/.local/share/lutris/runtime/dxvk/wow-test
[andrew@schotty-tower-wired wow-test]$ ls
setup_dxvk.sh  x32  x64
[andrew@schotty-tower-wired wow-test]$ 
2 Likes

This
Very well written step by step guide, this is the approved workaround atm

DXVK updated with a WoW fix

Should just work OOTB now.

2 Likes

I reinstall Battle.Net with Lutris as Lutris dev uploaded a new script to help wine users to play WoW without crash. Don’t forget to move your WoW game folder on another place before to reinstall Battle.Net.
I played more than one hour, it’s stable and fast.
It’s impressive how the wine community and actors was reactive.
Lot of thanks to Philippe and Lutris dev.

3 Likes

Thanks!!

Okay, this is probably the stupidest question asked here, but: should we see any differences in the options we are given? Like in WoW, I have the options for DirectX 11 and DirectX 11 Legacy. Now that I have the patch in for 8.15, I switched WoW to the non-Legacy version - is that correct, or should there be a menu option for DirectX 12? Is DKVX reporting as 11 or 12?

See, I toldja, dumb!

I personally had to do nothing besides download the tkg-4.3 runner. Lutris updated my default runner and dxvk accordingly.
So I just ticked the TKG-4.3 box and clicked “play”.
No more freezes. Great performance (for me).

Many thanks to the Lutris team.

Hello Biffster,
“the only stupiest question are those that are not asked”
Now that’s the bug is fixed by Blizzard, you can choose Directx11 non legacy, if your hardware support it.
Dxvk replace only DIrectx10 and DirectX11. For Direct12 on wine, you have to install vkd3d.

I haven’t played with vkd3d yet – you have any basic instructions on how to setup a prefix properly using it? I did a google, then even a bing search and found nothing. I presume that any prefix rigged for dxvk is going to have some overrides that break vkd3d, so I need to start with a fresh one. Or am I wrong? Not specifically to wow, btw, any game instructions would be great.

Thanks!

I just used a prefix generated by the dxvk lutris installer. Just don’t launch the game with dxvk enabled, cause then it won’t be installed on the prefix.

1 Like

I made it work by nuking the prefix and rerunning the installer. I saw that it was updated and whatever edit was made to the installer made the game work. Have been running without problems since then.

I looked and it was an updated dxvk version, patched to address blizzards f-up. My previous post is another way to get a working prefix from one that broke, up until the dxvk team officially released a fix. Now, I would just say to update WoW and it has a fix that addresses all of this and works again on dxvk going back to the .7x series.

1 Like

I had the same problem. After the patch battle net would give an error and not start the game.

I was able to manually go in and run the game but my frame rates was between 4 and 1 and totally unplayable.

What I ended up doing is upgrading to wine ver 4 and then reinstalling WOW. Runs perfect now with a steady 100 FPS no matter what I am doing in game.

Note: I had to go into Synaptic Package Manager and remove all instances of wine. Totally uninstall my old version of wine (3.8 staging) and then follow the install Wine ver 4 tutorials online. Others might not have to do that. Try to upgrade yours first and if it wont upgrade then you will have to go the path I went probably.

Linux Mint Cinnamon

With dxvk 1.0.1, wow runs without crush. However, I observe another issue. If I play > 1h, wow will start slowing down (eg. fps drop and freeze several sec). This effect getting worse if keep playing. By quit and restart the game, wow back to normal. I highly suspect this is due to memory leakage. Has anyone also noticed? Is there a solution?

I dont have that issue.

I am running with tkg4.3 wine, dxvk 1.0.1, esync. I had just replaced my gpu, but same config on my old 970 and on my rx590. Both ran things well.