The Old God N’Zoth has been unleashed from his titan wrought prison, and an ancient corruption has taken root across Azeroth, turning friends into foes and trapping warriors’ minds in nightmare visions of a hopeless future. As despair and madness consume the land, the heroes of the Horde and the Alliance will need to fight for their sanity—and the fate of their wounded world in this content update.
ShadowLands is live. Sylvanas and the Jailer in together, to bridge the world of the dead with Azeroth.
|Latest Wine Version Tested:||7.0-staging|
Maintainers: About Maintainership
Everything that I tested works:
- Starting the game
- Logging in
- Character selection/creation
- Server selection
- Adjusting in-game settings
- Questing and dungeons (70 to 100fps with graphic quality set to 8)
- Raiding (around 40 fps with graphic quality set to 8)
- All addons I tried (ElvUI, TSM, BigWigs, etc.)
- Auction house
Installation from Battle.net application works (of course, this means you need to get it running through wine first...)
Update through Battle.net application works
What does not
What was not tested
This test is an update of my last one following several wine and dxvk upgrade on my side. Following comments are still relevant:
Since several versions, wine staging and dxvk uses PE format for libraries, which requires them to be build with mingw support (obvious for dxvk which does not compiles without it, less obvious for wine whichcompile fine but does not allow game to run). Enabling mingw involves creating a crossdev environment. i can only recommend to follow gentoo wiki for it since it can be quite tricky ( https://wiki.gentoo.org/wiki/DXVK ). Once mingw compiler and libraries are fine, you can compile dxvk, and wine with mingw support. With current dxvk, I needed to upgrade my mingw compiler to version
10 (I used gcc 11 this time).
I used to have lots of random crash while playing in previous versions: I took the habit of compiling wine with "-march=x86-64" (instead of -march=skylake in my case) which used to fix the issue (I'm not
sure it is still relevant).
I'm running WoW (-d3d11) from a fresh wine prefix for wine staging 7.0, with dxvk 1.9.3 install on this wine prefix, and using nvidia drivers 470.94.
Windows is set to version 10 in winecfg, CSMT is disabled and winetricks is not used at all.
Those variables are set: WINEDEBUG=-all DXVK_LOG_LEVEL=warn STAGING_SHARED_MEMORY=1 STAGING_WRITECOPY=1 __GL_THREADED_OPTIMIZATIONS=1
I used to run WoW (and Battle.net) from a NTFS partition using ntfs-3g to mount it. I recently formated it to use ext4 instead (using rsync to move data away before, and move data back after). For now, I don't believe it made any difference from a stability or performance point of view.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Gentoo Linux x86_64||Jan 25 2022||7.0-staging||Yes||Yes||No||Platinum||b0nt4kun|
|Show||Gentoo Linux x86_64||Jul 18 2021||6.12-staging||N/A||Yes||No||Platinum||b0nt4kun|
|Show||Ubuntu 20.04 "Focal" (+ variants like Kubuntu)||May 06 2021||5.0.5||Yes||Yes||No||Platinum||Pablo Lucero|
|Show||openSUSE Leap 15.2||Apr 06 2021||6.5-staging||Yes||Yes||No||Platinum||Alberto|
|Show||Ubuntu 20.04 "Focal" (+ variants like Kubuntu)||Feb 05 2021||6.1-staging||Yes||No||No||Garbage||Maia Everett|
|Bug #||Description||Status||Resolution||Other apps affected|
|44210||GNUTLS_CIPHER_CHACHA20_POLY1305 is not work||UNCONFIRMED||View|
|46410||Screen flickering in WoW||NEW||View|
|46416||World of Warcraft dx12/vkd3d crashes soon after login (RADV)||NEW||View|
|46978||World of Warcraft shows ghost images when turning||UNCONFIRMED||View|
|47471||World of Warcraft 8.2.0 freezes when entering New zone Nazjatar (directx 12)||NEW||View|
|47731||World of Warcraft BFA Crash with error 132 Memory could not be read.||UNCONFIRMED||View|
|49170||WoW (World of Warcraft) shows colored grass and mosaic effects||UNCONFIRMED||View|
|49233||World of Wacraft (WoW) slow fps with the dx11 modern renderer||UNCONFIRMED||View|
|49423||Added input lag in World of Warcraft and other games||UNCONFIRMED||View|
|49497||WoW (World of Warcraft) crashes with multithreaded modern renderer||UNCONFIRMED||View|
|49639||World of Warcraft Shadowlands (wow) has a fly screen effect||UNCONFIRMED||View|
|49682||World of Warcraft (WoW) Shadowlands Beta with strange "shadows" in DX11Modern&DX12||UNCONFIRMED||View|
|49781||World of Warcraft (WoW) Shadowlands stays black with DX12||UNCONFIRMED||View|
|50614||World of Warcraft Retail (WoW) crashes with 6.1-staging||UNCONFIRMED||View|
|52585||Multiple applications need NtQueryDirectoryObject to return multiple entries (Cygwin shells, WinObj 3.01)||UNCONFIRMED||View|
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by b0nt4kun on Monday December 13th 2021, 9:43
- if there is any issue/side effect from running WoW on ext4 rather than NTFS (a long time ago I saw something about WoW being confused with ext4 permissions);
- if there is any performance difference (loading time for example).
Any feedback would be appreciated :)
by Pavel R on Wednesday January 19th 2022, 1:48
by b0nt4kun on Tuesday January 25th 2022, 4:29
by Hamidreza on Sunday May 16th 2021, 9:56
by Jon on Wednesday June 30th 2021, 15:45
by spaceman on Saturday April 17th 2021, 10:48
ACCESS_VIOLATION : error 132: ERROR #132 (0x85100084) Fatal exception!
The instruction at "0x000000018000396a" referenced memory at "0x000000000000000 0".
The memory could not be "read".
I'm a little embarrassed to report for anyone else who experiences this issue, that I resolved it, in 6.6 by suffixing my commandline with -d3d11. so:
env WINEPREFIX="/full/path/to/ WoW prefix/" wine '/full/path/to/World of Warcraft/_retail_/Wow.exe' -d3d11
This may have fixed my problems with 6.5, but reading a bug report I was waiting for 6.6 which was patched to fix a similar issue.