Diablo IV not launching

Thanks, I didn’t have those two packages. I’m trying it again. I uninstalled yesterday, so I need to download again… I should know in a while.

Edit: no change.

I got it working on Pop!_OS and nVidia but an running into the same issue you have on Manjaro w/ Radeon.

Symlink for libFLAC.so.8 made that output log error go away, but it still crashes.

I got it working on Manjaro w/ Radon.

Below is the log w/ it working

type or paste clutris-wrapper: Diablo IV
Started initial process 1858 from gamemoderun /home/psymin/.local/share/lutris/runners/wine/lutris-GE-diablo_4_beta-x86_64/bin/wine /home/psymin/Games/battlenet/drive_c/Program Files (x86)/Battle.net/Battle.net.exe
Start monitoring process.
gamemodeauto: 
esync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
[0614/195831.105:ERROR:network_change_notifier_win.cc(142)] WSALookupServiceBegin failed with: 0
[0614/195831.837:ERROR:network_change_notifier_win.cc(142)] WSALookupServiceBegin failed with: 0
[0614/195831.892:ERROR:dxva_video_decode_accelerator_win.cc(1405)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: Module not found. (0x7E)
Initial process has exited (return code: 0)
Monitored process exited.
Exit with return code 0
ode here

Using this wine runner

VKD3D 2.8

I made a symlink for the flac so but I’m not sure that did much.

Edit: Previously I tested before updating the system and it didn’t seem to work. Update and reboot and it worked.

I am also unable to get DIablo IV running on my Intel Graphics system, so far everyone I seen who got it running are doing so on NVidia or AMD graphics, so this could be an issue with running the game on Intel graphics (which to be fair is not even officially supported on Windows). I am running F38 and I tested with Lutris, with Steam and finally with GE Proton under Steam. All giving same result.

Away travelling atm, but hope to test on my NVidia system when I get home to verify.

I have a similar problem - it started after switching from zen Arch kernel to base and back - suddenly D4 wouldn’t start anymore. Reinstalled the kernel and headers, nvidia-dkms drivers (+dependencies), lutris flatpack, lutris native (and dep…), wine-stable from the AUR and from the base repositories, etc. etc. etc. No dice - D4 would always crash on start and kick me mack to the battle.net client… it does work on my other PC’s with zen kernel and current native install lutris, mind you, just not on my main gaming PC. As far as I can tell, the bad file discriptor errors have no impact, though, I get those on my radeon deasktop and hydrid graphics Thinkpad too, but the game runs perfectly fine there… the D4 crash comes without any errors in the lutris logs, it just, well, closes with an empty blizz error report. I’m at a loss…

@abacus I think I’m at a point where I’m just not going to try again until see an update to the Linux Intel graphics driver (last updated Apr 21 2023). Then I’ll try again with whatever updated install script Lutris has.

Last Epoch scratches the ARPG well enough anyway… I only bought Diablo IV because my niece and nephew did, and it would be nice to play together (I’m the “cool uncle”).

UPDATE: I got it to run by disabling/overriding the nvapi and nvapi64 DLLs in the runner configs. Not pretty, since it removes DLSS support from the game (and messes with the ground textures a bit, for some reason) but it works again.

Hello all,

I have the exact same problem here with my Intel Arc A770 on nixos. I am using Mesa 23.1.1 and kernel 6.3.4-zen1. I have tried many settings with lutris and bottles but the game always crashes at startup. It seems to be a problem with Intel cards. I am currently out of ideas. I guess we just have to wait until a new driver is released.

Hello all,

I’ve got the same issue with latest Lutris(lutris-GE-Proton8-8, VKD3D 2.8 as suggested) on Manjaro and Intel Iris Xe, and no helpful message from wine log, but if I activate the log on Diablo 4 (using launch parameter “-dredall” as suggested at Collecting Crash Log during the Beta - Technical Support - Diablo IV Forums ), I got some logs about the CTD of Diablo 4 with dump:

...
I 2023.06.19 09:42:53.962744    [Crash] Thread 'MainThread' handling fatal error
I 2023.06.19 09:42:53.962948    [Crash] UnhandledExceptionFilter
I 2023.06.19 09:42:53.963022    [Crash] Crashed thread: 'MainThread' (0x7b0)
I 2023.06.19 09:42:53.963146    [Sigma] --- OS memory stats -----
I 2023.06.19 09:42:53.963192    [Sigma] Virtual Mem Total: 63980.27 MB
I 2023.06.19 09:42:53.963233    [Sigma] Virtual Mem Used: 13737.78 MB
I 2023.06.19 09:42:53.963274    [Sigma] Virtual Mem Used by Process: 0.00 MB
I 2023.06.19 09:42:53.963314    [Sigma] Phys Mem Total: 63980.26 MB
I 2023.06.19 09:42:53.963353    [Sigma] Phys Mem Used: 13737.77 MB
I 2023.06.19 09:42:53.963393    [Sigma] Phys Mem Used by Process: 644.11 MB
I 2023.06.19 09:42:53.963432    [Sigma] --- OS memory stats end-----
I 2023.06.19 09:42:53.963525    [Sigma] Opening dump file
I 2023.06.19 09:42:53.963643    [Sigma] Dump file opened
I 2023.06.19 09:42:53.963695    [Sigma] Starting dump
I 2023.06.19 09:42:57.552292    [Sigma] Created dump after 1 attempts
I 2023.06.19 09:42:57.552764    [Sigma] Saved dump file to 'C:\Program Files (x86)\Diablo IV\Fenris-0.dmp'
----------------------------------------------
<ERROR-0>

UNHANDLED EXCEPTION: Unknown Exception (80000100) at:
DBG-OPTIONS<NoAddress NoFuncOffset NoImage>
DBG-ADDR<0000000170030158>("ntdll.dll")
DBG-OPTIONS<>
</ERROR-0>
I 2023.06.19 09:42:58.444494    [Crash] 
I 2023.06.19 09:42:58.444534    [Crash] <STACK-0>
I 2023.06.19 09:42:58.444573    [Crash] ------------
I 2023.06.19 09:42:58.444611    [Crash] Stack Crawl:
I 2023.06.19 09:42:58.444649    [Crash] ------------
...

I haven’t found any solution for this yet :frowning:

Edit: I found out that the address provided in the crash log above ( 0000000170030158 ntdll.dll ) is the same one from wine log:

wine: Call from 0000000170032288 to unimplemented function CFGMGR32.dll.CM_MapCrToWin32Err, aborting

So maybe this is the main error or side effect error (there is an unknown error in Configuration Manager Forwarder DLL “CFGMGR32.dll” which leads to the call of unimplemented function CM_MapCrToWin32Err) then crash?

Edit 2: I finally got it running!!, I saw the bug fixed in wine 8.6: Multiple apps crash on unimplemented function CFGMGR32.dll.CM_MapCrToWin32Err (Matrix Awakens MegaCity Unreal Engine 5.1 demo, Hogwarts Legacy)
https://bugs.winehq.org/show_bug.cgi?id=53781
So I switched to using system wine instead (which is currently 8.8 Staging in my Manjaro), tell the wine to simulate Windows 11 to bypass the check for Windows version.
In waiting for a fix in proton/GE version, I will see if I can really play this game, I got it to run somehow atm

Edit 3: Albeit the low fps (20fps @ 3440x1440 30fps @ 1920x1200) at lowest settings, the game is playable with wine 8.8

Edit 4: After tweaking around with game display setting in-game, when I switch back to lutris-GE proton 8.8, the error for CFGMGR32.DLL isn’t there anymore, but there is another error and CTD (maybe about DirectX12):

E 2023.06.19 14:24:50.788802    [Game] pm_api::PlatformInstance::CreateDevice: Unsupported API Backend - Error : Invalid, SystemCode : 0x00000000 (S_OK)
E 2023.06.19 14:24:50.788804    [Game] [Prism] CreateDevice failed - Error : Invalid, SystemCode : 0x00000000 (S_OK)

so system wine 8.8 at the moment for me

1 Like

Hey minhnim,

thank you very much you put me in the right direction.

I tried running the game with kron4ek-wine-8.10-amd64, dxvk 2.2 and vkd3d-proton-2.9 and oh wonder the game starts and is playable.

I used bottles to run the game. It’s very convinient for downloading and switching around with the runners.

So thanks again. See you all ingame!

greetings
cy

1 Like

Hello again,

here is a short update. The game is now running and it runs quite smoothly. I have around 50-60 fps at high preset in 4k. But from time to time when the game needs to load an animation that is a bit bigger. Maybe a big explosion or the effect of a shrine, the game then suddenly freezes. It’s as if the shaders for this animation are being compiled in the background and the game then freezes.

Here is the console output for such a case. Does anyone have an idea how to fix this problem?

9671.714:0974:082c:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
9671.714:0974:0830:err:vkd3d-proton:dxgi_vk_swap_chain_wait_and_reset_acquire_fence: Failed to wait for fence, vr -4
9671.714:0974:082c:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
9671.714:0974:082c:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
9671.714:0974:082c:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
9671.714:0974:0830:err:vkd3d-proton:dxgi_vk_swap_chain_submit_blit: Failed to wait for fence, vr -4
9671.714:0974:0830:err:vkd3d-proton:dxgi_vk_swap_chain_present_signal_blit_semaphore: Failed to submit present discard, vr = -4.
9671.714:0974:0830:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
9671.714:0974:0830:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
9671.714:0974:0830:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
9671.714:0974:0830:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.
9671.714:0974:0830:err:vkd3d-proton:d3d12_command_queue_signal: Failed to submit signal operation, vr -4.

I tested installing D4 on my Fedora Workstation NVidia system under Lutris and it worked without a hitch, so it seems that for me at least the problem is specific to trying to run Diablo 4 on Intel GPU.

I was able to finally get it to work on the A770 using:

Ubuntu 23.04 updated to latest mainstream kernel available using Ukuu
Installing the latest wine-staging version from the WineHQ repo
Using the system wine in Lutris, no other runners installed
Set DXVK to 2.1 and VKD3D to 2.8 as indicated above

60-70 FPS in town using the balanced XESS setting and med-high graphics settings

I tried installing multiple lutris runners and using the custom ones indicated above but would always get stuck with the CFGMGR32.dll.CM_MapCrToWin32Err error/bug. I assume this is the same thing that happens when trying to run natively in Steam as well. Hopefully it’s something that gets fixed in GE/Proton soon.

Relevant Mesa bug for this issue for those trying to get the game running on Intel is here:

Haven’t had any hangs at character selection, but the game does freeze on big explosions or sometimes when I portal as described above.

Hi @sl1n9bl4d3,

i am using Lutris + System Wine Staging + dxvk 2.1 + vkd3d 2.8 to run Diablo 4 on my Intel Arc A770. My Kernel is nixos 6.3.9 and I have Mesa 23.1.2 installed. But in the Game Settings there is no option for XeSS. Did you do anything special to get this option, or was it just there?

Does the game run stable for you or do you also have these freezes that I have already described above? I just saw you already answerd this. So it is a Problem in general.

Hello @cyriana,

The setting in the game is not called XESS specifically, it’s called FidelityFX Super Resolution 2, to my knowledge that equates to XESS on the Intel Arc chips.

The game does not run stable. I experience the same issues you described. The game will crash anytime there is a lot of stuff happening on screen and sometimes when portaling. I was able to get to run for longer by disabling the FidelityFX Super Resoultion setting in game completely, but it still crashed.

When it runs, the framerate is more than acceptable, but the constant crashing makes it unplayable still.

Hello again,

as it looks, XeSS is not supported or not recognized under Linux. Otherwise it would be displayed in the settings as follows:

FidelityFX Super Resolution 2 from AMD is somewhat comparable to XeSS, but Intel’s XeSS would certainly mean better FPS on the ARC graphics cards.

But as long as the problem with the freezes exists, reasonable gaming under Linux is not possible anyway. I have also already tested the latest GE-Wine version 8.10 from 02.07.23. Unfortunately the game still does not start with it. So we don’t need to get our hopes up at the moment.

I will later test if the fresh released dxvk version 2.2.3 brings an improvement.

I actually have the same problem on Zorin OS but it may just be my CPU. My Ryzen is parked for upgrades and as lady luck would have it my I7 motherboard popped 2 caps so now I am using an AMD A8-3870 with an RX470 which is fine for most stuff as I am a web developer so don’t need much more but… I wanted to play Diablo at least. Only Diablo 2 works on my PC not any other Diablo, not even Diablo 1 :confused: ( I did manually change diablo 1 to run DDraw which makes it compatible with Linux but still doesn’t display but Diablo 1 does start )

I have a pleasant update on the regular crashes. I finally got the game running stably. I’ve been playing for a while now and haven’t had a crash yet.

The solution:

I compiled Mesa 23.2.0-rc1 and installed it in my NixOS System. That’s it.

Also on my archbased Linux I could solve the problem this way.

greetings

Cy