Unknown
VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%
Vertex explosions and missing/flickering textures (like a mostly invisible Chatacabra in the tutorial)
Pop-ins and low framerate
Crashes and freezes
I came back after a month after quitting at the end of the Chatacabra fight because of heavy visual glitches. These problems did not occur again the second time, but mainly because after several attempts I could not manage to leave the base camp without the game freezing or crashing.
PROTON_HIDE_NVIDIA_GPU=1 PROTON_ENABLE_NVAPI=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%
Crackling at this point is the game warning me to restart before it crashes. Hasn't happened quite yet w/ the driver update.
Vertex explosions occasionally happen, and sometimes the lighting gets blindingly white. Doesn't seem to be affected by settings.
Frame drops used to be very common, especially in higher activity areas. Now after the update, so far I haven't experienced any huge performance issues outside of stuttering while I'm in between transition areas.
Prior to updating my graphics driver, every time I would complete a hunt I would have to force restart my entire game before the game would crash and lock up my computer. Not so much a problem at the moment, I was able to complete two hunts in succession without any performance hiccups. Hopefully it'll stay that way.
If you have similar hardware to mine, I genuinely wouldn't recommend picking up the game despite the graphics driver update fixing the frequent crashes and frame drops for me. It still looks pretty ugly, and Capcom shouldn't be given any money for this mess until they fix it. I'm only pressing on because I am a fan of the series and I'm able to look past the ugliness now that I can finally play the game (also I am way beyond the refund period), but this shouldn't be anybody's first Monster Hunter game, especially if they can't run it.
The game is fun. Being able to play it on Linux/GNU is amazing for gaming in general! This installment of MHW includes a lot of QOLs
PROTON_HIDE_NVIDIA_GPU=1 PROTON_ENABLE_NVAPI=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 WINEDLLOVERRIDES="dinput8.dll=n,b" gamemoderun %command%
Added reframework (nightly release, https://github.com/praydog/REFramework-nightly/releases); extract dinput8.dll in to your MHW game folder (example: SteamLibrary/steamapps/common/MonsterHunterWilds/). This will effectively remove Capcom's own DRM and improve overall performance (NOT to be mistaken for removing Denuvo which is different).
IMPORTANT NOTE: GE-Proton10-10 is a must have to see MAJOR/significant performance improvements!!! Use ProtonUp-Qt to easily download and install the latest version of Proton.
I'm getting around 40 FPS with almost the lowest settings and DLSS enabled. For a fast paced game like this it's not generally recommended.
gamemoderun %command%
In the Windward Plains at Area 13 there's some textures that just "explode all around the screen. It's perfectly playable but annoying and disrupts immersion.
Lots of stuttering during gameplay. Even after Steam has compiled Vulkan shaders (which take ~30 minutes) and the game has compiled shaders once it has booted up.
Low FPS. I guess my hardware is old, but it can still run Monster Hunter: World over 60 FPS at good graphical settings.
If your hardware is somewhat similar to mine, the game won't run at 60FPS 1080p no matter what you do. Not on Windows not on Linux. Upgrade your hardware if it's impossible for you to play below that and really want to play this game. Or play Monster Hunter: World if you want to try a modern Monster Hunter game out before pulling the trigger on a hardware upgrade.
gamemodrun %command%
Occassionally in the Windward Plains, I get some visual issues looking at the desert. Like polygons trying to render themselves and stretch like a corruption.
Somewhat stuttery to start off with. Vulkan shaders took forever to process. Can only play on like medium settings.
gamemoderun %command%
After Title Update 2 the was stuck in a crash loop for a long. The steam version and launch options made no difference. After researching, I found that Denuvo can crash due to split lock mitigation. I disabled that kernel flag and now the game runs fine.
Flawless if not for a quick harmless visual glitch on a cinematic
Better FPS than Windows but need to load shaders everytime.
After TU2 game started to look pixelated in Win11 so decided to try Bazzite. Amd GPU and linux sometimes surprise me. Game looks better and I gained 8-12 fps with same settings. Have to load shaders each time I want to play though. So 5 min wait is the price for better graphics.
Heavy vertex explosions
Game Randomly like to stutter, sometimes a reboot fixes this
I have tried Proton Experimental, Stable, Bleeding Edge, GE, EM, and even CahcyOS, Ive tried every launch option with hiding my Nvidia GPU, Forcing in FSR 3.1 with Optiscaler, and countless other options. No matter what i still get large Vertex explosions that leave the game "Playable" but unfun
Getting well over 15%+ fps compared to w11
LD_PRELOAD=""
VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2
PROTON_ENABLE_NVAPI=1
__GL_SHADER_DISK_CACHE_PATH=/home/diva/.cache/games/mh-wilds/
__GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1
WINEDLLOVERRIDES="dinput8.dll=n,b"
gamescope --mangoapp --prefer-vk-device 1002:15bf -W 1920 -H 1200 -w 1920 -h 1200 -r 165 -f -S auto --adaptive-sync -- gamemoderun prime-run %command%
I used the config file for performance that i found on nexusmods as a base then i edited the in game settings for quality.
Game crash when alt tabbing. Fixed by using gamescope
If i had epilepsy i would not have survived the random screen flashing while fighting seregios.
I used __GL_SHADER_DISK_CACHE_PATH=/home/diva/.cache/games/mh-wilds/ __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 to make the game create shaders in that location , now i dont have to compile shaders each time i change an in game setting. game used to create shaders each time i launch it which takes +40 min . after using this command it compiled for the first and second time slowly , now it takes only 10 seconds to compile shaders.
The game will run perfectly the first time you compile shaders. Every time you launch after that the game will stutter nearly constantly, and will crash 100% of the time if you try to change or forge equipment, if you even manage to load in to the lobby without crashing.
I cannot in good concious recommend this game currently be played on Linux, at least not with an Nvidia GPU. You'll lose some performance due to the compatibility layer's overhead, you'll also have to recompile the shaders every single time the game launches if you want the game to actually work. It's not enjoyable and forces you to launch 30 minutes before you plan to play.
Does not work on Intel BMG GPUs
gamemoderun %command%
The game doesn't finish shader compilation due to a Runtime Error (Expression: "!status && "vkCreateGraphicsPipe"") on Intel Mesa BMG and LNL GPUs.
Currently under investigation as https://gitlab.freedesktop.org/mesa/mesa/-/issues/13011 and https://github.com/HansKristian-Work/vkd3d-proton/issues/2439
Besides the frametime inconsistencies which for me make the game feel choppier, it's been completely playable on my system.
VKD3D_CONFIG=no_upload_hvv WAYLANDDRV_PRIMARY_MONITOR=DP-2 PROTON_ENABLE_WAYLAND=1 game-performance %command% /WineDetectionEnabled:False /HID/UseISteamInput:False -USEALLAVAILABLECORES
Textures have a weird sharpening flicker when using in-game FSR upscaling with FSR frame gen.
Controller will not be recognized if you use native wayland driver. Set /HID/UseISteamInput:False after %command% to get controller detection when running native wayland driver
Framerate is inconsistent on my system, making the game feel a little bit choppy. Could be just the performance issues of the game but I don't remember this stuttering when I ran the game on Windows 11.
VRR flickering. Could be related to dynamic workload profile switching on RDNA2: https://gitlab.freedesktop.org/drm/amd/-/issues/1500#note_2947513 . Using LACT to set static GPU Core Clocks and using manual performance control with the 3D_FULL_SCREEN profile didn't help with this so it could be a problem with Sway due to that the desktop flickers when I exit the game and the monitor OSD displays 48hz. I can't confirms this at the moment.
####PLEASE READ#### VKD3D=CONFIG=no_upload_hvv to disable resizableBAR has been unique in my case. This fixed my stuttering on Elden Ring too. I would tell people to try and compare it vs on to see if it helps with stuttering. Wilds has been really rough on PC for a lot of users, but on my side it has been a breeze to run, specially on Windows 11 before I switched to Linux. On Linux, it has been hard to get the game to run how I like and I still have not accomplished it because it feels choppy to my eyes. This game would also run on my system without any thinkering with compatibility mode using Proton Experimental, tho I recommend using latest Proton-GE. I am using REFramework and the game just loads the mod without any launch options, the installation is basically the same as in Windows. I am also running ReShade with custom addon support and I installed it through protontricks. make sure to use /WineDetectionEnabled:False or else the game will detect that is running through WINE and ray-tracing will be disabled, and also ReShade will have problems hooking addons (credits to BUSTheid for mentioning the solution to this and also controller detection for native wayland driver).
Could not move the screen to the second display.
For me, building the shaders before launching a game is essential; otherwise, the game won't even start. That said, apart from this one step, the game runs perfectly, just like it does on Windows 11.
Games works great, as well as on windows. Maybe with a bit less stutter but I'm not sure if it's a TU2 improvement or if it really runs a bit better on Linux. The games still lacks optimization, especially with textures, but that's another problem. Mods seem to work great too. I've installed the updated direct storage mod, reshade and a few other stuff and everything works.
PROTON_HIDE_NVIDIA_GPU=1 PROTON_ENABLE_NVAPI=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%
After TU2, I did have to remove GameMode from my launch setting options and reframework.
FSR4_UPGRADE=1 WINEDLLOVERRIDES="dinput8.dll=n,b" mangohud %command%
The wine dll override is for mods.
After the June 30th Title Update 2 (TU2), I had to remove 'gamemoderun' from my Steam launch options in order to regain stability.
PROTON_HIDE_NVIDIA_GPU=1 PROTON_ENABLE_NVAPI=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%
MANDATORY: The game stops crashing/artifacting after downloading the latest GE Proton (easily managed using ProtonUp-Qt). And leaving out 'GameMode' from launch options.
You need the hardware to tank the performance and tweak it to hell and beyond - it won't be pleasant/functional almost at all OOB
DXIL_SPIRV_CONFIG=wmma_rdna3_workaround PROTON_FSR4_UPGRADE=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 game-performance %command% /WineDetectionEnabled:False /HID/UseISteamInput:False
installed REFramework for gray bar removal on 21:9
If used with Gamescope, the game hung my whole system's audio hard. Otherwise works fine on Wayland.
HDR might be worse than Windows surprisingly, but installing the RenoDX HDR Tonemapping mod fixes lots of issues. That being said, you do need the /WineDetectionEnabled:False argument since Capcom had the brilliant idea to deliberately disable Raytracing and somehow interfere with Reshade addons hooking into the game if it detects Wine.
/HID/UseISteamInput:False argument is the only way to detect controller if you want to play on Wayland and not Gamescope.
This is not a Linux problem, the game is still unoptimized after TU2.
No crashes, just the game running like jank even though my build is very solid. Not a Linux issue.
Unacceptable release and lack of care for PC users from Capcom's side. It's not Linux causing most of the issues, it's the game itself.
(TU2) Runs as good (or as bad) as in Windows, even feels slightly smoother. The initial shader compilation does take notably longer, though.
__GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 game-performance %command%
Able to run the game without much tinkering using CachyOS, but was completely unable to do so using Bazzie due to system freezes, just FYI.
Can't recommend playing on linux since TU2.
Random Crashes
Since TU2 AMD FSR doesn't work with a lot of flickering. Also the game crashes every few minutes randomly. Maybe try with Proton Hotfix or version 10 instead. It won't work well with Proton 9.
TLDR: After Title Update 2, if you get the network R31A6-0-0:3 error try switching to Proton Experimental.
A lot of people on reddit say to try and disable Crossplay solves the issue, but if you're on PC and disable crossplay there's absolutely no one to play with because you're forced to play with people who also disabled crossplay in their options. I found one thread and the guy said to change proton. I was on CachyOS-Proton, I was able to join a lobby, see all the players and interact with them but could not create or join multiplayer quests. Switching to proton experimental made it work. No need to disable crossplay!
Make sure you switch proton version if you have network error code.
mangohud gamemoderun %command%
Wilds naturally runs kinda like sh*t. This is not any one persons hardware. You're able to play this game perfectly fine, minus the natural issues, without tinkering, but using custom Proton makes this game run so much better.
Despite tinkering for a while, I can't get the game to run stable enough for it to be enjoyable due to crashes and graphical bugs after TU2.
gamemoderun %command%
- A Seikret somehow carried an infinite black polygonal ray on its head
- A Doshaguma sometimes left artifacts of its full silhouette during motion as if it was Naruto multicloning
- The character face appeared to melt once
This was during 1 hour of game time after the Title Update 2.
- Significant stuttering once the camera is turned
- Equipping a Bow somehow worsens the stuttering effect. Reducing graphical settings and textures does not appear to help
- Texture warping during game and cutscenes, requiring game restarts
- Crash during Lagia cutscene
I will eagerly read the hopefully better solutions that others will find. My comment's aim is to document something that works poorly currently on setups like mine.
mangohud %command%
No issues so far
gamemoderun %command%
semi-frequent stutter, seemed to be resolved due to Feral's Game Mode, and setting higher IO priority. Seemingly gone after TU2
Not since TU2
The launch state of this game, especially on Nvidia and Linux, was frankly unacceptable. I think after TU2 with the true upgrade to DLSS4 and their improvements to vram usage and texture streaming, it's fine. If you were waiting until now, that was wise of you.
在此之前，dlss3几乎不能用，会出现明显的伪影，并且会偶尔出现卡顿。在只开DLSS的情况下，游戏在我的机器上只有40+fps。但在更新后，开启DLSS帧生成运行正常，并且在启用dlss2x或fsr3后，游戏能达到70-100+fps，并且不再有卡顿。游戏体验已经接近在Windows上的状态。
gamemoderun %command%
Needed to use GE-Proton10-4 to solve graphical suttering.
Crashes when processing the shaders, unable to proceed in the game's main menu when able.
Attempted changing some .dll that caused known issues when launching the game with Linux.
Unfortunately, the game has been unplayable with my HW/Os even after multiple hours of tinkering and trying different options suggested by the community, as of TU1. The shaders attempt to recompile on each attempt, meaning 20-40 minutes wasted for each session. On the not-so-likely scenario that the shader compilation finishes (90% of the time there is a system freeze at the end, forcing me to do a hard reset to recover it), there is a crash after loading my character.
Runs just like under Windows even with Frame Generation enabled. Former vision bugs are fixed.
It's still an incredibly demanding game to an unfair degree.
The benchmark and the release version of the game were abysmal on my 6600XT, but since upgrading my computer and the game receiving some performance updates, everything is fine now. Today, as of writing (06/27/2025), Capcom released a patch for FSR 4 upscaling in MH:Wilds. I did not see an option above FSR 3 in-game, I am guessing because AMD hasn't added support for FSR 4 on their Linux driver for RDNA 4 yet or wine needs to be wine-git, I don't really know and can't be arsed to figure it out. I'm sure it'll work completely in a month or two. I wasn't able to successfully install Optiscaler, still not sure why.
VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%
light flickering, vertex explosions
occasionally freezes and stops responding during cutscenes
lots of tinkering to get mods working as well as getting hdr and steam input to work at the same time. as well as other things
gamemoderun WINEDLLOVERRIDES="dinput8.dll=n,b" PROTON_ENABLE_HDR=1 VKD3D_CONFIG=dxr,hdr RADV_PERFTEST=nggc mangohud --dlsym gamescope -W 3840 -H 2160 -f --hdr-enabled -- %command%
replaced alot of dll files and alot of mods mainly featured towards prefromance (uncomprssed texture mod with the dlc caused game to show a black screen on boot)
there was one cutscnene where one peice of cloth was moving a bit weird
mostly run fine, i ultatmetly decied on 4k fsr qauilty which gets me 50-70 fps but i choose to use framegen and cap the real fps to 60 so i max out my monitor at 120hz
if you want hdr (gamescope) and steam input at the same time you need to launch the steam client with the -steamos3 flag which adds some annoying behavior on start up. also if your looking for more prefromance disabling the steam runtime and using native libaires can imporve preformance alot espicaly on systems like gentoo
mangohud %command%
Borderless fullscreen didn't work on first boot, issue fixed itself later.
Increased VRAM usage, may cause stuttering when playing on higher resolution monitors.
You may or may not find some extra stutteting on first boot and on 8GBs GPUs. Vertex explosions seem fine now, no need to hide your nvidia gpu anymore.
Should work fine with decent hardware, otherwise requires a lot of optimization tinkering.
mangohud WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_MODE=ultra-quality WINEDLLOVERRIDES=dxgi=n,b DRI_PRIME=0 RADV_PERFTEST=ngg,rapm,radv_rt=1,sam,cache_compressor,wave32,dualcu VKD3D_CONFIG=dxr11,dxr,no_upload_hvv mesa_glthread=true AMD_DEBUG=zerovram,nodma RADV_VIDEO_DECODE=0 PROTON_ENABLE_NVAPI=0 %command%
If you don't have the hardware I have, I recommend getting an external config.ini optimized specifically for performance, should also work if you use some upscaling if you don't want the game to look bad.
Also requires WINEDLLOVERRIDES=dxgi=n,b if you want to use OptiFG.
It could be my imagination, but the game feels smoother on linux. I tested the fps and it's about the same, no big difference. But on linux it feels way smoother.
