Current version of the game
- Battle.net application and setting the game client to 32bit mode
- Changing in-game settings - video, audio, key bindings
- Access to Leaderboards, User profiles etc.
- Game play
What does not
- Start-up logo is missing (bug 32083)
- Loading of item icons may take a few seconds. This often happens in Act V.
- Used 32bit game client
What was not tested
- Game play in 64bit mode
- Social features (clans, communities, ...)
- Season play as no season is running at the date of this testing
- Using Lubuntu 16.04
- Missing start-up logo does not impair the game in any way
- Missing item icons gets resolved by moving to another act. Act II seems to work the best.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Debian GNU/Linux 9.x "Stretch" x86_64||Jun 16 2019||4.10-staging||Yes||Yes||Yes||Gold||Acridwax|
|Show||Debian GNU/Linux 9.x "Stretch" x86_64||May 03 2019||4.7-staging||Yes||Yes||Yes||Gold||Acridwax|
|Show||Debian GNU/Linux 9.x "Stretch" x86_64||Apr 20 2019||4.6-staging||Yes||Yes||Yes||Gold||Acridwax|
|Show||Debian 9 (Stretch)||Mar 22 2019||4.4-staging||Yes||Yes||No||Garbage||Acridwax|
|Show||Debian 9 (Stretch)||Mar 22 2019||4.4-staging||Yes||Yes||Yes||Gold||Acridwax|
|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, GO 1.4+ runtime)||STAGED||View|
|30849||Diablo 3: Hangs on "Authenticating Credentials"||RESOLVED||ABANDONED||View|
|30920||Diablo 3: Random freezes||CLOSED||WORKSFORME||View|
|30967||Diablo III: Resolution problems without virtual desktop||UNCONFIRMED||View|
|30993||diablo 3 d3d device error||UNCONFIRMED||View|
|31072||Diablo III: Sound is very quiet||UNCONFIRMED||View|
|31262||Diablo III in game mouse cursor Out of sync, hangs in place.||UNCONFIRMED||View|
|31839||Mouse jumps to the upper left corner of the screen||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|
|32212||Mouse cursor not released from Blizzard based games||CLOSED||ABANDONED||View|
|33111||Graphical Artifacts in Diablo 3 on AMD Graphics||RESOLVED||NOTOURBUG||View|
|33413||Diablo III: Intermittent non-responsive UI elements||CLOSED||ABANDONED||View|
|33686||Diablo III: Audio cuts out after a while of game play||CLOSED||ABANDONED||View|
|34451||divide by zero in diablo 3||CLOSED||ABANDONED||View|
|35990||keyboard becomes unresponsive in blizzard games||UNCONFIRMED||View|
|37984||Diablo 3: Video card missing required features||CLOSED||ABANDONED||View|
|39261||Battle.net launcher 188.8.131.520 sometimes fails to start, reporting 'Battle.net requires the Windows Secondary Logon service to be enabled.' (error code BLZBNTBTS00000025)||CLOSED||INVALID||View|
|42191||Multiple games require d3d11 deferred contexts (Diablo 3, Dark Souls 3, The Evil Within, Elex, Alien: Isolation)||STAGED||View|
|44032||Diablo 3 2.6.1: Mouse-downs register as mouse clicks||CLOSED||FIXED||View|
|44585||Multiple applications and games need ntdll.LdrRegisterDllNotification/LdrUnregisterDllNotification implementation (Firefox 60+, Diablo III v2. 6. 1. 49286+, World of Warcraft, Overwatch)||CLOSED||FIXED||View|
|44616||Multiple Blizzard games need 'ntdll.NtCreateThreadEx' implementation (Diablo III v2. 6. 1. 49286+, World of Warcraft, Overwatch)||CLOSED||FIXED||View|
|44617||Multiple Blizzard games need Win7+ 'user32.GetWindowDisplayAffinity' and 'user32.SetWindowDisplayAffinity' stubs (Diablo III v2. 6. 1. 49286+)||CLOSED||FIXED||View|
|45443||Diablo 3: Starting the game causes a black screen softlock on the X-environment||UNCONFIRMED||View|
|47265||Multiple Blizzard games (Diablo III, Heroes of the Storm, Overwatch, Starcraft, StarCraft II, World of Warcraft) crash immediately on launch||CLOSED||FIXED||View|
Please note that due to bug #45443, Diablo III will work only in Wine Staging. The game will not launch in vanilla Wine (both stable and development releases) until the patch for this bug is integrated.
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.