I’m experiencing freez at Diablo 3 when using latest Wine, the game just freezes. Tested on Alllen and Heath Zed 10FX USB sound card.

so just clicking on the sound Icon, tools icon and going to Applications tab allowed me to adjust the volume of 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 ''Įdit /etc/pulse/nf and add default-fragment-size-msec = 5Īfter that the volume was really low and it appears that pulse volumes bars per application. As a result of this, many aspects of the application will fail to function properly (including chatting, authenticating, and closing the game). 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.

(To use the 32-bit client, go to App -> Settings -> Game Settings -> Diablo III -> 'Launch 32-bit client (instead of 64-bit)'.) 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). For some reason the 64-bit client has abysmal performance (around 1-2 fps). This should be fixed as of Wine 6.19 ( commit link).ģ2-bit game client uses DirectX 9, while 64-bit client uses DirectX 11. Extremely low performance with 64-bit game client

If you find that they are still required, please post it in the comments.ġ. Below workarounds should not be needed anymore to run the game.

Diablo 3 patch 3/4/2018