When starting a new round of Bounty Hunt, MangoHud will report VRAM usage at ~4 GB.

As I traverse through the map, VRAM usage as reported by Mangohud steadily increases and does not appear to be released automatically.

Every few minutes, I can usually force some VRAM (usually 0.5 - 1.5 GB) to be released by toggling the in-game display mode (e.g. Fullscreen Windowed > Fullscreen > Fullscreen Windowed). The amount which seems to be released in this way tends to decrease as the game progresses.

Eventually, around 10-10.5 GB VRAM in use, I start to see stutters in-game which necessitate more frequent toggling of the display mode workaround described above.

If the game progresses too long or if I have traversed too much of the in-game map without toggling the display mode, VRAM in use eventually reaches 10.5 GB - 11 GB VRAM and the game may hang for anywhere between a few seconds to 1-2 minutes.

Inside Proton, the game does not appear to be able to estimate how much VRAM is actually in use, and changing the setting for VRAM available to Hunt does not seem to matter.

Software information

• Hunt: Showdown 1896 (SteamId 594650)
• 1440p or 1080p
• Most graphics settings to High

Launch commands:

VKD3D_CONFIG=log_memory_budget VKD3D_DEBUG=info VKD3D_LOG_FILE=".../vkd3d_hunt.log" gamemoderun %command%

System information

• Kernel: 6.16.4-arch1-1 (64-bit)
• Graphics Platform: Wayland
• Memory: 32 GiB of RAM (30.4 GiB usable)
• GPU: Intel(R) Arc(tm) B580 Graphics (BMG G21)
• Driver: Mesa 25.2.1-arch1.5
• Wine version: GE-Proton10-15
• VKD3D-Proton version: 2.14.1 (build: 334e778136f2c34)

sudo lspci -k | grep -EA3 'VGA|3D|Display'

VGA compatible controller: Intel Corporation Battlemage G21 [Arc B580]
Subsystem: ASRock Incorporation Device 6021
Kernel driver in use: xe
Kernel modules: xe

Log files

vkd3d_hunt_20250830_1440p.log

vkd3d_hunt_20250903_1440p.log

steam-594650.log