Diablo III

What works

Installation

Playing the game, auction house, network play, single user play.

The games runs smoothly, there are no lags, even on that test machine with a relatively slow Graphic adapter (nVidia GT240)

Sound

Embebbed videos

What does not

Changing the resolution crashes the option module (preferences), but after restarting the game, the new settings are applied and the game runs using the new screen resolution

Workarounds

What was not tested

Diablo seems to be an endless game, obviously not everything has been tested

Hardware tested

Graphics:

• GPU:
• Driver:

Additional Comments

Because of the crash of the resolution and the endless loop in HD res by login could not rate it as Platinum. The game started without any problem after install (in low res) and the log in could complete. With 1920x1024 display resolution, the game could not log in (endless loop when loading heroes) starting it with : setarch i386 -3 wine Diablo\ III.exe -launch solves the problem. User MUST be member of the video group otherwise the games crashes at startup. Additional info : Intel DualCore 2Gb RAM nVidia GeForce GT240 1Gb RAM NVIDIA graphics driver kernel module nvidia-gfxG02-kmp-desktop Version: 295.49_k3.1.0_1.2-16.1 x86_64 (out of the nvidia repo) OpenSuse 12.1 out of the box,with OBS wine and Packman repo activated Kernel 3.1.10-1.9-desktop

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.

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.