Diablo III

I’m experiencing freez at Diablo 3 when using latest Wine, the game just freezes. These crashes happen at random times...
Running in terminal directly in Wine the following error message is generated at crashing:

076c:fixme:d3d_shader:shader_glsl_input_pack Unhandled sysval semantic 0x2.
076c:fixme:d3d_shader:shader_glsl_input_pack Unhandled sysval semantic 0x2.
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
06d4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
amdgpu: amdgpu_cs_query_fence_status failed.
amdgpu: The CS has been cancelled because the context is lost.
amdgpu: The CS has been cancelled because the context is lost.
amdgpu: The CS has been cancelled because the context is lost.
amdgpu: The CS has been cancelled because the context is lost.
amdgpu: The CS has been cancelled because the context is lost.
amdgpu: amdgpu_cs_query_fence_status failed.
amdgpu: The CS has been cancelled because the context is lost.
amdgpu: The CS has been cancelled because the context is lost.

- DeskMini X300, Ryzen 5700G
- Arch Linux 5.15.12-arch1-1
- Sway WM
- Latest (stable) Mesa driver

Hi all,

I am adding a comment in case anyone else experiences similar issues. I am running Diablo 3 on an AMD RX5700 but was experiencing awful lag and frame pacing issues. After much troubleshooting I recalled I "maxed out" my settings like I did in Windows so I reset the video settings but issues persisted. I then recalled I changed the audio settings, sound channels to be specific, to max as well, so I set them to default. This fixed my frame pacing and lag issues immediately! Make sure that if you changed sound channels to High (128) and experience issues to go back to Low (32). Now the game runs at max video settings and with sounds at default settings perfectly.

Every time I try to launch the 64-bit client, I get a stack overflow error. 32-bit works fine. Anyone else have this problem? Regression?

This is with wine-staging 5.16.

What is your OS/distribution? Are you using your distro's package, or did you compile Wine yourself?
Regarding regression, what's the last Wine version that is working for you?

The error message suggests you're probably hitting this bug:
bugs.winehq.org/show_bug.cgi?id=45349
You need Wine compiled with PE support for 64-bit Blizzard games to work.

Yeah, Slackware-current, so no builds are PE builds. There's no official build, per se. Time to investigate PE support... Thanks!

For PE support you "just" need to have mingw-w64-gcc installed when building Wine. Good luck ;)

Yeah, mingw-w64 is going to be a project, I think. I'm a bit surprised there isn't an official package for it.

Tried proton-ge with it, but get a black screen more often than not. It does actually load...sometimes.

Does not work on Wine 5.0 stable. Used dxvk-setup (dxvk package, Debian 10). Does not launch.
Switched Battle.Net to use 32bit loader. Launches, transparent screen followed by crash.
Tried disabling dx11 but that prevents Battle.Net from loading so I can't do that. Installed VC++ 2015.

I get a bunch of this which seems like it could be related.

013b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0x11.
013b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0x12.
013b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0xe.
013b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0xd.
013b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0x6.
013b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0xf.
013b:fixme:d3d:wined3d_query_gl_create Unhandled query type 0x5.
013b:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
013b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table.
013b:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
013b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table.
013b:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
013b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table.
013b:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
013b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table.
013b:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
013b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table.
013b:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
013b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table.
013b:fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
013b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table.
013b:fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
013b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table.
013b:fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
013b:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table.

Please see the "Wine version" note at the top – currently D3 works only in Wine Staging.

Just wanted to drop a comment here in case anyone else is having this issue and has a solve!

I recently upgraded from Wine Staging 4.8.1 -> 4.9.1 and it seems the update causes Diablo 3 to freeze with a grey screen at launch. Fiddled with it for a couple of hours and gave up, downgrading back to 4.8.1.

My staging settings are all unchecked and my only library override is d3d11 set to native. I wasn't sure if anyone else was having any luck using a larger patch suite, will give it another try later on and follow up.

Kernel: 5.1.8-arch1-1-ARCH
Nvidia: 430.26
DXVK: 1.2.1
Wine Staging: 4.8.1

vulkan-icd-loader: 1.1.108-1
lib32-vulkan-icd-loader 1.1.107-1

Hope this is helpful, let me know if I can add any additional info.

Please see bug 47265 [1]; it is fixed in 4.10.
Also, where did you get versions 4.8.1 and 4.9.1? Official releases are only at 4.8 and 4.9, there are no .1 versions.

[1] bugs.winehq.org/show_bug.cgi?id=47265

I would do a test result, but I'm not sure how this website really feels about installs patched massively... so I'll just post a comment instead.

Using a patch pack like github.com/Tk-Glitch/PKGBUILDS/blob/master/wine-tkg-git/README.md with DXVK, esync (and Plasma tray fix) the Diablo 3 64bit client runs pretty much flawlessly for me in a prefix set to Win10 with esync enabled.

Doesn't even have that weird issue I used to get where inventory items may take ~30 seconds to load properly.

Just some FYI for those interested.

I just realized that DVXK is mentioned in the notes for getting 64bit to work. Oops.

I am confirming that patching with DXVK works. I've tested using WINE 4.0-staging and patching with DXVK version 0.96 by copy pasting:

64 bit versions of:

d3d10_1.dll
d3d11.dll
dxgi.dll
d3d10.dll
d3d10core.dll

into the game prefix /Windows/System32 path, overwriting existing DLLs and

32 bit versions of the same above DLL files into the game prefix /Windows/syswow64 path, overwriting existing DLLs there as well.

Subsequently, adding these DLLs as overrides to the WINE configuration for the prefix allows for flawless play of the game using the 64 bit client.

I do experience some weird quirks with the Battlenet App, but turning off the option for "Allow the window manager to control the windows" in WINE seems to fix the Battlenet App problems for me (also using Windows 10 as the Windows version is a must).

This continues to work with WINE 4.5 staging patched with DXVK version 1.01 for both 64 bit and 32 bit clients. No quirks.

Continues to work with WINE 4.6 staging patched with DXVK verison 1.03 for both 64 bit and 32 bit clients. Narrowed down the winecfg overrides to only requiring the dx11 (native windows) override added. The other typical DXVK overrides are unneeded, but the dlls still appear to need to be copied over into their respective 64bit(/system 32) and 32bit(/syswow64) paths of the prefix.

Still works for 4.7 staging patched with DXVK version 1.03 using only the winecfg override for d3d11 (native windows).

To avoid getting a hanging game with a blank grey screen I had to deactivate an option in winecfg:

deactivate winecfg --> tab "staging" --> option "Enable CSMT for better graphic performance (deprecated)"

Has anyone tried or gotten this to work? The game runes flawlessly on 3.19 staging with DXVK .90 but if I try to install/use ReShade it just crashes on startup.

I made it the last time with POL, but that doesn't work any more either.
Now i tried it simply with the latest wine-staging (3.18)
I was able to install the Battle.net client without problems. By running this command: sudo apt-get install p11-kit-modules:i386 p11-kit:i386 i also had no problems with the login-screen. It worked without problems (no missing graphics, no ugly buttons/login-fields).
But then, when you hit the "Install" button it stops working. The window for the installation pops up, the waiting animation starts, but then nothing more. The animation keeps running forever.
die-lappenbude.de/images/ssdiainstall.png

Little update:
for whatever reason sometimes at first start of the BN app i get the install sconfig window shown, but hitting the "install now" button simply does nothing.
die-lappenbude.de/images/ssdiainstall2.png

I tried some things, I deleted the Cache folder of Diablo and now it downloads the game.
Solved for now.

This problem is described on Battle.net App's page, in "Cannot install or update games" note: appdb.winehq.org/objectManager.php?sClass=version&iId=28855
You will almost certainly encounter this issue in the future when updating games / the app. Unfortunately there doesn't seem to be any permanent way to fix it, you have to delete product.db file every time this happens.

It begins with Wine 2.19 Staging and use Windows 10 as the Windows version. You will get the error message, and the login and password window comes up. Instead of logging in, click the settings gear icon and a dropdown menu appears, at the bottom of the dropdown, click Continue Without Logging In. This will get you to the option that will allow you to click play. After the game boots up, it will ask you for your login and password.

This is currently working for me. I've logged in a few times to play. The success is repeatable.

What is the issue that requires workaround? Most people seem to be able to launch D3 without problems through the Battle.net App. Also, Staging version 2.19 is really old – you should try with newer versions (e.g. 3.6).
If you still need the workaround, you can do it in a simpler way: go to the game's directory and run
$ wine 'Diablo III.exe' -launch
This will launch D3 directly, completely skipping BN App.

I can play D3 with dx9 just fine by forcing 32bit. But with Blizzard dropping support for other games with DX9, I figure it is only a matter of time before DX9 will stop working altogether.

DX11 however is 1 fps max atm, is there any fix for that?

Has anyone tested the new wine-staging branch on Diablo III?

Yeah, it works the same as staging 2.21, plus there are performance improvements from Wine 3.0+ (and no need to manually kill Battle.net.exe anymore).

can someone verify: I was having occasional mouse freezing in gnome. The mouse would click but not move. The suggested fix was to remove libinput and replace with evdev. I did that and it solved my mouse issue. I just tried in d3 and the problem seems to have gone away. running the lastest 2.21-staging. Now i dont know if there was a fix to wine-staging or the replacement of libinput.

crap... put it in wrong spot

Mouse freezing only occurs for me in full-screen. Playing in Windowed or Windowed Fullscreen stops the bug from triggering.

For me, in order to stop the mouse-downs-register-as-mouse-clicks problem in Diablo 3 2.6.1 with wine-staging 2.21, I had to recompile wine with the right patch. I'll attempt to explain how to do this here.

Step 1: Compile (build) wine. Instructions are here: wiki.winehq.org/Building_Wine. Make sure you build wine 2.21 and not some development version. You can get wine 2.21 source with git, or you can get it here: ftp.winehq.org/pub/wine/source/2.x/wine-2.21.tar.xz

Step 2: Download wine-staging 2.21 source. You can get it with git, or you can get it here: github.com/wine-compholio/wine-staging/archive/v2.21.tar.gz

Step 3: Apply the patch "kernel32-SetFileCompletionNotificationModes" from wine-staging using patchinstall.sh:
./patchinstall.sh DESTDIR=../../wine-source kernel32-SetFileCompletionNotificationModes
replacing "../../wine-source" with the path to your wine-2.21 source. Note that you have to be in the wine-staging "patches" directory when executing patchinstall.sh.

Step 4: Rebuild wine (both configure and make).

Of the four above steps, the most difficult and painful, by far, is the first step, because you need to install lots of development stuff on your computer in order for wine to compile. But you ought to be able to complete all four of the above steps in half an hour or so, assuming you don't get lost.

Hopefully, the patch "kernel32-SetFileCompletionNotificationModes" will start being included in non-staging wine soon so that we don't have to do all this in order to play Diablo 3.

Well, I just tried playing Diablo 3 again after a couple of months away, and the patched wine I described creating in my previous message no longer works: Diablo 3 won't start. Blizzard has released more patches for Diablo 3. The current version is 2.6.1.49508; the patched wine I made in November worked with 2.6.1.47919. Apparently Blizzard made major changes to Diablo 3 between 2.6.1.47919 and 2.6.1.49508. I tried the latest wine, version 3.2, and it didn't work either. For some unknown reason, the latest version of wine-staging is still 2.21. I see that someone has posted three new bug reports (44585, 44616, and 44617) about the problem. Those bug reports seem to suggest that Diablo 3 2.6.1.49508 will work with a properly patched wine. I found that wine 2.21 with all but one of the patches in wine-staging 2.21 works. So I'm posting this message to explain how.

In my four-step procedure above, replace the command line in step 3 with:
./patchinstall.sh DESTDIR=../../wine-source --all -W server-send_hardware_message

This command line will, instead of adding the single patch "kernel32-SetFileCompletionNotificationModes", add all patches except "server-send_hardware_message".

There's probably some minimal set of patches that will make it work, but I don't have the patience right now to figure out which ones. I hope this helps.

> For some unknown reason, the latest version of wine-staging is still 2.21.
The reason was announced here [1]. Fortunately new maintainers took the project [2] an it has just been bumped to version 3.3 [3].
You might want to check this new version to see what works and what doesn't. I am using it all the time, but I can't reproduce the mouse-down issue, so I don't know if it was fixed or just doesn't appear for me.

[1] wine-staging.com/news/2018-02-17-future-wine-staging.html
[2] www.winehq.org/pipermail/wine-devel/2018-February/123080.html
[3] github.com/wine-staging/wine-staging/commits/master

I've just tested with the new wine-staging 3.3, and the problem is unchanged. With all patches included, the mouse-downs-register-as-mouse-clicks problem is present for me. If I leave out the single patch "server-send_hardware_message", then the problem does not occur.

Thanks for your hints.
I used the unlimeted backgroudn and foreground FPS and the single Core command.
It seems to work so far.
Single click problems did not solve this way. In Addition I closed the battl.net app. Did not work neither.
Thanks for the hints

i am getting a bug that my char just stops moving when holding down button. Didnt have this issue prior to 2.6.1 of D3. I have gotten around the problem by using setarch and forcing 32bit and enabling virtual desktop in winecfg. Can someone confirm that they have the same issue? Running 2.20 staging.

i should add it just stops at the last place i clicked instead of following the mouse.

I did not experencie the problem you describe – my character correctly follows the mouse when it's held down. I'm running also on Wine Staging 2.20, with a 64-bit Win 7 prefix. I did however encounter the problem described in bug #31262, when I had Lock Cursor option enabled; I am now launching D3 without virtual desktop, in Windowed Fullscreen mode, and with Lock Cursor disabled, and I have no problems with mouse cursor.
Maybe your issue is somehow related to display settings – what is your video configuration in D3?

3840x2160@60. I been using fullscreen, but will try the window and see if i can reproduce.

i just tested with window (fullscreen) and it works much better. Never thought of using that. Thanks for the tip.

can confirm that on 2.20 and patch 2.6.1 on full screen i will test it in window mode too

I am also seeing this problem. Diablo 3 usually (but not every time) acts like I've clicked when I'm actually holding the mouse button down. I tried fullscreen, windowed, and windowed-fullscreen, and that didn't have any effect. I tried configuring wine with and without a virtual desktop, and that had no effect. I'm running wine-staging 2.20 with Diablo 3 2.6.1.47919.

try using setarch also. I had to use that with the virtual desktop and windows (full)

Okay, I've now tried all 16 settings combinations, and seen the problem on all 16 combinations. The combinations are: both with and without "setarch i386 -3"; with and without wine set to use a virtual desktop; Diablo 3 set to fullscreen, windowed, or windowed-fullscreen mode; and, for windowed-fullscreen mode, both with and without Diablo 3's lock-cursor-to-window option.

After a great deal of work, I've found a workaround for this problem that works for me. The culprit seems to be the patch "server-send_hardware_message", one of the 440 patches that are part of wine-staging 2.20 and not part of wine 2.20. With wine recompiled without this patch, the problem disappears: my mouse-button holds register as mouse-button holds, not clicks. I also found that the only patches needed to make Blizzard app and Diablo 3 work with wine 2.20 are the patches "kernel32-SetFileCompletionNotificationModes" and its prerequisite "ntdll-FileNameInformation", and not the 438 other patches in wine-staging 2.20.

Ive installed it and it works for 32bit but the launcher is very very slow. It seems that it only uses one of my six cpu cores.
in the D3 Forums i found a workaround with a Program (UnparkCPU) that forces windows to use all cores but this doesnt work in wine(or at least i dont know how)

tried to install it on 64, but launcher doenst start after installation.
tried wine 2.20 and 2.18 but the launcher crashes after 1 second (debug shows some wierd stack overflow)

massivelyop.com/2017/08/16/diablo-iii-is-testing-item-changes-and-no-xp-support-for-its-next-patch/

Has anyone tried the PTR? Any changes we need to make?

uho, it means no directx 9 support anymore, and since directx 11 is not up to par yet (it works, but in the single digit fps)

I've been trying the PTR, and the past two patches, everything's been fine. They still list a lot of older video cards for recommended hardware (but have Windows 7 as the lowest version of windows), so I'm thinking dx9 isn't going away.

I didn't try the PTR, i tried the live patch. Since XP support is droped the game doesn't start anymore in 32 bit mode.
a) winecfg set to WinXP/2003 : Error msg at start is "Winvers not supported anymore" use at least win7
b) winecfg set to Win7 and above ... the game does nothing, not even the logo on startup.
c) 64bit game still doesn't run smooth. it is VERY slow but it is starting.

Huh. Are you using staging? I've got things set to Windows 7, and am using 32-bit fine. (This was the same day the patch launched.)

I'm set to Windows 10, sorry. And I'm using a 64-bit wineprefix, but running 32-bit Diablo III. I'm currently using wine-staging 2.17. (Been too lazy to upgrade to 2.19.)

Hi,
i habe a 64bit prefix too and use 2.19 staging, tried 2.17 before, the game was running perfectly until i got the patch.
I tried win7 - win10. When i start the game (from bnet or directly) the game seems to start, i'll get a process running (can seet is in the ps-list) but on the monitor it does nothing (not even the logo)

Have you maybe tried with a clean wineprefix? I'm also using 64-bit prefix on 2.19 staging with win7, and I have no problem running the game (although, like you said, the logo is not displayed – just after a couple of seconds the game launches).
If it still doesn't work, is there maybe something interesting in the logs when you start the game directly? Or, do you have any dll overrides set (none should be needed for Diablo III)?

Sure, i tried a new 64bit wineprefix too but my blizzard games are not installed in wine. i took them directly from my win7 partition. The games are all in their own subdirs on this mountpoint.

As i could find out - the problem itself was hosted by the nvidia driver from the debian sid tree, as i updated this driver the last time i got also some bad performance in worldofwarcraft too. so i removed every sid package depending the nvidia driver and downloaded the latest original one from the nvidia website. after the install everything is running fine now as before the patch.

:-)
thx 4 help
S.

could you explain how you did install that on 64?
im trying it but it wont work.

Found out the trick is to reinstall IE8 (and maybe dotnet4.5 , 4.6 .. )

But was getting weird errors with winetricks. Found out, the version I had of winetricks was too old.
I am using Ubuntu , so I replaced the winetricks in /usr/bin with the one from :
raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks

then I did a : winetricks --force ie8 , and it worked.

took me awhile to figure that one out :)

finally got Diablo 3 RoS to install and show up properly at the login screen for the game, however all attempts to log in give me the message "There was a problem logging in. (Code 7)". anyone happen to come across this here and was able to get past it?

also I'm not able to log into battle.net at all through the Blizzard App client... is this normal?

Windows 10 Wine 2.11 staging 32 bit
Linux Mint 18.1

Diablo has been working fine for me, but I've never been able to see much of the stuff on the battle.net app which didn't bother me. Now that the necromancer is out, there is a promotional splash page on diablo 3's section of battle.net, which covers the play button. The problem is that the X in the top right corner used to close the promotion does not appear. I've tried clicking where it should be, messing with some settings, but I really don't know what to do here.

using wine-2.8 and winetricks-20170614 on Slackware64 14.2, while also having installed corefonts, ie8, and vcrun2015 along with adding d3dcompiler_47 in winecfg. install went fine, however when I start the game I can hear the music playing however my screen is black. any suggestions? running nvidia 375.39 binary drivers as well.

this is what shows in terminal

err:d3d:wined3d_debug_callback 0xa8cae60: "GL_INVALID_OPERATION error generated. Source and destination dimensions must be identical with the current filtering modes.".

any suggestions??

I've had quite some trouble installing the game and getting it to work. After figuring it out, I've noticed all is already well documented in Wine under Blizzard App. Don't forget to look there.
After resolving all, mainly vcruntime140 and installing lib32-libldap, lib32-gnutls, everything works like charm :) great gameplay and performance. Enjoy.