Dragonflight retail release.
Application Details:
Version: | 10.0.2 |
License: | Retail |
URL: | http://www.worldofwarcraft.com |
Votes: | 0 |
Latest Rating: | Gold |
Latest Wine Version Tested: | 8.0-staging |
Maintainers: About Maintainership
What works
Everything that I tested works:
- Starting the game
- Logging in
- Character selection/creation
- Server selection
- Adjusting in-game settings
- Questing and dungeons (50 to 70fps with graphic quality set to 7)
- Raiding (around 35 fps with graphic quality set to 7)
- All addons I tried (ElvUI, WeakAura, 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
Performance and frame rates are sub-optimal.
Workarounds
DXVK - to address performance issues.
What was not tested
- In-game Voice Chat
- In-game Shop
- PvP
Hardware tested
Graphics:
Additional Comments
This test is an update of my last one following several wine and dxvk upgrade on my side. Following comments seems 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 which compile 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/D... ). 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 12 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 8.0, with dxvk 2.1.0 install on this wine prefix, and using nvidia drivers 525.85.05.
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 Workaround? | Rating | Submitter | ||
Current | Gentoo Linux x86_64 | Feb 02 2023 | 8.0-staging | Yes | Yes | Yes | Gold | b0nt4kun | |
Show | antiX Linux 21 ‘Grup Yorum’ | Dec 30 2022 | 8.0-rc3-staging | Yes | Yes | No | Silver | spaceman |
Bug # | Description | Status | Resolution | Other apps affected |
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Aaron Dewell on Tuesday January 3rd 2023, 18:00
Reverting that setting to "native" fixed the crashes for me. The game runs quite well even at higher graphics settings with high framerates.
(Note: ultimately the solution for that day's low framerate was a reboot of Linux. I'm sure something simpler would have done it, but I don't know what it would have been.)
by spaceman on Wednesday January 4th 2023, 13:04
My WoW prefix currently uses four overrides:
d3d10core (native)
d3d11 (native)
d3d9 (native)
dxgi (native)
So I'm already set to d3dx11 (native) and my crashes are regular, but not too intrusive.
by Aaron Dewell on Wednesday January 11th 2023, 19:39
Good call on having Battle.net in it's own prefix. I can only update it from a VM now, then copy the resulting directory into my wineprefix.
by Steve Ebey on Tuesday January 3rd 2023, 17:24
by spaceman on Sunday January 15th 2023, 5:16