UnsupportedShow Details
Unknown
Periodic stuttering but most likely due to caching. Performance in towns can be rough.
Game runs well enough for my specs but I still receive periodic stuttering. Use GE-Proton10-4 and NOT Proton Cachy OS Proton since having crossplay enabled will prevent you from even creating or joining rooms.
It runs but graphics and performance is worse than Win11. Needed a lot of work to get HDR and controller to work at the same time.
WINEDLLOVERRIDES="dxgi.dll,dstorage.dll,dstoragecore.dll,dinput8.dll=n,b" game-performance gamescope -w 3440 -h 1440 -W 3440 -H 1440 -bf --hdr-enabled -- %command%
Works but requires work
`PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 game-performance %command%`
or
`game-performance gamescope -w 2560 -h 1440 -W 2560 -H 1440 -bf --hdr-enabled -- %command%`
mouse is too fast when using gamescope option
Cannot play online with crossplay enabled, have to disable
You can use the first launch command to play if you have KDE on Wayland for HDR support, but you will lose controller and steam overlay functionality. Alternatively you can use the gamescope command for HDR, but my mouse did not respect system sensitivity so it was overly fast; additionally the compositor captures my mouse which I didn't want.
Anteriormente el juego daba unos tirones exagerados. Del palo que se quedaba congelado por más de un segundo, ahora. Aunque he probado el preset en bajo en ved de alto aunque la gpu no era el problema. El juego no se traba absolutamente nada, no hubo ningun glich grafico y todo fue super fino. La verdad experiencia 10/10
Igualmente a mí me fue bien pero a usted puede que no y por si no lo sabía este juego tiene pantalla de compilación. Le consumira un buen cacho del tiempo de juego en compilar (Me tardó 20 minutos con mi HW)
mangohud VKD3D_CONFIG=dxr11,dxr PROTON_ENABLE_NVAPI=1 PROTON_ENABLE_NGX_UPDATER=1 WINEDLLOVERRIDES="dstorage.dll,dstoragecore.dll,dinput8.dll=n,b" %command%
As of writing there is still one area in the Windward Plains that has a vertex explosion. Unforunately this is also where the game begins when you start a new save.
There is an issue with stuttering, which is solved by decompressing the game's textures. Doing so takes an additional 17GB of storage space, or 38GB if you don't delete the original compressed textures.
https://www.nexusmods.com/monsterhunterwilds/mods/951
Download the .exe and place it in the MHWilds install directory
- Launch the .exe with Wine
- Paste the file name:
re_chunk_000.pak.sub_000.pak
- Paste the file name:
- then press Enter > Down once > Enter > Enter
- ( In other words True > True )
Wait for the file to decompress
- Rename ( .pak > .backup ) or Delete (frees 21GB) the original re_chunk_000.pak.sub_000.pak
- Rename re_chunk_000.pak.sub_000.uncompressed.pak >
re_chunk_000.pak.sub_000.pak
- Rename re_chunk_000.pak.sub_000.uncompressed.pak >
You can do the same thing with the High-Res Texture pack by the way, which comes out to a whopping 106GB when uncompressed 😅
WINEDLLOVERRIDES="dinput8.dll,dstorage,dstoragecore=n,b" VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%
There is a spot in the first map where triangles stretch everywhere.
Game Freeze often at the start.
O desempenho foi uma otima experiencia, tive alguns congelamentos de segundos em momentos bem especificos, melhor que windows
Linux Wins
mangohud WINEDLLOVERRIDES="dstorage.dll,dstoragecore.dll,dinput8.dll=n,b" %command%
Génération d'images activé je suis à envirions 100 FPS
VKD3D_CONFIG=dxr11,dxr PROTON_ENABLE_NVAPI=1 PROTON_ENABLE_NGX_UPDATER=1 DXVK_NVAPI_DRS_SETTINGS=NGX_DLSS_SR_OVERRIDE=on,NGX_DLSS_RR_OVERRIDE=on,NGX_DLSS_FG_OVERRIDE=on,NGX_DLSS_SR_OVERRIDE_RENDER_PRESET_SELECTION=render_preset_latest,NGX_DLSS_RR_OVERRIDE_RENDER_PRESET_SELECTION=render_preset_latest WINEDLLOVERRIDES="dinput8=n,b" %command%
Minor artifacting only in the Windward plains
There used to be massive issues with Nvidia graphics cards on MH wilds, where you needed to make your graphics card show as generic to get the game to run properly without artifacts. But testing today proton experimental + mh wilds updates have made the game quite stable now. No more vertex explosions that I've encountered. DLSS4 also works like a dream!
Game runs great out of the box but is heavily improved by tinkering and choosing the correct graphics options.
VKD3D_CONFIG=dxr11,dxr PROTON_ENABLE_NVAPI=1 PROTON_ENABLE_NGX_UPDATER=1 game-performance dlss-swapper-dll %command%
On first launch, game would not fullscreen. Every launch after the game fullscreens perfectly fine.
Game was stuttering and UI was bugged and ghosting with Frame Gen enabled ONLY when using the High Res Texture Pack DLC. Using the normal High graphics setting stopped UI ghosting and stutter.
Would recommend not using the High Res Texture Pack. Even with a 5080, performance was awful until I returned to the vanilla High setting. Once I did, UI ghosting introduced from Frame Generation and a constant stutter disappeared completely, and the game runs better than it did with similar settings on my old Windows 11 install.
Performance on par with Windows 10 - texture compression characteristic of Wilds
Didn't play for long this time around. Last time I tried was a month ago, which ended terribly. Crashed in the middle of a fight following tons of consistent lag. This time, in the plains, fought two mons during a sandstorm with almost no noticeable lag. Recent updates did the trick?
mangohud %command%
On some rare occaisions the game just freeze without any way to fix this other then close the game and reopane it but it's seemes they fix this in the last update and the proton hotfix
the game do run out of the box but I switched to Hotfix version of proton only because the launch bugs
Change config.ini parameters to:
ParallelBuildProcessorCount=<vcore number>
RenderWorkerThreadPriorityAboveNormal=Enable
I got better performance compared to windows + optiscaler... <3 linux
gamemoderun %command%
Works without any issues, played a few hunts. PS5 controllers works like a charm, no delays on input. Gameplay wise it's playable, graphics wise it's the typical slowdown and stuttering similar to Windows 11.
- Isolated vector explosions; primairly on character faces.
- Some stuttering; likely a tandem issue with other systems (nvidia + wayland + gnome 43.9).
Initial launch did not expand the window to fullscreen by default. Additional launches successfully had the window at fullscreen (windowed) successfully.
Some slowness in menus after Vulkan compilation and game optimization.
After 2 months, I decided to try again.
WARNING: This is not a stable debian system
- Backports enabled
- Updated nvidia driver from 535 >> 570, and switched from X11 >> Wayland
gamemoderun WINEDLLOVERRIDES="dstorage.dll,dstoragecore.dll,dinput8.dll=n,b"
The launch options are not doing much tbh, i don't feel a difference with or without gamemode or the directstorage.dll's, the other one is just for the REFramework and mods.
in-game settings:
- you will get stutters when HDR is enabled in-game but not in OS.
- when using HDR you should turn Bloom to "Low". On "High" i would get stutters
- with the High Texture Pack installed, still use only "High". They will still look much better than before and "Highest" gives really bad performance/stutters)
PROTON_HIDE_NVIDIA_GPU=1 PROTON_ENABLE_NVAPI=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 VKD3D_CONFIG=no_upload_hv,force_host_cached __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%
ParallelBuildProcessorCount=16 RenderWorkerThreadPriorityAboveNormal=Enable
After pulling my hair out trying different versions of Proton and launch options all resulting in terrible stuttering and vector explosions (I mean waiting for those shaders for 30 mins to see if the most recent tinker worked... made me absolutely homicidal), switched to Experimental (not bleeding edge just the main experimental option which I think is 10.0) and made the change to the ini and since then no issues; played 4 hours with zero problems, no explosions, no stuttering... nada.
Will report back if anything changes!
Vertex explosions galore, so bad that the game was unplayable.
Was very stuttery the first time launching and extremely bad after some initial tinker attempts, now no issues after final changes.
If I wasn't already a big fan of the mhw franchise I would have thrown in the towel on day 1. Its really a scandal that they would release a game optimized this terribly. My current fix works great so far--no performance issues at all now (knocking on all the wood) but we'll see how long that lasts 😬
mangohud %command%
I gotta say, i was playing on win11, and with this same hardware, now im getting around 10-20 more fps and more smooth than it was before... and im not even running the latest kernel ... im happy with this .. really happy !
Downgrade GPU driver (Mesa 25.1.0 to 25.0.5)
I purged kisak-mesa fresh PPA (kisak/kisak-mesa) which provided Mesa 25.1.0 and added kisak-mesa stable PPA (kisak/turtle) which provided Mesa 25.0.5.
DXVK_CONFIG="dxgi.hideAmdGpu=True;dxgi.customVendorId=10de" DXVK_NVAPI_GPU_ARCH=GA100 PROTON_HIDE_NVIDIA_GPU=1 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 game-performance %command%
Minor vertex explosion in certain area on the Plain map.
100% enjoyable.
Borked with Mesa 25.1.0
- Several versions of Proton (Hotfix, Experimental, 9.0-4, 8.0-5, 7.0-6)
- Kernel upgrade (6.14.4 to 6.14.6)
The game used to be playable with Mesa 25.0.4. After upgrading Mesa 25.1.0, it is however borked. I should try to downgrade Mesa.
Has a bit longer than normal shader compliation and some more shader stutters for for first few mins of playing but smooths out after that.
gamemoderun %command%
Using gamemoderun helps improve fps drops when doing asset loading things like moving the camera quickly.
The game worked perfectly! I had one bug, but I also had it on windows where some of the icons might be mixed up or off. If you experience that, just delete the config.ini file in your game installation folder.
gamemoderun %command%
Regular flickering of the lighting, not that distracting to me
Controller temporarily loses connection for a few seconds every now and then
Crashed also for Windows users, not proton related I believe
Unable to start with Intel ARC due to Mesa issues
gamemoderun %command%
Game crashes on shader compilation with "!status && "vkCreateGraphicsPipelines" as seen in https://gitlab.freedesktop.org/mesa/mesa/-/issues/13011
If you look past the occasional vertex explosion and enable frame generation the game runs fine.
PROTON_HIDE_NVIDIA_GPU=1 PROTON_ENABLE_NVAPI=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command% -USEALLAVAILABLECORES
Change config.ini parameters to:
ParallelBuildProcessorCount=16
RenderWorkerThreadPriorityAboveNormal=Enable
Vertex explosions tend to happen in the desert area
- The game doesn't go above 50FPS without frame generation on low settings.
- The shader compilation doesn't use all my cpu cores so it takes a long time.
The game crashed once when starting up after what I assume to be a problem with shader compilation.
PROTON_HIDE_NVIDIA_GPU=1 PROTON_ENABLE_NVAPI=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%
fps dropdown starting the game
you need to run it with these commands that I found on a Steam forum for my graphics card, is necesary if you have verical lines coming from your character, and you can find a config file optimized in nexus mods for this game this 2 thigs are necesary, and runs great litle fps dropdown at the first minute on the start menu but I mean its fine in game runs with no issues
gamemoderun %command%
When terrain becomes transparent due to the camera being inside it, the transparency effect often doesn't render properly, causing a mostly black mass of flickering pixels across part of the semi-transparent terrain. Not gamebreaking, but noticeable.
Some regions tank FPS occasionally. I am quite certain that this is an issue with shader caching. Resolves itself after a short time, reappears every now and then.
Maybe two or three crashes in about 40 hours of play.
gamemoderun WINEDLLOVERRIDES="dstorage,dstoragecore=n,b" %command%
I updated the DirectStorage DLLs to version 1.2.4 (by downloading them from https://www.nuget.org/packages/Microsoft.Direct3D.DirectStorage and placing them in the game dir); without that, the game won't even launch.
I got the game running at 50-60 FPS on the highest settings, with FSR set to quality, no frame generation, and QHD resolution (although it could be running better, and I won't mention the game's optimization). Shader compilation takes a lot of time. I didn't experience any bugs or crashes throughout the entire playthrough. Multiplayer works without any problems. I played the game for 50h via shared library on steam.
PROTON_HIDE_NVIDIA_GPU=1 PROTON_ENABLE_NVAPI=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 VKD3D_CONFIG=no_upload_hv,force_host_cached __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%
Originally was launching from another disk, changed the install location to the default for the linux boot drive. Worked perfectly with the tweaks. Even better than on my windows OS.
Haven't tried tinkering with it yet, but as of default installation, can't enjoy the game
Default install and play runs a lot worse than in Windows. Stuttery and with artifacts on a 5090.
gamemoderun %command%
Compiling shaders and optimizing the game will take time, a lot of time.
gamescope -f -W 2560 -H 1600 -r 165 --backend wayland -- %command%
Modified the DLL for direct storage
The game would start then minimize and fail to do anything else or show on the display without gamescope
Without the launch commands above and replacing the DLL like the other comments mentioned -together- this game would not boot. The only optional command in it for me was gamemode. Adjust the gamescope resolution to your machine of course but if your game minimizes or freezes or launches for 2 seconds and stops like mine did try the above
PROTON_HIDE_NVIDIA_GPU=1 PROTON_ENABLE_NVAPI=1 VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 WINEDLLOVERRIDES="dinput8.dll=n,b" gamemoderun mangohud %command%
Upgrading my GPU driver to the latest version and using Proton Hotfix fixed the issues I had.
The game runs smoothly on my hardware on custom (medium-low) settings.
Additionally, I use the following mods but haven't tried to measure the perfs impact:
