Proton
Proton copied to clipboard
Monster Hunter Rise (1446780)
Compatibility Report
- Name of the game with compatibility issues: Monster Hunter Rise
- Steam AppID of the game: 1446780
System Information
- GPU: RX 580
- Driver/LLVM version: 4.6 (Compatibility Profile) Mesa 21.3.3
- Kernel version: 5.16.0-arch1-1
- Link to full system information report as Gist: https://gist.github.com/dorni1234/417c810ec1e7434a1c62d5ce3c5ebe9a
- Proton version: 6.3-8, Experimental
I confirm:
- [X] that I haven't found an existing compatibility report for this game.
- [X] that I have checked whether there are updates for my system available.
Symptoms
Game starts up, crashes on "compiling shaders" on the first screen of the game.
Reproduction
Start the game.
Install vulkan-radeon, delete amdvlk and try again.
Install
vulkan-radeon, deleteamdvlkand try again.
Thank you very much, this did indeed fix the issue.
Shall I close this issue now, or leave it open in case any other compatibility problems occur for other people?
Leave it open i guess, wouldn't hurt.
Sad that how AMDVLK is prompted as first option on Arch leads to a bad experience for most users.
Glad it helped.
Monster hunter rise stutter when loading and it freezes too form time to time.
Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/8346. @blastermaster77 posted on 2022-01-15T05:14:56:
Your system information
Computer Information:
Manufacturer: Gigabyte Technology Co., Ltd.
Model: X570 GAMING X
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 7 3700X 8-Core Processor
CPU Family: 0x17
CPU Model: 0x71
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 4426 Mhz
16 logical processors
8 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
"Manjaro Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 5.15.12-1-MANJARO
X Server Vendor: The X.Org Foundation
X Server Release: 12101002
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20211207.0
Video Card:
Driver: NVIDIA Corporation NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 495.44
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 164 Hz
VendorID: 0x10de
DeviceID: 0x1c03
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 2560 x 1440
Desktop Resolution: 2560 x 1440
Primary Display Size: 24.41" x 14.57" (28.43" diag)
62.0cm x 37.0cm (72.2cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 6144 MB
Supported MSAA Modes: 2x 4x 8x 16x
Sound card:
Audio device: Nvidia GPU 84 HDMI/DP
Memory:
RAM: 32088 MB
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 960028 MB
Largest Free Hard Disk Block: 146440 MB
- Opted into Steam client beta?: [Yes]
- Have you checked for system updates?: [Yes]
Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
Steps for reproducing this issue:
- Launch Monster hunter rise with proton-experimental
- When it loads ti stutters real bad and then it stabilizes 3.The game freezes from time to time during quests. 4 see video attached with the problem.
https://user-images.githubusercontent.com/9307070/149609929-9fc3d289-4ae3-47da-8053-1b5723d80473.mov
Hi,
The game seems to always update one component upon launch:
Seems like some graphical libraries are being replaced, which also prompt to shader recompile - when this happens then I get this error:
If I retry multiple times I get lucky and then the game is smooth as butter.
I'm using Proton 6.3-8 on Ubuntu 20.04 on a 3080 Ti (nVidia drivers 495.46).
I did not see that D3D error window yet on my computer(RX 5700 XT) but the shader recompilation on every launching followed by its usual stuttering is here too.
I'm also getting the stutter on load mentioned a few posts up (the post with the video). Stutters fairly badly when first loading into town, then for a few seconds when entering a stage, as shown in the video. Stabilizes for the most part shortly after, but there will be an occasional stutter (~1 sec) during gameplay as well.
- AMD Ryzen 5 3400G
- NVIDIA GTX 1650 SUPER (470.86)
- 16GB RAM
- Pop OS 21.10
It may be irrelevant but a quick test led to a proton log with a large number of warnings like
warn:d3d12_pipeline_state_init_graphics: Ignoring stencilTestEnable due to lack of stencil aspect
More than 5000 lines like this and all I did was loading the game, walking a little in the village and closing it.
System Information
-
GPU: GTX 2080ti
-
Driver/LLVM version: nvidia 495.46
-
Kernel version: 5.16.0-arch1-1
-
Proton version: 6.3.8-5
Opted into Steam client beta?: [No] Have you checked for system updates?: [Yes]
Attaching the PROTON_LOG, although the issue is not with the game startup. steam-1446780.zip
Here is a more detailed log which also captures the time period where the error occurs. steam-1446780-extra.zip
Symptoms
I have difficulties with multiplayer. I can join hunts in progress, and others can join mine, but if I attempt to depart on a hunt from the gathering hub with others, I disconnect with a "Communication Error" and enter the hunt separately from other players.
Reproduction
Launch Monster hunter rise with proton (but have tried also with proton-experimental and proton-ge)
Join a lobby with friends (this works)
Start a new hunt, wait for everyone to ready up, then launch hunt.
One of the players gets a communication error. Both players enter the hunt, but in separate instances.
Brief update, the "Fatal D3D Error" is fairly common on Windows too, nothing special about Proton/wine seems like... Perhaps some dodgy CAPCOM code?
@blastermaster77 As a workaround to the stuttering, I've been deleting the steam shader cache for the game (in steamapps/shadercache/1446780) and shader.cache2 file from the game folder before starting the game. The game seems to be happier if it rebuilds its own cache each time.
I experience the loading screen stuttering as well, and have been wondering if that is somehow related to the multiplayer communication errors I'm seeing (if the game fails to communicate during those stutters, is that what causes the disconnect?).
I haven't yet tried deleting the shader caches manually yet, but I do know that proton and proton-experimental crash for me during the game intro (before reaching the main menu) if shader precaching is disabled in Steam settings.
I also get that crash when turning off precaching. And to clarify, it's not just loading screens that are stuttering for me. It seems that every shader that was compiled on the last run causes a massive stutter on the next run when it is used again.
@Keelhauled Hm, that seems to line up with my experience of the game recompiling its own cache every time I change runners and thus running great on that first boot, but then stuttering again on subsequent boots with the same runner. But I've seen a report on ProtonDB of someone getting a Denuvo lockout from changing runners too many times so that's not something I want to do too often.
EDIT: I tried just deleting shader.cache2 and that got rid of the stutters, so it doesn't seem that deleting Steam's cache is necessary. However, I've also noticed that on boots after shader.cache2 is deleted, while the game doesn't stutter, it does fade to a black screen for several seconds after a loading screen, essentially adding several seconds to load times. Without deleting shader.cache2, there's no black screen after loading screens, but the stuttering is present. So it seems like a choice between stuttering or longer loads.
The game plays perfectly fine, but I have experienced a strange graphical glitch at Lava Caverns. There are green and red glowing parts on walls in the caves where there are water falls. Has anybody else had this?
I just installed latest mesa-git (22.0.0) and this is how it looks like
:
Hello @TheChriZ, that looks like https://gitlab.freedesktop.org/mesa/mesa/-/issues/5620.
This bug does not occur with Proton-Experimental
I did some more testing with the help of a gracious friend. It seems like deleting the shader cache does somewhat fix the multiplayer connection issues I am encountering. It seems like if I attempt to load a map with a multiplayer session, it will succeed with no issues only if, during the load, I get the "Compiling Shaders" bar. Otherwise a communication error occurs. Deleting the shader cache meant that I was able to depart on a hunt with my friend, and it succeeded, but a communication error occured when returning back to the lobby (I assume this is because I already had computed shaders for the town and so did not need to again). This also explains why joining a lobby works, there is no map transition when joining a lobby.
I can only guess why this happens, my best totally uninformed theory is that there's some kind of handshake failing during the loading screen hitches, which doesn't fail if shaders need to be computed (maybe the game communicates an expected delay in that case? pure speculation).
Compatibility Report
- Name of the game with compatibility issues: Monster Hunter Rise
- Steam AppID of the game: 1446780
System Information
- GPU: Amd radeon rx 580 8GB
- Driver/LLVM version: 4.6 Mesa 20.3.5
- Kernel version: 5.10.0-10-amd64
- Proton version: 6.3-8 and experimental fail similarly.
Symptoms
Update After clearing shadercache, game runs correctly again. Leaving the error report as the error is still present (but probably unrelated).
Game worked since launch until today, where i get the following error and a Steam crash to desktop.
Unhandled Exception:
System.TypeLoadException: Could not load type of field 'InstallerMessage.Form1+<CodecCheck>d__11:<codecQuary>5__2' (3) due to: Could not load file or assembly 'Windows.Foundation.UniversalApiContract, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
at InstallerMessage.Form1..ctor () [0x0000c] in <a06ba4bb41904acfa9f23ab189e60bef>:0
at (wrapper remoting-invoke-with-check) InstallerMessage.Form1..ctor()
at InstallerMessage.Program.Main () [0x0000b] in <a06ba4bb41904acfa9f23ab189e60bef>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeLoadException: Could not load type of field 'InstallerMessage.Form1+<CodecCheck>d__11:<codecQuary>5__2' (3) due to: Could not load file or assembly 'Windows.Foundation.UniversalApiContract, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
at InstallerMessage.Form1..ctor () [0x0000c] in <a06ba4bb41904acfa9f23ab189e60bef>:0
at (wrapper remoting-invoke-with-check) InstallerMessage.Form1..ctor()
GameAction [AppID 1446780, ActionID 1] : LaunchApp changed task to RunningInstallScript with ""
GameAction [AppID 1446780, ActionID 1] : LaunchApp changed task to SynchronizingCloud with ""
GameAction [AppID 1446780, ActionID 1] : LaunchApp changed task to SynchronizingControllerConfig with ""
Opted-in Controller Mask for AppId 1446780: ffff
GameAction [AppID 1446780, ActionID 1] : LaunchApp changed task to ProcessingShaderCache with ""
Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice().
Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice().
Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice().
***** OUT OF MEMORY! attempted allocation size: 1698128704 ****
src/tier0/memstd.cpp (2838) : OUT OF MEMORY
src/tier0/memstd.cpp (2838) : OUT OF MEMORY
src/tier0/memstd.cpp (2838) : Fatal assert; application exiting
src/tier0/memstd.cpp (2838) : Fatal assert; application exiting
Installing breakpad exception handler for appid(steam)/version(1642451672)
assert_20220119202613_32.dmp[37423]: Uploading dump (out-of-process)
/tmp/dumps/assert_20220119202613_32.dmp
_ExitOnFatalAssert
Reproduction
Tried both steam stable and beta, both fail the same way. Tried both proton 6.3-8 and proton experimental, both fail the same way. Other games with proton 6.3-8 and proton experimental that ran before today run correctly.
Solution
In my case, the game worked again after removing the shader cache. The vulkan shader loading bar took less than normal and never went into the game but crashed steam instead, hopefully this helps others.
System Information
- GPU: AMD 6700xt
- Driver/LLVM version: Mesa 22.0.0-devel (git-f1f65e5bcf)
- Kernel version: 5.15.11
- Proton version: Experimental
Symptoms
Online play is not working properly: most of the time it will let you connect to another lobby once and play one hunt, after that the game will either crash or disconnect, either when returning to the lobby or when departing for another hunt. If it disconnects it won't be able to connect again (in game error or crash when joining). There is also an element of randomness on whether it lets you connect even one time, it seems like if you try it as soon as you get in game it mostly works fine, but otherwise if you try after playing a while even in single player it can fail the first time too.
Reproduction
Speak with the "Courier" npc (see attached picture), select play online->find a lobby and join a game. If it lets you, play one mission then come back to the lobby. If it doesn't disconnect you or crash, join another mission on the same lobby to trigger the issue. I tried 5 times and I got disconnected or crashed 100% of the time. If disconnection happens, trying to join another lobby will result in an error. I stopped testing because I didn't want to disturb other players

Unrelated to the issue, but experimental bleeding edge stopped working with one of the last updates, it crashes once it gets tho the health disclaimer on boot so I can't try that either (that used to work, not sure about the online because I never tried with bleeding edge. I haven't played in a week so I'm not sure when it broke). Below it's a log for the bleeding edge crash steam-1446780.log
In terms of the "Fatal D3D Error", seems like it may be caused by enabling MANGOHUD (v 0.6.5) - apparently enabling it cause this issue to happen ~50% of the times the game is started, I've disabled it and so far never experienced the error once - will post further updates if this is the case.
Edit - can confirm having MANGOHUD enabled triggers the "Fatal D3D Error", restarted the game multiple times without it and never got it - otherwise is quite frequent.
adding to my other message, today I played 2-3 hours with a build of proton-tkg based on wine-staging 95bf6698950d82622f7461111b3a199343ce9a21, didn't get disconnected even once
Is there a way to disable vulkan shader compilation just for monster hunter rise? I noticed that when I start a session on wayland the game compiles the shaders on its own and its smooth as butter, wen I go back to x11 and wayland for the second time the steam vulkan shader compilation appears and it gets stutter like the video i posted above. Its with nvidia drivers.
@blastermaster77 afaik there is no way to disable it per game
95bf6698950d82622f7461111b3a199343ce9a21
Could you please link to the proton version you used?
95bf6698950d82622f7461111b3a199343ce9a21
Could you please link to the proton version you used?
My comment was mostly directed at Valve devs, I don't know if it's ok to share unofficial builds here. You could compile it yourself with proton-tkg for now.
Compatibility Report
Name of the game with compatibility issues: Monster Hunter Rise
Steam AppID of the game: 1446780
System Information
GPU: GeForce RTX 2060 SUPER
Driver/LLVM version: Mesa 22.0.0-devel
Kernel version: 5.4.0-96
Proton version: Proton Experimental
Symptoms & Reproduction
I start the game with any Proton version, it crashes & gives me an error.
Greetings,
I run this game on Linux Lite & I get this error message. I updated everything & cannot find a solution. The other bug reports didnt work for me or maybe I did something wrong. Im relatively new to Linux & this is my first bug report, so yeah probably getting something wrong
Hello @Pr0gr4mm3rR4m, your log hints that something's unhealthy with the Vulkan render path on your system. Please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
As a side note, if you're primarily using the NVIDIA proprietary driver, then having a bleeding edge build of mesa will give you no benefit because those two drivers share no code.
I have just noticed the following dmesg output after launching Rise
umip: MonsterHunterRi[34229] ip:14f533690 sp:93f740: SGDT instruction cannot be used by applications.
umip: MonsterHunterRi[34229] ip:14f533690 sp:93f740: For now, expensive software emulation returns the result.
umip: MonsterHunterRi[34229] ip:160386cb2 sp:93d4c8: SGDT instruction cannot be used by applications.
umip: MonsterHunterRi[34229] ip:160386cb2 sp:93d4c8: For now, expensive software emulation returns the result.
umip: MonsterHunterRi[34229] ip:15e660f48 sp:93d0c8: SGDT instruction cannot be used by applications.
Is it something to be concerned from a performance point of view?