Current version of the game
Application Details:
| Version: | Current |
| License: | Retail |
| URL: | https://diablo4.blizzard.com |
| Votes: | 1 |
| Latest Rating: | Gold |
| Latest Wine Version Tested: | 8.21-staging |
Maintainers: About Maintainership
What works
Everything seems working by launching it from Lutris, after applying the workaround to disable Intel XeSS.
CPU: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
GPU: Mesa Intel(R) HD Graphics 520 (SKL GT2) (Gen9)
OS: Arch Linux
Runner: Lutris (wine-ge-8-22)
DXVK: 2.3
VKD3D: 2.11
D3DExtras: v2
What does not
With a GPU Intel Gen9, the game crashes duing startup due to Intel Xess.
A log with the error can be found in C:\Program Files (x86)\Diablo IV\FenrisDebug.txt, which contains something like this:
I 2023.11.28 23:16:12.723986 [Game] [Prism] XeSS supported, initializing for Intel family Gen9 (7)
I 2023.11.28 23:16:12.774987 [Crash] Thread 'MainThread' handling fatal error
I 2023.11.28 23:16:12.781436 [Crash] UnhandledExceptionFilter
I 2023.11.28 23:16:12.781922 [Crash] Crashed thread: 'MainThread' (0x5d4)
I 2023.11.28 23:16:12.782487 [Sigma] --- OS memory stats -----
I 2023.11.28 23:16:12.782788 [Sigma] Virtual Mem Total: 24113.12 MB
I 2023.11.28 23:16:12.782994 [Sigma] Virtual Mem Used: 4424.10 MB
I 2023.11.28 23:16:12.783229 [Sigma] Virtual Mem Used by Process: 0.00 MB
I 2023.11.28 23:16:12.783444 [Sigma] Phys Mem Total: 7729.12 MB
I 2023.11.28 23:16:12.783654 [Sigma] Phys Mem Used: 4040.82 MB
I 2023.11.28 23:16:12.783976 [Sigma] Phys Mem Used by Process: 602.28 MB
I 2023.11.28 23:16:12.784240 [Sigma] --- OS memory stats end-----
I 2023.11.28 23:16:12.784645 [Sigma] Opening dump file
I 2023.11.28 23:16:12.785188 [Sigma] Dump file opened
I 2023.11.28 23:16:12.785414 [Sigma] Starting dump
I 2023.11.28 23:16:25.940550 [Sigma] Created dump after 1 attempts
I 2023.11.28 23:16:25.943480 [Sigma] Saved dump file to 'C:\Program Files (x86)\Diablo IV\Fenris-0.dmp'
----------------------------------------------
<error-0>
UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005) at:
DBG-OPTIONS<noaddress nofuncoffset="" noimage="">
DBG-ADDR<000000001A9426CA>("XeFX_Loader.dll")
DBG-OPTIONS<>
</noaddress></error-0>
Even disabling XeSS from the Diablo config file does not change anything.
Workarounds
After some reverse engineering of the XeFX_Loader.dll, I figured out that there is an environment variable that disables the XeFX_loader:
XeFX_xess_ForceLoaderPath=C:\whateveryouwant.dll
After setting this variable, Diablo 4 starts and runs smoothly.
What was not tested
Played just 1h and tested basic stuff (menu, gameplay). Everything seems working.
Hardware tested
Graphics:
Additional Comments
| Operating system | Test date | Wine version | Installs? | Runs? | Used Workaround? | Rating | Submitter | ||
| Current | Arch Linux x86_64 | Nov 28 2023 | 8.21-staging | Yes | Yes | Yes | Gold | Alain | |
| Show | Fedora 38 x86_64 | Jul 06 2023 | 8.11-staging | Yes | Yes | Yes | Gold | XOR | |
| Show | Arch Linux | Jun 13 2023 | 8.10-staging | Yes | No | Yes | Garbage | Maciej Stanczew | |
| Show | Arch Linux | May 12 2023 | 8.7-staging | Yes | No | Yes | Garbage | Maciej Stanczew | |
| Show | Arch Linux | Mar 26 2023 | 8.4-staging | Yes | No | Yes | Garbage | Maciej Stanczew |
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by XOR on Tuesday August 22nd 2023, 8:21
wine-8.13 (Staging) wont working and wine-8.14 (Staging) too.
Use wine-8.12 (Staging).
by Timothy on Monday August 21st 2023, 13:53
Also,
d3d_extras_version: v2
dxvk_version: v2.2
vkd3d_version: v2.9
How do we install these? winecfg, winetricks, manually... For example, I can't find d3d_extras_version anywhere.
Thanks.
by Maciej Stanczew on Tuesday August 22nd 2023, 15:49
What exactly is this issue? Is it GPU dependent? I'm running the game just fine without getting such error.
> How about the library overrides with winecfg? Do we have a definitive list?
d3d12, d3d12core, dxgi
First two should be created when installing VKD3D-Proton, and last one when installing DXVK.
> For example, I can't find d3d_extras_version anywhere.
Who told you to install it? It shouldn't be required to run the game.
by Timothy on Tuesday August 22nd 2023, 16:43
Okay, I'll recheck my dll overrides. And the d3d_extras_version is listed above.
by XOR on Friday July 7th 2023, 1:42
Fedora 38 64bit.
?I used wine-staging from WineHQ repository, also working on Kron4ek?: github.com/Kron4ek/Wine-Builds
Crashed on start with lutris and proton builds of wine.
CPU: i5-7500 CPU @ 3.40GHz
Video i915 integrated Intel HD Graphics 630 (~20fps on minimal settings)
Set version to Windows 11 or use regedit on HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion and changing CurrentBuild and CurrentBuildNumber values? to 2090
?d3d_extras_version: v2?
dxvk_version: v2.2?
vkd3d_version: v2.9?
Realtime priority required for smooth playing.
My user script, run it after game starts:
#!/bin/sh
PID=`pgrep Diablo`
if [ "$PID" ]; then
sudo chrt --rr --pid 99 $PID
fi
by kolAflash on Sunday June 11th 2023, 17:53
github.com/HansKristian-Work/vkd3d-proton/releases
Installing VKD3D-Proton via current winetricks version 20230212-next is broken!
winetricks 20230212-next misses to install d3d12core.dll beside d3d12.dll. d3d12core.dll was newly introduced in VKD3D-Proton version 2.9. And without VKD3D-Proton 2.9 will give you a "unimplemented function d3d12core.dll.D3D12GetInterface" error.
P.S.
Runs fine on Debian-12 with the three workarounds applied: Windows Build 18363, DXVK, VKD3D-Proton
Alternative to get rid of the outdated drivers message: In Battle.net launcher set launch parameter "-bypassgpudrivercheck" for Diablo IV.
by GarMr on Tuesday July 4th 2023, 13:25
Any thoughts would be appreciated.
by RealDark on Friday March 24th 2023, 15:43