Current version of the game
Installation, 2 factor authentication, character creation, single player, multi-player, auction house, item trading, game updates, creating games, joining games, player profile.
What does not
Changing resolution and graphics settings works, but when you apply the settings the game crashes. Kill the game, then re-launch it and the settings you applied will have been set.
Also, to install and play the game you need to follow very specific instructions. Read my "extra comments" for the steps you need to follow to install and have the game run flawlessly.
What was not tested
PVP, because the feature is not enabled yet.
It's suggested that you create a stand-alone installation of wine for specifically for Diablo 3. Name it wine-d3, or something meaningful. To do this, set the following environment variables by entering the following into a terminal: WINEARCH=win32 WINEPREFIX=$Home/.wine-d3 winecfg Now install wine. This will create a directory under your home directory called .wine-d3 using a win32 architecture. *IMPORTANT* when installing from DVD media, make sure the DVD is mounted in "unhide" mode. I don't believe this step is needed if you are installing from the BNet download. Example: mkdir /media/Diablo3 umount /dev/sr0 mount /dev/sr0 /media/Diablo3 -o unhide Launch the D3 installer with wine. Wait for the installer to finish, then run the game. Any game updates will also be downloaded and installed during this time. To create a shortcut for the D3 launcher, create a shortcut that executes the following command: env WINEPREFIX="[path to wine instance]" setarch i386 -3 wine C:\\windows\\command\\start.exe /Unix [path to wine instance]/dosdevices/c:/users/Public/Start\ Menu/Programs/Diablo\ III/Diablo\ III.lnk The important parts of the command are the environment, D3 needs to be told to run in 32 bit mode, and -3 configures the memory setting for 32 bit mode. If you try to run the game with more RAM, it will hang when it attempts to retrieve your character list.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Manjaro Linux 19.0||Mar 26 2020||5.4-staging||Yes||Yes||No||Platinum||Jus de Patate_|
|Show||Manjaro 19.0.0||Mar 07 2020||5.2-staging||Yes||Yes||No||Platinum||Mustafa Yedibaba|
|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|
|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|
|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|
|33111||Graphical Artifacts in Diablo 3 on AMD Graphics||RESOLVED||NOTOURBUG||View|
|35990||keyboard becomes unresponsive in blizzard games||UNCONFIRMED||View|
|42191||Multiple games require d3d11 deferred contexts (Diablo 3, Dark Souls 3, The Evil Within, Elex, Alien: Isolation, Assassin's Creed III)||STAGED||View|
|45443||Diablo 3: Starting the game causes a black screen softlock on the X-environment||UNCONFIRMED||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.