UnknownUnknown
PROTON_LOG_DIR=${HOME}/Documents/proton/ PROTON_LOG=1 VKD3D_CONFIG=disable_uav_compression %command%
Frequent crashes untill i swapped to proton experimental and enabled the bleeding edge beta driver. That got me a 3½ hour game
I hope for better proton/wine drivers with the full release
VKD3D_DEBUG=none %command%
Crashes after 1-2 hours
Use proton hotfix and the launch options above. Game may crash after 1-2 hours. Big improvement to Proton GE with crashes after 15 minutes.
Happy hunting
gamemoderun %command%
Game had some heavy artifacts under Proton Experimental, and the menu scene froze for aa second on startup then recovered. The menu freeze was fixed when using Proton GE and major articafts disappeared.
gamemoderun VKD3D_CONFIG=disable_uav_compression VKD3D_DEBUG=none PROTON_LOG=1 %command%
I had to force experimental bleeding edge and this time I was able to play for 2-3 hours straight with no issues. I also turned off steam overlay, that might have helped as well
At least until the frequent crashing of the amdgpu driver is fixed, this isn't really playable
- Some terrain in the beginning section did not load it's higher resolution textures when getting closer
- In 21:9 mode there are constantly flickering white artifacts close to the right side of the screen
- HDR in gamescope looked pretty washed out even with some manual changes and cranked up contrast
- Using any kind of upscaling or frame generation (DLSS, FSR, XeSS) results in a black screen with only the UI being rendered
Shader Compilation Stutter
The game crashes randomly in a pretty catastrophic manner: It freezes and the audio keeps playing, then after a while the screen flickers, kwin freezes and crashes repeatedly and after a couple of minutes recovers.
dmesg shows that the amdgpu driver crashes, halting and resetting the GPU and clearing vram, which leads (for some reason) to repeated crashes and resets of the GPU in conjunction with kwin_wayland.
The message of the crash isn't very helpful:
amdgpu 0000:0d:00.0: amdgpu: Process information: process MonsterHunterWi pid 51360 thread vkd3d_queue pid 51605
amdgpu 0000:0d:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=6340127, emitted seq=6340129
I have not yet tested if these crashes happen in X11 or with a different wayland compositor.
Right now the only hope is that the beta could help fixing these issues (either in the game, proton or mesa/amdgpu) before the games release in a couple of weeks.
I can now play the game decently, after some experimenting. Before that, game crashed, there was stutter, some texture artifacts, etc...
VKD3D_CONFIG=disable_uav_compression gamemoderun %command%
Thanks to the people in the steam community that documented the VKD3D_CONFIG fix (the gamemoderun fix is just to prevent ubuntu from going to sleep mode when using a controlled).
gamemoderun PROTON_LOG=1 %command%
I tried multiple versions of proton and the game eventually always crashes, sometimes right away sometimes after 20 minutes. The video freezes with the audio still going but eventually KWin Manager resets killing the game and Steam
whenever i launch the game after a crash the game starts with fsr active which means i can only see menus
Even on Nobara, a distro aimed at being plug and play for linux gaming it still required a decent amount of troubleshooting to get running.
mangohud %command%
Stuttering in lobbies, significantly more cpu utilization than expected as well. ~60-70% when framerate was uncapped in crowded lobby. Tested in solo lobby as well with a 90 fps cap and it was around 40-50%
I cannot play for more than 10-20 minutes without crashing hard enough that it logs me out of my linux profile. Then it won't let me log in unless I purposely messup my password a couple times then try to log in, or if I restart my PC.
FSR is enabled by default and causes renders to just not appear at all. Menus and the HUD still display just no actual render or cutscenes. Must be disabled, then the game will actually render.
Due to the crashes I would not recommend playing this on Linux as of 2/7/2025. I cannot even complete a single quest without crashing.
Unfortunately, it's unplayable due to crashing and significant artifacting even within the weapon selection tutorial.
Significant artifacting present in the weapon selection camp, particularly when looking past the tent. Some missing textures.
Game would crash when trying to load videos in the weapon selection screen.
For some reason it is causing Firefox to slow down, crash, and otherwise misbehave when it is running during game launch. Problems appear to be avoided/reduced if closed and then reopened after MHWilds has launched.
It's just not currently in a playable state. Granted, only the beta access of the game is currently available.
gamescope --enable-hdr -h 2160 -f -e -- env DXVK_HDR=1 %command%
The entire screen is black when using any upscaler besides NativeAA.
Crashes HARD. It will sometimes cause amdgpu to freeze making my entire desktop frozen and unable to switch to another TTY, making it necessary to manually reset my PC. The benchmark seems to work fine, but the actual beta is incrediably unstable.
fsr
Frequent crashes
Textures are a hot mess
Game looks bad was able to get 50 - 60 FPS. Doesn't seem worse than Windows for similar hardware.
FSR makes everything but menus a black screen. Once disabled everything works. Also, only on this game my 6700XT GPU regularly throws a ring gfx_0.0.0 timeout and causes a GPU reset.
It seems like many people with AMD GPUS are having issues. I personally receive a GPU reset every 30 - 60 minutes. I've tried several amdgpu module options(runpm, gpu_recovery, and ppfeaturemask), mesa-git, and maxing out fans. I can't seem to avoid the GPU reseting. I was able to get enough up time to hunt all the monsters except Rey Dau (too long couldn't finish without a crash). Longest uptime achieved with "amdgpu.ppfeaturemask=0xffffbfff". Several threads on which features to enable/disable just tested this one (appears to be DS_FCLK).
xess&fsr can't open,it make black screen
fps18~30
Game launches, loads menu with black background, once you load a save the interface works but everything that's rendered is just black. Not playable.
Simply doesn't launch.
Black screen for 5 seconds, and then it does a crash report.
GPU driver crashes frequently once in the actual game (past character editor and after cutscenes at the start)
FSR 3 seems to cause the game background to be blank when enabled (it's on by default, and keeps turning itself back on after reopening the game), did not try going in-game with it enabled yet though
Grey window followed by crash report window.
Doesn't work. I tried using wined3d, forcing a specific D3D version (it seems D3D11 is required), but everything either results in the game not starting at all (disabling D3D11), showing a dialogue about unsupported hardware (forcing wined3d), or the grey window and the crash report.
Occasional crashes, but that seems to happen to many folks on reddit/r/monsterhunter anyways, so I guess not Linux related.
AMD FSR3 did not work, had to disable upscale
I'm amazed, it just works.
gamemoderun %command%
FSR3 does not work resulting in menu on a black screen. Disabling it solves the issue.
Had one big crash which killed the Gnome shell too.
mangohud %command%
Crashing occured when I would open my save for some reason. Did not start on the first time opening from save, only after the second or third.
Without frame gen (and when it would open my save) it would drop to 30-50 fps in a populated lobby and stutter graphically.
First crash sent me to lock screen which never actually unlocked. Rebooted and then it crashed again and gave me a black screen with a "watchdog: watchdog0 did not stop!" warning before rebooting.
When I first started the beta it must not have been able to truly go online, that portion worked flawlessly and my fps was ~80-90. Once I got in a full lobby it dropped to 30-40, had some weird animation stutter and ultimately crashed (and potentially corrupted the save?)
Game is impossible to progress with crashes within 2-3 minutes of starting tutorial mission.
Disable display scaling to solve black screen for rendered graphics.
Have not been able to complete the tutorial mission due to crashes.
All rendered scenes are black with overlays working while display scaling is turned on. Game runs fine with setting turned off.
VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%
terrain disappearing and large flat artifacted geometry
very low framerate
Disable DLSS (on by default) to fix light flickering
