Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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.
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.
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'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
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
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.
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 ?
I am running it on Nobara with these launch options added to Steam:
7900xtx (undervolted) / 7800x3d / 64gb / Proton Experimental [Bleeding Edge]
I also needed to change these lines in the config.ini to read like this:
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
It runs ok now with low settings on everything.
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.