ShUl0w
Published
mangohud %command% --skip-launcher
Playing with DirectX works perfectly without any noticeable issues; I did not test Vulkan.
PROTON_HIDE_NVIDIA_GPU=1 VKD3D_CONFIG=force_bindless_tex_heap gamemoderun %command%
Currently, the game suffers a heavy VRAM leak, which will ultimately cause low FPS and full game crashes. In case you notice from white / foggy floor textures, your GPU is likely running out of VRAM.
Following Pathiefs instructions to create a dxvk.conf file located at /YOUR_STEAM_LIBRARY_DRIVE/SteamLibrary/steamapps/common/Diablo IV/ and setting the values about 2 GB lower than my GPUs VRAM fixed everything for me. For an 8GB VRAM GPU the values would be:
dxgi.maxDeviceMemory=6144
dxgi.maxSharedMemory=6144
Adjust accordingly for your respective VRAM.
In addition, make sure to use FSR, as DLSS seems to be borked right now.
Performance is slightly lower than on Windows
Without the applied fixes, the game will crash on a regular basis
PROTON_ENABLE_WAYLAND=1 mangohud %command%
Under Wayland, monitor detection seems borked, and may crash the game when moving the window (especially on startup) or changing ingame resolution. This can be fixed by setting the primary display via WAYLANDDRV_PRIMARY_MONITOR=YOUR_MONITOR_ID in the launch options.
Under Wayland and this specific GE-Proton version, I had to set Steam Input to "Use default settings", in addition to switching my leverless to PS4/PS5 mode before starting the game. In all other combinations (e.g. setting it to Xbox mode), my leverless would not be detected at all.
Wayland improves the experience regarding input lag massively. However, there are some extra steps you might want to take.
- If your distro supports it, enabling ntsync also helps to further stabilize the frame times - at least on my system. Under current Arch, this can be done with
sudo modprobe ntsync. - If you are running the game on a television that does not support native 60Hz and up (e.g. 59.95Hz), enabling VSync in the game settings will fix dropped inputs, although it will add a tiny bit of input lag (which is still noticeably less than when running under xwayland).
The controller detection took me quite some time to figure out and might be different for your specific controller, and may not work at all. This is the only game where I had such issues, so I believe this is more of a GGST issue than a Wayland/Proton issue.
gamemoderun mangohud %command%
Minor flickering on some distant textures
On my system, I wasn't able to install the Rockstar Launcher, as no buttons would register clicks. Switching to Proton 8.0-5 resolved this, and after installing the launcher I was able to switch back to Proton Experimental.
gamemoderun %command%
Played through the whole game without any issues.
gamemoderun %command%
DX11 performs worse than DX12, which runs as expected. Selecting the High Resolution Texture Pack causes massive FPS drops; no issues when setting textures to Full.
gamemoderun %command%
Performance in window mode is severly degraded; Fullscreen works without any issues
The game only works with GE-Proton8-32. I have tried several other Proton versions (Hotfix, Experimental, 9,8,7, various GE9 and GE8), which ultimately caused Denuvo to lock my install for 24 hours. Thus, make sure to not switch Proton versions too often, as each seems to count as individual install. With GE-Proton8-32 however, the game runs amazing. I had lots of issues with it on Windows, like performance drops and full crashes, but have yet to encounter any of these under Proton. Surround sound is hidden behind a setting in the games audio menu. Otherwise, I did not need any additional launch options besides gamemoderun.
gamemoderun %command%
Zero issues from the first start of the game, performance appears to be better than on Windows. Can't notice any degradation, even over long sessions.
PROTON_ENABLE_WAYLAND=1 mangohud %command%
Under Wayland, the game tends to crash when changing resolutions. This can be fixed by setting the primary display via WAYLANDDRV_PRIMARY_MONITOR=YOUR_MONITOR_ID in the launch options.
Under Wayland, it is necessary to disable Steam Input, as it is not supported. My leverless was recognized fine once I disabled this, whereas it wasn't recognized at all before.
Setting lightning & texture settings above "High" causes major performance degradation
The game suffers from noticeable input lag when running under xwayland. Thanks to GEProtons Wayland support, this has been completely fixed. However, there are some adjustments needed to get everything to run nicely.
- If you have issues with slowdowns during online matches, run
sudo sysctl kernel.split_lock_mitigate=0before starting up the game. - If your distro supports it, enabling ntsync also helps to further stabilize the frame times - at least on my system. Under current Arch, this can be done with
sudo modprobe ntsync. - If you are running the game on a television that does not support native 60Hz and up (e.g. 59.95Hz), enabling VSync in the game settings will fix dropped inputs, although it will add a tiny bit of input lag (which is still noticeably less than when running under xwayland).
Generally, you will want to enable Shader Warming on Startup and Input Delay Reduction regardless of your display server protocol. Note that the Steam overlay will not work under Wayland at the moment, so if you intend to use the ingame shop, you will have to start the game using xwayland.
To sum it up, I would argue that running under Wayland allows for competitive gameplay, while xwayland will only suffice for casual gameplay. For the latter, the game will run out of the box with any current Proton version, but setting kernel.split_lock_mitigate=0 might be needed regardless. Optionally, feral gamemode will do this for you aswell.
