DZPlayer
Published
VKD3D_CONFIG=disable_uav_compression MESA_DISK_CACHE_SINGLE_FILE=0 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 gamemoderun %command%
Make sure that when you add to the start up commands and switch into Proton Experimental (bleeding-edge) that you give Steam a restart.
VKD3D_CONFIG=disable_uav_compression MESA_DISK_CACHE_SINGLE_FILE=0 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 gamemoderun %command%
If you are having issues getting the game to start, either it disappearing or freezing the PC, open the config.ini (./steamapps/common/MonsterHunterWilds/config.ini) and adjust the renderer capability to DirectX11 instead of the default DirectX12.
Changing this setting will let you compile shaders and play the game, but will revert to the default immediately when the game runs. I recommend letting this happen just to get in-game to start adjusting settings there. Once you are pleased with the game's performance/visual quality, open the config file again and change the renderer capability back to DX11. Save the file and make it read-only to prevent the game from reverting it again.
If using multiple monitors, the game will occasionally pull the arrow back into its bounds while unfocused.
The game does NOT have an in-game setting to select a different renderer. This has to be applied to the config manually and made read-only to stick.
VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 gamemoderun %command%
Prior to the first title update, the config file needed to refer to DirectX11 for the game to run. This no longer appears to be the case and can be returned to the default of DirectX12. However, the title update appears to have updated the dstorage.dll and dstoragecore.dll files and is causing other issues. Reverting the files to their 1.2.2 versions appears to solve these issues.
For a guide to assist in downgrading those .dll files: https://www.youtube.com/watch?v=Rx622NWG298 For access to the older versions of the .dll files: https://www.nuget.org/packages/Microsoft.Direct3D.DirectStorage/1.2.2
After performing these steps, delete the shader.cache, vkd3d-proton.cache, and vkd3d-proton.cache.write files and apply the launch options along with Proton Experimental's Bleeding Edge beta.
The game should now function again after recompiling shaders.
