WineHQ

Diablo III

Current version of the game

Application Details:

Version: Current
License: Retail
URL: https://diablo3.blizzard.com
Votes: 34
Latest Rating: Platinum
Latest Wine Version Tested: 9.9-staging

Maintainers: About Maintainership

No maintainers. Volunteer today!

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Installing/Updating works fine.

Launcher works exactly how it should.

Game starts and runs either with wine "Diablo III.exe" -launch, or simply pressing play on the launcher like you would on Windows.

Login screen works fine, including Authenticator entry screen.

All sounds work fine, no sound glitches or anything of that kind were found during any tests.

All cinematics play wonderfully.

All in-game graphics are very smooth with no special patches or anything required. (NVidia users with graphics driver NV-295.49 and older WILL NEED TO UPDATE to NV-295.52 or NV-302.07Beta to run the game, this is a graphics card/driver issue, not a WINE issue however)

All game UI elements, including but not limited to Game menu, friends list, chat, achievements, inventory, companion inventory, skill list(and all sub-trees), all Blacksmithing and Jeweling UI elements, quest/lore UIs, action bars, health bars over player and NPC heads, health and mana/hatred/disciplin/rage/spirit orbs. Ect.

What does not

Of all the things in the game there is only 1 problem I can detect, HOWEVER, im not sure if this is a WINE glitch or not, but when you are running in fullscreen or Windowed-Fullscreen, and you change the window type to Windowed, where the boarders appear, you are still unable to make the mouse LEAVE the game, and must completly close the game after changing the display to Windowed, for you to be able to treat it like a normal program window. However, if you start the game in windowed mode already, this glitch does not appear, until you set it to fullscreen or windowed-fullscreen mode again.


Workarounds

What was not tested

Everything was tested. Multiple character class and gender combinations were tried several times in all 4 acts on normal, hardcore, nightmare, and hell difficulties. Multiple bnet accounts were used in testing, no visible problems with using diffrent bnet accounts for login.

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

Installs, launches, and plays well with AND WITHOUT patches, patches are NOT required for me to install launch, update, and play the game. HOWEVER wether you have patches or not, you will require winetricks vcrun2008 inorder to launch the game, otherwise the splashscreen will appear, disappear, and Diabli III.exe will hit a Nlock I/O exception and Seg-fault error and close. Overall approx. 24hours in testing by multiple people on the same and diffrent computer with a total of 18 diffrent characters played during the tests. Tested with both NVidia AND ATI graphcis cards. NOT TESTED WITH INTEL GRAPHICS CARDS. I cannot tell you what intel will do, probably wont have any problems tho. PC specs of the main computer used in testing(approx 18hrs in total on this computer alone) AMD Athlon II X2 250 3.1GHz NVidia GeForce 450 GTS with NVidia-302.07Beta graphics driver. Fedora 16-64bit with Linux kernel 3.3.5 Wine version 1.5.4(patched AND unpatched were both tested) Using LDXE desktop enviorment with XFCE panel and Compiz-Fusion ***All test data outlined in above sections was collected and recorded using Wine 1.5.4-unpatched with winetricks vcrun2008 on Fedora 16 64bit OS running an AMD Athlon II x2 chip (speeds and GHz varies) with NVidia 450 GTS or better(and ATI equivilent) graphics cards.***

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowLinux Mint 21.3May 28 20249.9-stagingYes Yes NoPlatinumDaniel Dias 
ShowUbuntu 20.04 "Focal" (+ variants like Kubuntu)Sep 24 20227.17Yes Yes NoPlatinumAcridwax 
ShowUbuntu 20.04 "Focal" (+ variants like Kubuntu)Aug 30 20227.16Yes Yes NoPlatinumAcridwax 
ShowUbuntu 20.04 "Focal" (+ variants like Kubuntu)Aug 29 20227.15Yes Yes NoPlatinumAcridwax 
ShowDebian GNU/Linux 11.x "Bullseye" x86_64Aug 03 20227.14Yes Yes NoPlatinumAcridwax 

Known Bugs

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

Show all bugs

HowTo / Notes

Wine version/build

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.

[OBSOLETE] Workarounds

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.

Comments

Comments Disabled

Comments for this application have been disabled because there are no maintainers.
Back