World Of Warcraft Legion
Following recent events in the Broken Isles, a link has been created between Azeroth and Kil'jaeden's homeworld of Argus, bringing the Burning Legion closer than ever to destroying Azeroth. In order to stop them once and for all, Illidan and Velen are taking the war directly to the surface of Argus, where they hope to join forces with Alleria, Turalyon, and the Army of the Light to launch an all-out assault on the Legion's primary base of operations.
1. PvP (Battlegrounds, Arena Battles)
2. World Questing (Broken Isles)
1. System->Graphics (except MSAA Anti-Aliasing)
2. System->Advanced (DirectX 9, DirectX 11)
What does not
1. The options Anti-Aliasing: MSAA (2x-8x) in System->Graphics. When I turn it on, the screen blurs and cannot be used.
2. Some my WoW key bindings conflicted with KDE Plasma and I had to rebind them to 'None' in KDE System settings->Shortcuts. (Alt+F1, Alt+`).
What was not tested
1. Raids and dungeons
2. Any zones apart from Broken Isles, Argus and Orgrimmar
3. Voice chat
I have Radeon HD 7970 on amdgpu open-source driver.
On stable packages of Gentoo the game appeared to be not usable for my in DirectX 9 and DirectX 11 as there were a slow fps rate and shimmering textures In DirectX 9 and red-looking textures in DirectX 11. But I decided to use the testing branch for some packages and it worked. I did not tested witch one package was the problem but here are the packages that I have installed:
x11-libs/libdrm-2.4.88 (2.4.82 stable)
media-libs/mesa-17.3.0 (17.1.10 stable)
x11-drivers/xf86-video-amdgpu-1.4.0 (1.3.0 stable)
to install them you need to add them in /etc/portage/package.accept_keywords this way:
then Gentoo portage will pull the testing branch for them.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||antiX-17 "Heather Heyer" Core||May 28 2018||3.9-staging||Yes||Yes||Yes||Gold||spaceman|
|Show||antiX-17 "Heather Heyer" Core||Mar 08 2018||3.3||Yes||Yes||Yes||Gold||spaceman|
|Show||Arch Linux x86_64||Jan 18 2018||3.0-staging||Yes||Yes||Yes||Gold||d3rrial|
|Show||KDE Neon 5.11.4||Jan 05 2018||2.21-staging||Yes||Yes||Yes||Gold||Jay Greenfield|
|Show||Ubuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)||Dec 08 2017||2.21-staging||Yes||Yes||Yes||Gold||Nuffin|
|Bug #||Description||Status||Resolution||Other apps affected|
|11674||Dual-core unsupported in WoW and SC2||STAGED||View|
|29168||Multiple games and applications need realtime updates to KSYSTEM_TIME members in KUSER_SHARED_DATA (Star Wars: The Old Republic game client, Blizzard games: 32-bit Diablo III, 32-bit WoW, Overwatch, GO 1.4+ runtime)||STAGED||View|
|35461||Synergy server causes mouseover events to fail in World of Warcraft||NEW||View|
|37942||World of Warcraft (7.x.x) hangs: 100% CPU usage||UNCONFIRMED||View|
|40868||World of Warcraft 7 (Legion expansion beta realm version) client causes a lot of seh:RtlCaptureStackBackTrace stub noise in console||STAGED||View|
|41167||HLSL shader parsing failed||REOPENED||View|
|42065||WOW 7.1 spams fixme:d3d_draw:draw_primitive_arrays Start instance (VALUE) not supported.||UNCONFIRMED||View|
|42805||World of Warcrafft 64 bit client freezes or glitches after some time||UNCONFIRMED||View|
|43417||World of Warcraft leaks memory in both 64 and 32 bit modes.||UNCONFIRMED||View|
|43656||32-bit World of Warcraft client reports 'Game Initialization Failed!' or crashes on startup with stack overflow||RESOLVED||ABANDONED||View|
|43768||WOW crash game||UNCONFIRMED||View|
|43857||WoW PTR 7.3.2 crashes on startup||UNCONFIRMED||View|
|44585||Multiple applications and games need ntdll.LdrRegisterDllNotification/LdrUnregisterDllNotification implementation (Firefox 60+, Diablo III v2. 6. 1. 49286+, World of Warcraft, Overwatch)||STAGED||View|
|44650||Multiple Blizzard games need dxgi and d3d11 dlls mapped without hole between two LOAD segments (Diablo III v2. 6. 1. 49286+, World of Warcraft, Overwatch)||STAGED||View|
|45101||Mouse cursor not displaying correctly in Hearthstone||UNCONFIRMED||View|
|45209||Staging 3.8 crippling preformance degradation||RESOLVED||FIXED||View|
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 gcc 7.3.1 and I have installed all the dependencies that wine needs. if you are running the fedora distro of wine, you can use 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. There are several forks of the pba patches, so if one does not apply, uncomment one of the other, and try again. make the changes to the apply portion, to reflect the directory that some of the other repos use. I only compile a 64 bit wine, since all I do is run WoW. If you want to run other apps, then follow the winehq wiki about building both 32 and 64 bit and the proper steps to install them.
rm -fr wine rm -fr wine-staging rm -fr wine-pba git clone git://source.winehq.org/git/wine.git git clone https://github.com/wine-staging/wine-staging.git git clone https://github.com/acomminos/wine-pba.git cd wine-staging ./patches/patchinstall.sh DESTDIR="../wine" --all echo If the patches apply cleanly, then go forth and compile cd ../wine git apply ../wine-pba/patches/* echo this is the end, if no errors were presented, beyond the whitespace warnings, 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.
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.
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-x make -j24 cd ../wine32-build PKG_CONFIG_PATH=/usr/lib/pkgconfig ../wine/configure
CFLAGS='-march=bdver2 -mtune=bdver2 -O3 -fPIC -fomit-frame-pointer -pipe
--with-wine64=../wine64-build --without-gtk3 --with-x make -j24