Current version of the game
Everything works. I've played the game for several seasons totaling hundreds of hours.
What does not
Inventory item icon lag. Town for Act II is the only act where the lag is minimized to the point where the game is playable both solo and with other players both public and private. The presence of additional players tends to exacerbate the inventory item icon delay. Again, town for Act II is the only place where the inventory icons load in a reasonable amount of time. Town for Act V has the worst load time of inventory item icons next to town for Acts III and IV. Town for Act I is second to town for Act II. Setting texture quality to low only improves delay by a very slight difference. Configuring all of the remaining graphics settings to low or off also only collectively yields a marginal improvement to the delay.
This item icon delay also applies to certain items dropped on the ground. In particular, crafting materials like deathsbreath and some legendary items may be delayed for a significant amount of time before showing up on screen. I've noticed this to be especially true on map tile sets with a great deal of content (memory related?) and even more so when other players are present in the game.
I believe both item icon issues above are related because the marginal improvement provided by setting all graphics settings to low applies to both.
Do inventory management in the town for Act II.
What was not tested
Would be a platinum rating if not for the item icon lag or delay.
Intel i-7-3770K 3.5GHZ
Geforce GTX 970
32 GB RAM
|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|
|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)||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.