Current version of the game
Everything including seasonal heroes.
What does not
What was not tested
Opening a game to public.
I downloaded the latest Battle.net client, installed it, and then install Diablo III using the client. It worked like a charm with no workaround or extra steps.
Note: due to bug bug #45443 Diablo III always needs the very latest version of wine staging. So, if my Diablo III starts acting funny or doesn't load at all, I always check for an update for wine staging.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Arch Linux x86_64||Nov 05 2021||6.20-staging||Yes||Yes||No||Platinum||deap|
|Show||Ubuntu 20.04 "Focal" (+ variants like Kubuntu)||Apr 09 2021||6.5-staging||Yes||Yes||Yes||Gold||Acridwax|
|Show||Fedora 33 x86_64||Dec 27 2020||6.0-rc3-staging||Yes||Yes||Yes||Gold||Katharina|
|Show||Debian GNU/Linux Testing "bullseye"||Jun 21 2020||5.0.1||Yes||Yes||Yes||Gold||sney|
|Show||Debian 10.x "Buster"||May 21 2020||5.8-staging||Yes||Yes||No||Platinum||pioruns|
|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.
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)".)
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. 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>'
2. 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.