I've been having a couple of troubles playing Diablo IV, though they seem to be a lot worse with the new expansion. After a while of playing for a while, the game seems to leak VRAM and makes my desktop pretty unstable. Alt+tabbing occasionally breaks the game, the image freezes but I still hear the noises of the menus opening and such. If I don't alt-tab the game doesn't break.
I have found this reddit thread about setting a dxvk file to limit the amount of VRAM available to Diablo. I set up the max VRAM to 8gib but mangohud still reports 10gb being used. I tried setting the DXVK_CONFIG_FILE flag but that also doesn't seem to work. Mangohud report 10gb VRAM very fast. DXVK file contents:
dxgi.maxDeviceMemory=8192
dxgi.maxSharedMemory=8192
Decreasing the graphic settings just slows down the problem, it doesn't prevent it.
Launch options: DXVK_CONFIG_FILE=/gamedrive/dxvk.conf mangohud %command%
Specs:
Intel i7-12700K @ 4.900GHz
NVIDIA GeForce RTX 3080 (driver version: 560.35.03)
64GB DDR4
EndeavourOS Linux
6.11.3-zen1-1-zen
Hyprland
GE-Proton9-16
Diablo IV is a DirectX 12 game. Those don't use DXVK directly, though I think they might still use the DXGI component that comes with it, even though vkd3d-proton is providing the Direct3D 12 support.
DXVK_CONFIG_FILE is not a flag, but an environment variable. It is for overriding the location where dxvk.conf is expected to be. By default, that file is expected to be in the game's current working directory when it starts, so you don't need this environment variable at all if you figure out what directory that is. It's sometimes the directory where the game executable lives, but not always. (Hint: look for a dxvk or vkd3d log file.) Details here.
Note that one person in that reddit thread says dxvk.conf can be in "any folder of the wine prefix". As far as I know, that's just plain wrong. It has to be where DXVK is expecting to find it.
If you can't figure out where to put the config file, you might try applying those dxgi settings using an environment variable instead. In Steam, the game launch options would be:
DXVK_CONFIG="dxgi.maxDeviceMemory = 8192; dxgi.maxSharedMemory = 8192" %command%Here's a different possible workaround, to be put in Steam's game launch options:
PROTON_HIDE_NVIDIA_GPU=1 %command%Or if using Lutris with a Proton Wine runner, you would add an environment variable to the game (or launcher) profile, with key:
PROTON_HIDE_NVIDIA_GPUand value:1.If none of those workarounds help, you'll want to get involved in these discussions:
https://github.com/HansKristian-Work/vkd3d-proton/issues/1588
https://github.com/ValveSoftware/Proton/issues/7199
Edit: Several people have reported that this VRAM bug doesn't happen on AMD cards. If you happen to have one, you might give it a try.
I have tried the
PROTON_HIDE_NVIDIA_GPU=1before and I can tell you it definitely helps. The game is unplayable without it, to be honest. The VRAM still fills up but it's not instantly, it takes quite a while. Makes the problem manageable.Unfortunately I do not. I bought this nvidia card long before I switched to Linux and boy, do I regret it.
I edited my comment again around the same time you were replying. You might want to take a look to see if anything I added helps.