Current version of the game
Installing via Battle.net app.
Logging in to hero list and playing the game.
What does not
Nothing I've found.
What was not tested
Playing for longer than 10 minutes, so no dungeons or anything was tested.
To get the game to run, you need to get a copy of dbghelp.dll into your Diablo folder, set dbghelp to Native in winecfg. msvcp100 is probably needed set at Native/builtin. Haven't tested it without, as I'm running it in my Battle.net prefix. To launch the game you need to run the following command: setarch i386 -3 -L -B -R wine '/path/to/Diablo III.exe' -launch -opengl Game will not retrieve Hero List if Launched by the Battle.net app.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Ubuntu 20.04 "Focal" (+ variants like Kubuntu)||Sep 24 2022||7.17||Yes||Yes||No||Platinum||Acridwax|
|Show||Ubuntu 20.04 "Focal" (+ variants like Kubuntu)||Aug 30 2022||7.16||Yes||Yes||No||Platinum||Acridwax|
|Show||Ubuntu 20.04 "Focal" (+ variants like Kubuntu)||Aug 29 2022||7.15||Yes||Yes||No||Platinum||Acridwax|
|Show||Debian GNU/Linux 11.x "Bullseye" x86_64||Aug 03 2022||7.14||Yes||Yes||No||Platinum||Acridwax|
|Show||Ubuntu 20.04 "Focal" (+ variants like Kubuntu)||Jul 03 2022||7.12||Yes||Yes||No||Platinum||Acridwax|
|Bug #||Description||Status||Resolution||Other apps affected|
|11674||Dual-core unsupported in WoW and SC2||STAGED||View|
|30967||Diablo III: Resolution problems without virtual desktop||UNCONFIRMED||View|
|30993||diablo 3 d3d device error||UNCONFIRMED||View|
|31262||Diablo III in game mouse cursor Out of sync, hangs in place.||UNCONFIRMED||View|
|32083||Diablo III: Missing logo on startup||NEW||View|
|32084||Diablo III: Crash on changing from fullscreen mode to window mode||UNCONFIRMED||View|
|32179||Diablo III: changing keyboard layout to nonlatin makes all letters to be questionmarks||UNCONFIRMED||View|
|33111||Graphical Artifacts in Diablo 3 on AMD Graphics||RESOLVED||NOTOURBUG||View|
|35990||keyboard becomes unresponsive in blizzard games||UNCONFIRMED||View|
Please note that due to syscall thunks requirements described in bug #45349, 64-bit Diablo III client will work only in Wine built with PE support.
Below workarounds should not be needed anymore to run the game. If you find that they are still required, please post it in the comments.
1. Extremely low performance with 64-bit game client
This should be fixed as of Wine 6.19 (commit link).
32-bit game client uses DirectX 9, while 64-bit client uses DirectX 11. For some reason the 64-bit client has abysmal performance (around 1-2 fps).
In order to get around this and have a usable fps, either 1) use the 32-bit client, or 2) use DXVK (not directly supported on AppDB).
(To use the 32-bit client, go to Battle.net App -> Settings -> Game Settings -> Diablo III -> "Launch 32-bit client (instead of 64-bit)".)
2. How to run the game on 64-bit systems
On systems with more than 4 GB of memory Diablo III sees an unusual amount of memory (from its perspective) due to differences in the memory layout on Windows and Linux. As a result of this, many aspects of the application will fail to function properly (including chatting, authenticating, and closing the game). To resolve this problem you need to run the game in particular way to tell Linux to use a Windows-like memory address space:
setarch i386 -3 wine '<path to Diablo III.exe or Battle.net Launcher.exe>'
3. How to fix audio with PulseAudio
Edit /etc/pulse/daemon.conf and add
default-fragment-size-msec = 5
After that the volume was really low and it appears that pulse volumes bars per application. so just clicking on the sound Icon, tools icon and going to Applications tab allowed me to adjust the volume of the game.
Tested on Alllen and Heath Zed 10FX USB sound card.