Monster Hunter Wilds

Monster Hunter Wilds

View Stats:
How is it working on Linux?
How's it working for people on your Linux systems compared to Windows? (Not talking steam deck, like Ubuntu, wine, etc...)

Also, what specs are you using. What stand out settings, and what crashes/glitches of any.

Thanks in advance for sharing.
< >
Showing 1-15 of 15 comments
Not good. I'm running SteamHeadless on Unraid, the same setup that ran the Open Beta Test and the Benchmark tool. Before Sunday's patch, the full game would crash on boot regardless of launch options or proton versions. After the patch, the game now boots to a black screen and doesn't appear to be doing anything.

Other people appear to be running the game just fine with some tweaking. See ProtonDB for more reports: https://www.protondb.com/app/2246340

My specs are as follows, as noted by ProtonDB:
Distro: Debian GNU/Linux 12 (bookworm)
Kernel: 6.6.68-Unraid
RAM: 64 GB
GPU Driver: NVIDIA 570.86.16
GPU: NVIDIA RTX 2000 Ada Generation
CPU: 12th Gen Intel Core i5-1235U

Edit March 4, 2025:
Today's patch means I'm back to crashing on boot.
Trying to run on a Window's VM now, same hardware, streaming to another device where I want to play with a controller. I'm not sure this game is even stable enough to run this way.
Last edited by Jeff Le Guy; Mar 4 @ 12:41pm
Umino Mar 3 @ 3:14pm 
If the free benchmark tool is anything to go by, the game should run just fine on linux if your hardware is up to the task.

I ran the benchmark on my new main rig (Ryzen 7700 + RX 7700XT running Linux Mint Debian Edition) and I get around 70-80 fps on 1080p Ultra without Raytracing.

Just make sure you run the game from a fast SSD ... I had the benchmark installed on spinning rust at first and I could really see how it is loading in textures and extra polygons on the fly ... when I started the benchmark for the first time, it looked like some N64 game for 5 seconds - boxy faces and blurry textures and everything ... then the details started popping in one by one.

On the second run, that stuff was still in the filesystem cache or something because it did not look this weird.
I have an AMD R5 5600x, 16 GB RAM, with AMD RX 7900 XT running Arch Linux.

The game runs okay at 1440p native res with everything set to Ultra except for Shadows and Draw Distance (shadows and draw distance being set High).

FPS fluctuates between 40-60 in camps with lots of players. FPS is more solid 70-80 in the outdoor areas and fighting monsters.
It plays like ♥♥♥♥♥♥♥ on the lowest settings lol (I have 2560*1440p monitor)

It's manageable in the forest (30-40 ♥♥♥♥♥♥ FPS), but once I reached a water level (like the Jyuratodus mud area in World), my computer started to stutter a lot (powerpoint slide show FPS). I'm gonna have to power through the level I guess.

Proton: Proton Experimental [bleeding-edge]
Distro: Nobara 41
Kernel: 6.13.3-201.nobara.fc41.x86_64
RAM: 32 GB
GPU Driver: NVIDIA 570.124.04
GPU: RTX 3080
CPU: AMD Ryzen 7 3800X
Last edited by MonkeyOfWAR; Mar 3 @ 11:39pm
Dildozer Mar 3 @ 11:53pm 
It works well enough on my setup on Ubuntu 22.04 with rtx 3060 and 5800x. I use the launch options on proton db to disable nivida compatibility and the other command that people recommend and use fsr set to quality and no frame gen caped at 60fps at 1080p. The only issues I have is there is 1 rock in the desert area that causes weird artifacts when looking directly at it, and when I'm entering a new zone for the first time the game all but freezes then continues just fine (I think it's the shaders loading for the first time). Had crashes when trying to run it on high with no framegen and using frame gen at all causes it to crash or lock up after some time playing. I do have a windows drive I'm tempted to test but id rather just deal with the jank the game offer now then windows 11 in general.
NashDash Mar 3 @ 11:55pm 
Is it?
I give the performance on my system a solid meh. Runs 30-40 most places on roughly medium settings, which is playable, though turning things down doesn't really add more than 5 extra fps. Only major issue is occasional crashing that takes my DE down with it, screeching and crying all the way.

Proton: GE-Proton9-25
Distro: Pop_OS 22.04 LTS
Kernel: 6.9.3-76060903-generic
RAM: 32 GB
GPU: AMD Radeon rx 6650 xt
GPU Driver: Mesa 24.0.3
CPU: AMD® Ryzen 5 2600
Running fairly good on cachyos. I've had maybe 6 crashes in 33 hours of play. I have a fairly high end system but with an AMD GPU. I run it in proton experimental bleeding edge and a few launch commands I found on protondb.
mccloud Mar 4 @ 12:06am 
Works fine on my Mint 22.1.
5700X3D + RX 7800XT
Proton Experimental

No crashes whatsoever. If you turn on FSR, it crashes within an hour, at random times. Without it, no issues. Hearing all the trouble people have on the Windows side, even with AMD cards, yet here I am with no issues on Linux lol. I think the latest AMD Windows driver is broken, clearly the cards can run the game just fine.

That said, I am gonna try XeSS later today, maybe it works without crashing. Anything to get rid of that TAA blur. When FSR is working, before the inevitable crash, it looks good and sharp. Tried FSR just for antialiasing, AMD Native, but that comes with a ~5fps hit, so I turned that off.

Honestly, the only things I need more from the game are performance improvements (getting 50-60 fps on a 1440p with a 600€ GPU is a disgrace for what the game looks like, most people have way worse GPUs than me, poor souls) and some alternative to TAA - anything to reduce that blur. Other than that, technically the game is good.
Umino Mar 4 @ 5:01pm 
Originally posted by mccloud:
Honestly, the only things I need more from the game are performance improvements (getting 50-60 fps on a 1440p with a 600€ GPU is a disgrace for what the game looks like, most people have way worse GPUs than me, poor souls)

Well, AFAIK Monster Hunter Wilds is running on the RE engine ... is that correct?

If it is ... well ... think about it ... an engine created for survival horror games that primarily feature narrow hallways, buildings and underground facilities with many small rooms ... maybe a monster here or there ...

... and this same engine is now used to render vast outdoor areas with heaps of creatures going about their business ... what was capcom expecting how it would perform ?
Last edited by Umino; Mar 4 @ 5:01pm
Perfect. It took me tinkering. But the game runs on High settings with High Res textures at 140+ fps. (FSR AA Native + FG)

I am running it on Nobara with these launch options added to Steam:
unset LD_PRELOAD; RADV_DEBUG=synccompile RADV_PERFTEST=gpl MESA_VK_WSI_PRESENT_MODE=fifo RADV_FORCE_VRS=2 PROTON_ASYNC=1 VKD3D_CONFIG=no_upload_hvv gamemoderun VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%

7900xtx (undervolted) / 7800x3d / 64gb / Proton Experimental [Bleeding Edge]

I also needed to change these lines in the config.ini to read like this:
ParallelBuildProcessorCount=16
RenderWorkerThreadPriorityAboveNormal=Enable
Last edited by Bind0fGod; Mar 4 @ 5:23pm
JayKaye Mar 4 @ 5:11pm 
Better than windows, though that's not a high bar.
Runs ok until all the models explode and the game crashes

Operating System: Bazzite 41
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.5-102.bazzite.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 28 × Intel® Core™ i7-14700F
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4070
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D99
System Version: 3.0
Originally posted by MonkeyOfWAR:
It plays like ♥♥♥♥♥♥♥ on the lowest settings lol (I have 2560*1440p monitor)

It's manageable in the forest (30-40 ♥♥♥♥♥♥ FPS), but once I reached a water level (like the Jyuratodus mud area in World), my computer started to stutter a lot (powerpoint slide show FPS). I'm gonna have to power through the level I guess.

Proton: Proton Experimental [bleeding-edge]
Distro: Nobara 41
Kernel: 6.13.3-201.nobara.fc41.x86_64
RAM: 32 GB
GPU Driver: NVIDIA 570.124.04
GPU: RTX 3080
CPU: AMD Ryzen 7 3800X


It runs ok now with low settings on everything.
I'm running Bazzite 41, on a system with a 5900HX + 3070 w/32gb of RAM. After a lot of fiddling the game runs fine. I've updated and forced DLSS4 so the image quality is pretty good, mostly a mix of High and Highest settings, did some config tweaks too. Since the game has a hard time hitting and staying past 60, I locked it at 48 on a 144hz monitor and that looks fine enough to me. Using GE Proton 9-25.

Overall it's a good experience (I just finished the story/hit the credits), but in specific spots I get an issue with vertex explosions. There's a spot in the desert that does it, and a specific monster later in the game that does it too. I can play through it but nothing I've done seems to alleviate that problem. I'd assume a patch and/or an update for Proton will get that straight at some point. The game has crashed once or twice, but not regularly/not with any consistency.
< >
Showing 1-15 of 15 comments
Per page: 1530 50

Date Posted: Mar 3 @ 2:56pm
Posts: 15