UnknownUnknown
Consistently crashes after the first hunt after a few minutes.
The beta didn't get my hopes up. Might need to refund this if it still crashes my DE on launch day.
gamemoderun %command%
black screen unless fsr is disabled, menus still usable
game reliably crashes after nearly an hour
game regularly crashes
20-30 fps
His works but poorly optimized and PS1 graphics running in 20-30 fps in low configs :p
The game (Public Beta State) is broken currently.
AMD_VULKAN_ICD=RADV PROTON_NO_FSYNC=1 vblank_mode=0 gamemoderun %command%
the game stays on black screen, it renders nothing. even switching Windowed and Borderless Window doesn't help at all.
PROTON_HIDE_NVIDIA_GPU=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.x86_64.json gamemoderun %command%
Set EVERYTHING to the lowest setting possible or OFF. I had to deal with laggy fps, low-poly monsters and frequent crashing. These issues seemed to have stopped after changing the settings, fps and resolution to the ugliest and lowest before restarting. I had fun, but I'd rather wait until they properly optimize the game for PC, so like half a year or more after release.
For the most part, the game can be played like in any other platform. Just a small bit of tinkering required but it is playable.
gamemoderun %command%
The game shows only the UI with a black screen when I open it. I have to turn off AMD FSR 3 or set it to "Native AA" for it to render the game properly.
Even though it can be played, the game is still very poorly optimized. Had to play it in the lowest graphical settings.
The game crashes while in a lobby and hunting a monster. If too many things are happening all at once, the game crashes (and in my experience, it happened twice at the same spot on the map); but it only happens with more people in a party. Didn't have any problems in singleplayer hunts.
game consistently crashes after a few minutes
games always crashes after a few minutes
games always crashes after a few minutes, except during the initial cutscene and first gameplay phase
runs very well but after a few minutes, the games crashes my WM (hyprland), and i'm sent back to my display manager greater. when i reconnect to my user i have no sound.
Open beta is a crash fest. Hope this gets fixed before release.
some flickering artifacts on right side of the screen
frequent GPU crashes taking down the entire desktop
game only shows a black screen if FSR is on
THIS REPORT IS FROM THE 2024 OPEN BETA AND MAY NOT REFLECT THE STATE OF THE GAME AT RELEASE
Active FSR = BLACK SCREEN BUG -> Set e.g. "AMD FSR 3"-Modus: "AMD Native AA"
Not 100% with my card, wont get above 90 fps
Crash, then it was impossible to run the game again. I found that deleting crash.exe and crash.dll worked once, but my games crash again and this technique isn't working anymore.
Artifacting is still insane
Performance is the same as on Windows (Aweful) but with artifacting, missing textures and if you use upscaling there is flickering of textures as well
The game crashes usually before any meaningfull progress can be made and saved.
Fullscreen is not an option only borderless window at native resolution
Frequently freezes after 20 - 30 minutes
Blackscreen while upscaling is active; defaults back to upscaling sometimes.
Wait for full release, the Beta doesnt work.
It seems to be completely playable, but the visuals are terrible and it's hard to understand the environment you're in.
VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 gamemoderun %command%
Many textures are extremely slow to load, if they load at all. Much of the time it appears that chunks of the world are just missing or misshapen leading to the player often "walking on air" or walking through what appears to be solid environmental features. Certain places also have a number of small, white spots appearing regularly around the screen that I'm assuming are part of a graphical element that didn't fully load.
The sliders for determining contrast and brightness would not work with a controller or keyboard, only by using the mouse. Some menu button inputs seemed to only work with a controller button and not with the keyboard (I don't think I tried clicking on those).
Mostly seemed to play okay (from a purely functionial standpoint) though it did feel like it was struggling a little more than it ought to.
This literally would not make it past the splash screens until I added "VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2" to the launch options. With all versions of Proton I tried and all other launch options I found here, the game would crash after the splash screens. The game also takes a considerably long time to pre-compile shaders (I believe 30min-1hour), which made testing various Proton versions extemely tedious.
I tested with Proton 9.0-3, Proton Experimental, and GEProton9-18. It didn't even make it past compiling shaders on official Proton. I only found the effective launch options shown here after testing GEProton9-17, so I'm unsure at present if those launch options would enable it to work or work better in other Proton versions.
Blackout when FSR 3 is enabled except Native AA mode.
Crashes in High/ Ultra graphics settings especially during encounter with "Doshaguma Boss".
- I often experience the game freezing while pursuit of "Doshaguma Boss".
- The game (included Doshaguma Boss) runs fine provided that graphics setting is Medium .
After couple of minutes of playing the game will start to have very huge graphic artifact making it unplayable
gamemoderun %command%
Beta version, i am reporting this in hopes the proton devs/MHwilds devs will fix things
Very strange. Most time high profile runs better than medium/low/lowest.
For people using a AMD GPU, if you have gpu reset problem (freeze and the whole session crashes), try to lower your maximum GPU clock.
https://gitlab.freedesktop.org/drm/amd/-/issues/3131 https://wiki.gentoo.org/wiki/AMDGPU#Frequent_and_Sporadic_Crashes
Although this doesn't solve the performance problem, at least this game won't kill your whole session anymore.
PROTON_ENABLE_NVAPI=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%
During initial setup, controller buttons could not be used for left and right sliders of menu items
Missing textures, broken textures, unoptimised, crashes, game doesn't work without GE-9-18.
Missing ground textures. Flickering textures bouncing all over the place. Characters bodies stuck half-way underground.
Crashed early on past character creator.
unplayable given current performance shortcomings and the inability to adequately address them (particularly re: resolution options)
could not override built-in resolution or windowing values with Steam launch options or config editing (any changes made to config.ini were reverted on startup; launch options were always ignored).
~20fps in-game, regardless of settings.
froze once after intro cutscene; otherwise stable.
black screen if resolution scaling or frame gen is enabled.
apocalyptic fps.
First time trying out a Monster Hunter game. This game is too demanding for my PC, IMO. Looks and plays okey for a beta.
Crashes too often
AMD FSR creates black screen
amdgpu resets, same issue like Dragons Dogma 2
Beta Test
VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 PROTON_ENABLE_NGX_UPDATER=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 MANGOHUD=1 %command%
Upscaling/frame generation like FSR, DLSS or the intel one makes the game render everything as black. Proton experimental bleeding-edge fixed the issue for me.
Drivers constantly crashing (Mesa 23.x.x, 24.2.6) to greeter after 15-40 minutes of gameplay, Upgraded drivers to 24.2.6. Tried several proton versions (GE-16, GE-18, Proton Experimental, proton bleeding-edge) but the crashes continued.
The crashes made it so I couldn't beat Doshaguma before a system crash to greeter happened.
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=768173, emitted seq=768175
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process MonsterHunterWi pid 7080 thread vkd3d_queue pid 7148
If it wasn't for the crashes it would be 100% playable.
Noting this is a beta report, the game had great feel but a total lack of stability, leaving me unable to play despite hours of tinkering.
VKD3D_CONFIG=disable_uav_compression
The recommended Frame Generation setting would always have ghosting every time the camera angle changed on every object. I found it nauseating.
I finished one hunt in the 10 hours of the game I played. After tutorial I experienced crashes within minutes of leaving the hub area, if not in the hub area itself. I'm told there is a texture memory leak issue for AMD graphics cards in the beta.
I really don't know why I got my hopes up for a beta on this engine, but I still have hopes for the full release.
VKD3D_CONFIG=dxr mangohud MANGOHUD_CONFIG=time,vram,fps_limit=30,fps_limit_method=early,cpu_text=7700X,gpu_text=6650XT,wine,vulkan_driver,position=top-left,resolution,show_fps_limit %COMMAND% -fullscreen
Upscaling/Frame-gen causes a crash after awhile. Upscaling method needs to be disabled.
Runs flawlessly. Upscaling seems to have been added last minute and doesn't work as intended. The core game has zero issues, however. Got 30-45 fps with a 6650XT, which is better than Windows.
PROTON_FORCE_NVAPI=1 DXVK_ENABLE_NVAPI=1 VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json gamemoderun %command%
I tried default Proton, Proton Experimental, and GE-Proton9-16 previously and they all CTD'd when trying to launch. With GE-Proton9-18 the game launches and plays but with massive graphical artifacts everywhere. Without the launch options the game launches but has performance problems and HORRIFIC stutters making it even more unplayable. With the launch options the game stutters for a bit when loading an area or save but the stutters mostly go away and it runs... Okay, but with horrible graphical artifacts everywhere.
Its still a beta but the game needs serious optimization. Were talking about 70% better. Given the graphics, this should be achievable.
18-22 fps
When in the oasis where you choose your weapon, it crashes
Unoptimized, when in the oasis where you choose your weapon, it crashes
Windows users are complaining about the performance they are seeing in combination with the graphics. So capcom will probably work on this.
I love the open beta, but it's hard to recommend to anyone who isn't a massive fan of the series and is okay with dealing with crashes.
Game freezes somewhat often and requires a restart, so I needed to do both hunts a few times in order to succeed.
Frame Generation causes significant artifacts
Must disable upscaling for game to render. FSR3 with Native AA works.
Crashes somewhat frequently, even with lower graphical settings.
WINEDLLOVERRIDES="d3d12.dll,d3d12core.dll=n,b" MANGOHUD_CONFIG="gpu_temp,vram,position=top-right" mangohud %command%
Frequent geometry corruption, floating or "stuck" triangles, missing floor, walls, clothes, etc.
Low FPS at native resolution, frequent stutters
Matchmaking is opaque. Connection attempts and lobby/link joins will randomly fail with cryptic error messages. This is a technical beta however, so this much is expected
I have done extensive experiments trying to make this game run better, including setting arcane configuration variables in VKD3D, compiling libraries from scratch and lowering settings as much as possible. Despite this, I do not consider the game playable on my hardware in its current state in any of the configurations I have tested.
To much tinkering required to get the game into a state where its "playable but not great"
PROTON_FORCE_NVAPI=1 DXVK_ENABLE_NVAPI=1 gamemoderun %command%
At times textures didnt load properly, making monsters run around as a black blob while the texture flew through the air (happened only twice within 3 hours of play)
Sometimes dips into high 40s regardless of settings
Game crashes after a short time without Launch Options
Was able to connect to a friends lobby and played for an Hour
I don't think it's a Linux problem, it's a developer pushing a terribly optimised game in 2024 problem. Wait until the next beta.
Using FSR with Frame Generation basically makes this game so hideous as to be unplayabale.
Game runs terribly due to poor optimisation - albeit my CPU isn't great these days, it should not be performing this badly on a title like this.
If the game drops below 30 fps for whatever reason (like being in a settlement with Frame Generation off) then it'll crash your entire Wayland session.
Personally, I already love the beta and can't wait for the game to release. However, the beta is very buggy right now on linux.
The game freezes often. I had trouble beating the second monster because my game would freeze when it started limping away.
If you're like me and love Monster Hunter: World and/or Rise, then I would absolutely recommend giving the beta a try. Do keep in mind that you most likely WILL experience crashes and freezes, however I still managed to beat the entire beta despite this. If you aren't a fan of or haven't tried the Monster Hunter series, I would recommend waiting for the game to release and either playing a demo if they release one or wait for reviews/buy the game and play for less than two hours on steam so you can refund if you don't enjoy it.
If you optimize it to the fullest and don't mind bad graphics you can play the game. But if it is enjoyable highly depents on your standards
Difficult to read text, because of low forced resolution. Can be fixed with larger texts option ingame.
The game does not render with FSR enabled by default. This can be fixed if you force a 640x400 resolution in the game launch settings.
The game does not seem to support a fullscreen option in the settings
If you set the ingame graphics to the lowest. Force 640x400 resolution in the game launch settings and enable FSR3 ultra performance + frame generation you get about 30FPS in a hunt and about 20 to 30FPS in the hub.
Game crashes frequently sometimes, but sometimes also only once within an hour
Game DCs sometimes from the multiplayer, but never on quest only in hubs or the title screen.
Unoptimised - lower framerate than expected for the visual quality
FSR not supported
Didn't play for long
Needed bleeding edge proton (proton experimental betas branch) and to disable AMD FSR
AMD_VULKAN_ICD=RADV PROTON_NO_FSYNC=1 vblank_mode=0 gamemoderun %command%
Cutscenes bug out a bit at the bottom of the screen.
Had to set AMDFSR to AA. Other than some buggy cutscenes ( sometimes ), it ran pretty well.
There seems to be a problem with loading in textures and the right LOD model. In the worst case this can make the world disappear. Making sure textures are set to Medium seemed to at least make the game fully playable, even if that means you're fighting very low poly monsters on occasion.
gamemoderun %command%
Flickering
Laggy
Was unable to test, very laggy
Experimented with other commands, nothing seemed to remove the flicker
[Beta Report] Guaranteed crashing means I cannot continue playing as hunts can take longer than the time limit.
gamemoderun %command%
Average 40FPS but some quieter areas easily reached 60-80. Camp was filled with players which dropped me to 30-35FPS but I never experienced frame stuttering
Tried Proton Experimental, Experimental Bleeding Edge, GE and Hotfix but I was guaranteed to have a crash to my lightdm login prompt after approximately 30-40 minutes of gameplay as other users have experienced, this is regardless of Proton version. I am still investigating the cause since this is the first time I have ever experienced crashing to lightdm, I also had to hard reboot once.
Had no issues joining people and lobbies beyond navigating slightly confusing menus. High player volume led to frame reduction but that happens in other games too (e.g FFXIV) so it is not entirely the fault of MH Wilds.
Crashes are frequent
Performance is bad for everyone on the beta
Upscaling causes everything to be black except the UI
