World of Warcraft

What works

• Installation (through Battle.net App)
• Logging in
• Character select
• Basic PvE around Goldshire
• D3D11 Renderer (via DXVK)
• IPv6
• Hardware Cursor
• Windowed Fullscreen
• VSync + Triple Buffering (FPS caps at 60, no tearing, and FPS can fluctuate to values other than 15/30/45)
• 4k Resolution
• 64-bit
• Starting WoW through Battle.net App
• Starting WoW through WoW-64.exe

What does not

• Relatively poor Direct3D 11 renderer performance

Workarounds

• Used DXVK to bring the Direct3D 11 renderer to acceptable performance levels

What was not tested

• Other PvE
• PvP
• D3D9 Renderer
• OpenGL Renderer

Hardware tested

Graphics:

• GPU: AMD
• Driver: open source

Additional Comments

• Radeon RX 560 (AMDGPU open-source driver + RADV)
• Mesa 18.2 (che Copr)
• LLVM 7.0 (che Copr)
• 4K@60Hz (over HDMI)
• Fedora Workstation 28 (GNOME on Xorg)
• Kernel 4.17 (4.17.3-200.fc28.x86_64)
• Wine Staging 3.11 (default in Fedora's repo)
• DXVK 0.61
• Overall, it works and performs great; perhaps at a little less FPS than Windows, but still more than enough playable at the same settings

I would recommend putting this in a directory of its own, such as wine-dirs or some other similar name, so that if needed, a simple rm -fr wine-dirs would eliminate everything, if you need to free up the space on your drive.  These steps work on my Fedora 28 distro. I use the latest gcc from the Fedora repositries, and I have installed all the dependencies that wine needs.  if you are running the fedora distro of wine, you can sudo dnf  builddep wine to download the dependencies, then do sudo dnf remove wine, so that when you compile, you do not cross versions and have to troubleshoot. copy and paste the text shown here, to a script file, and run it.  Go get some coffee, or watch tv, as dependent on your internet speed, the git repos may take time to download. 

clear
echo Cleanup and fresh download of repositories needed
rm -fr wine
rm -fr wine-staging
echo WineHQ Devel Source Git
git clone https://github.com/wine-mirror/wine.git
echo Unoffical Wine Staging Git
git clone https://github.com/wine-staging/wine-staging.git
cd wine-staging
echo Working in $(pwd)
./patches/patchinstall.sh DESTDIR="../wine" --all
cd ~/wine-dirs
sed -i -e 's/MODE_FIFO/MODE_IMMEDIATE/' wine/dlls/dxgi/swapchain.c
cat wine/dlls/dxgi/swapchain.c | grep -i mode_IMMEDIATE
echo this is the end, if no errors were presented, then compile and enjoy

if you get problems with firewall, then most likely, you do not have gnu-tls installed. simply install that and rerun the script.

Build VKD3D Library

rm -fr vkd3d
git clone git://source.winehq.org/git/vkd3d.git
cd vkd3d
./autogen.sh
./configure --enable-demos --with-sysroot
make -j6
sudo make install
sudo ldconfig

Compiling for a WoW64 Shared Build per the Wine Wiki

These instructions assume all the build dependencies for 32 and 64 bit are properly installed.  If not, you must take the time to get them. Explaining that here would be beyond the scope of this example. Shown here is the compile script I use after running the download and patch in the other How-to shown on this site. Make sure to change bdver2 to native so that it detects your processor properly. also change the make -j6 to a different number, as per the number of cores you have. This does speed up compiling. 

echo Clean Start
rm -fr wine64-build
rm -fr wine32-build
echo Make Build Directories
mkdir wine64-build
mkdir wine32-build
cd wine64-build
../wine/configure CFLAGS='-march=bdver2 -mtune=bdver2 -O3 -fPIC -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS -DWINE_NO_DEBUG_MSGS' --enable-win64 --without-gtk3 --with-vkd3d --with-vulkan --with-x
make -j6
cd ../wine32-build
PKG_CONFIG_PATH=/usr/lib/pkgconfig ../wine/configure CFLAGS='-march=bdver2 -mtune=bdver2 -O3 -fPIC -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS -DWINE_NO_DEBUG_MSGS' --with-wine64=../wine64-build --without-gtk3 --with-vkd3d --with-vulkan --with-x
make -j6

If the compile is successful then the script shown below will uninstall any previous compiled version, and install the newest build.

cd wine32-build
sudo make uninstall
cd ../wine64-build
sudo make uninstall
cd ../wine32-build
sudo make install
cd ../wine64-build
sudo make install
cd ..
wineboot --update

Go set windows version to windows 10, so that the game will present the DX12 option, in the advanced settings, and then restart the game, and enjoy the WoW 8.0 Battle for Azeroth. You may also run Battle.net desktop app. Shown below is the script I use to run WoW.  To run Twitch, wine has to be set to Windows 7, but WoW has to be set to windows 10, to allow DX12.  The launch script takes care of that.  

Game Launch Script

#!/usr/bin/env bash
winetricks win10
env VKD3D_DEBUG=none WINEDEBUG=-all STAGING_SHARED_MEMORY=1 STAGING_WRITECOPY=1 nice -20 wine64 '/home/steve/.wine/drive_c/Program Files (x86)/World of Warcraft/Wow.exe'
winetricks win7

As a reminder - this error has been popping up since the 7.3 patch.

There is a github repo with a "clean" Windows-version Cache-file set

github.com/1thumbbmcc/wowcache.git

There's a forum thread here at WineHQ about the error:

forum.winehq.org/viewtopic.php?f=8&t=30803s

and there are existing forum threads on both EU and US official WoW forums:

eu.battle.net/forums/en/wow/topic/17620271965

eu.battle.net/forums/en/wow/topic/17620282020

us.battle.net/forums/en/wow/topic/20765466460

As far as we can tell - some (not all) characters generate
unusable/unstable files in the Cache folder when playing under Wine on
Linux that result in the error/disconnect. Some players have reported
being able to play normally after just adding the Windows-version Cache
files (without first clearing the folder) but since 8.0 that hasn't been
the case for me - the error and disconnects persist unless I delete ALL
existing files in my Cache prior to extracting the .zip contents into
the folder. Also, subsequent clearing of the Cache folder (because of
conflicts with other patches/addons etc) has required once again
reloading the Windows-version Cache files or the error and disconnects
resume. This is just a workaround - the bug is obviously not fixed, but
it does allow you to resume play without the disconnects. Until Blizzard
corrects the actual file-creation problem I'll try to pop in here more
frequently to update and respond.