Monster Hunter Rise (1446780)

[dorni1234]

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:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-1446780.log

Symptoms

Game starts up, crashes on "compiling shaders" on the first screen of the game.

Reproduction

Start the game.

[Leopard1907]

Install vulkan-radeon, delete amdvlk and try again.

[dorni1234]

Install vulkan-radeon, delete amdvlk and 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?

[Leopard1907]

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.

[kisak-valve]

Monster hunter rise stutter when loading and it freezes too form time to time.

Issue transferred from ValveSoftware/steam-for-linux#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:

1. Launch Monster hunter rise with proton-experimental
2. 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.

2022-01-15.00-30-10.mov

[Emanem]

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).

[wwmm]

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.

[SeraphisCain]

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

[wwmm]

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

steam-1446780.zip

More than 5000 lines like this and all I did was loading the game, walking a little in the village and closing it.

[jakepacheco]

System Information

• GPU: GTX 2080ti

• Driver/LLVM version: nvidia 495.46

• Kernel version: 5.16.0-arch1-1

• Full system information report

• 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.

[Emanem]

Brief update, the "Fatal D3D Error" is fairly common on Windows too, nothing special about Proton/wine seems like... Perhaps some dodgy CAPCOM code?

[Keelhauled]

@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.

[jakepacheco]

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.

[Keelhauled]

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.

[SeraphisCain]

@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.

[TheChriZ]

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?

[TheChriZ]

I just installed latest mesa-git (22.0.0) and this is how it looks like


:

[kisak-valve]

Hello @TheChriZ, that looks like https://gitlab.freedesktop.org/mesa/mesa/-/issues/5620.

[TheChriZ]

This bug does not occur with Proton-Experimental

[jakepacheco]

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).

[bakanando]

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.

[EmmerichFrog]

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

[Emanem]

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.

[EmmerichFrog]

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

[blastermaster77]

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.

[EmmerichFrog]

@blastermaster77 afaik there is no way to disable it per game

[ktzee]

95bf6698950d82622f7461111b3a199343ce9a21

Could you please link to the proton version you used?

[EmmerichFrog]

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.

[kisak-valve]

Hello @mattipulkkinen, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the misrender, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

[mattipulkkinen]

steam-1446780.log

I've attached the proton log, but it looks like the Steam Runtime Diagnostics is a no-go. Selecting Steam Runtime Diagnostics from the help menu opens the appropriate window as it should, but after a few seconds it causes my desktop session, or something, to crash so badly I need to hit the reset button. Otherwise all I can see is a black screen, and I can't even get into a virtual terminal. I tried it twice now with the same result.

Edit: looks like the Steam Runtime thing crashing with AMD cards is a known issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2384#note_1769931

[Kaedras]

I've also got some flickering that appears to be a regression in Proton experimental (switching to Proton 8.0-3 fixes it).

log: steam-1446780.log

runtime diagnostics
system information

screenshots:

[alasky17]

@Kaedras Could you see if this regression is fixed on the experimental bleeding-edge branch? We are hoping that this is the same regression impacting some other games, and the fix was just pushed live very recently :)

[Kaedras]

@alasky17 I've just tested it, and it seems like the issue has been fixed.

steam-1446780.log

[Blisto91]

@mattipulkkinen Thank you for the report.
This should now behave as native Windows on latest Proton Experimental. There will still be a flicker as that is just the game, but it should now not appear a lot worse with AMD + radv.

[NTrixner]

Hi!
I'm having a pretty big issue with Rise under Proton with my Manjaro. The game completely flickers black a few times every second.
Additionally, the resolution, window mode and display settings can't be changed - they immediately switch back to the original resolution (not shown in the video, since it would have taken too long to get to the menu)
The game's unplayable in this state, sadly.

PXL_20231004_195500851.TS.mp4

steam-1446780.log
runtimeDisagnostics.txt

[Jorgee1]

Compatibility Report

Name of the game with compatibility issues: Monster Hunter Rise

Steam AppID of the game: 1446780

System Information

• GPU: AMD Radeon RX 480
• Driver/LLVM version: Mesa 23.2.1-arch1.2 / vulkan-radeon 1:23.2.1-2 / LLVM 16.0.6
• Kernel version: Linux 6.5.7-arch1-1
• Proton version: Proton Experimental, Proton Hotfix, Proton 8.0-4, Proton 7.0-6, Proton 6.3-8

Link to full system information report (proton log and steam system information) error-logs.zip

I confirm:

• that I haven't found an existing compatibility report for this game.

• that I have checked whether there are updates for my system available.

Symptoms

I have the same problem mentioned by @NTrixner, here is a formal report.

The screen flickers whenever the game starts in full screen mode. I am unable to use the in-game settings to change resolution or switch to windowed mode. At around minute 1:52 I pressed Alt+enter to force the game out of full screen.
You can also change the resolution with the .ini file, but by pressing Alt+enter the changes are overwritten and goes back to a window with monitor resolution.

When the game is not flickering, the frame rate hovers at around 10 - 17 FPS. Back when the game first launched, it ran at +60 FPS.

Here is the video proof (seizure warning)

monster.hunter.flicker.compressed.webm

After some time the game crashes and the Capcom crash report tool tries to do something but fails with error code: 0x2000000

Already tried the following launch options without success:

• WINE_FULLSCREEN_FSR=1
• WINE_FULLSCREEN_FSR_STRENGTH=1
• WINEDLLOVERRIDES="dinput8.dll=n,b"
• WINEDLLOVERRIDES="dinput8.dll=b"
• RADV_PERFTEST=nosam

Also, when the game starts, steam throws the following exception. Not sure if this is normal, but haven't seen it in other games.

Oct 21 13:58:51 Zordon-PC steam.desktop[7132]: fsync: up and running.
Oct 21 13:58:51 Zordon-PC steam.desktop[7132]: wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Oct 21 13:58:53 Zordon-PC steam.desktop[7245]: Unhandled Exception:
Oct 21 13:58:53 Zordon-PC steam.desktop[7245]: 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=14.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
Oct 21 13:58:53 Zordon-PC steam.desktop[7245]:   at InstallerMessage.Form1..ctor () [0x00063] in <fce48153e782462bbf37770256af3859>:0
Oct 21 13:58:53 Zordon-PC steam.desktop[7245]:   at (wrapper remoting-invoke-with-check) InstallerMessage.Form1..ctor()
Oct 21 13:58:53 Zordon-PC steam.desktop[7245]:   at InstallerMessage.Program.Main () [0x0000b] in <fce48153e782462bbf37770256af3859>:0
Oct 21 13:58:53 Zordon-PC steam.desktop[7245]: [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=14.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
Oct 21 13:58:53 Zordon-PC steam.desktop[7245]:   at InstallerMessage.Form1..ctor () [0x00063] in <fce48153e782462bbf37770256af3859>:0
Oct 21 13:58:53 Zordon-PC steam.desktop[7245]:   at (wrapper remoting-invoke-with-check) InstallerMessage.Form1..ctor()
Oct 21 13:58:54 Zordon-PC steam.desktop[2632]: /bin/sh\0-c\0mangohud /home/kenshinn1/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=1446780 -- /home/kenshinn1/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/home/kenshinn1/Extra2/SteamLibrary/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/kenshinn1/Extra2/SteamLibrary/steamapps/common/Proton - Experimental'/proton waitforexitandrun  '/home/kenshinn1/Extra2/SteamLibrary/steamapps/common/MonsterHunterRise/MonsterHunterRise.exe'\0
Oct 21 13:58:54 Zordon-PC steam.desktop[7270]: ERROR: ld.so: object '/home/kenshinn1/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Oct 21 13:58:54 Zordon-PC steam.desktop[7270]: ERROR: ld.so: object '/home/kenshinn1/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Oct 21 13:58:54 Zordon-PC steam.desktop[7270]: ERROR: ld.so: object '/home/kenshinn1/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Oct 21 13:58:54 Zordon-PC steam.desktop[7270]: ERROR: ld.so: object '/home/kenshinn1/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
Oct 21 13:58:54 Zordon-PC steam.desktop[7270]: ERROR: ld.so: object '/usr/$LIB/mangohud/libMangoHud_opengl.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Oct 21 13:58:54 Zordon-PC steam.desktop[7271]: ERROR: ld.so: object '/home/kenshinn1/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Oct 21 13:58:54 Zordon-PC steam.desktop[7271]: ERROR: ld.so: object '/home/kenshinn1/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Oct 21 13:58:54 Zordon-PC steam.desktop[7272]: ERROR: ld.so: object '/home/kenshinn1/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Oct 21 13:58:55 Zordon-PC steam.desktop[7394]: fsync: up and running.
Oct 21 13:58:55 Zordon-PC steam.desktop[7394]: wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Oct 21 13:58:57 Zordon-PC steam.desktop[7392]: Setting breakpad minidump AppID = 1446780

Reproduction

Start the game in full screen mode, when is not in full screen mode it has very low FPS.

[kisak-valve]

Hello @Jorgee1, your system is configured to run the game with AMDVLK. Can you test how the game behaves with mesa/RADV?

[Jorgee1]

Good day
@kisak-valve,

I have both installed, but I have set the environmental variable AMD_VULKAN_ICD to RADV (https://wiki.archlinux.org/title/Vulkan).
It shouldn't be using AMDVLK.

As you can see on the following picture, RPCS3 describes the GPU with RADV. If i switch the variable to AMDVLK the description changes.

Also tried running the game with AMDVLK with the same result. Do you think this could caused by AMDVLK?

Regards

[Jorgee1]

Wow, thanks to your comment I managed to fix it.
It was AMDVLK, decided to uninstall it and that solved all my problems.

It seems that driver has issues with with Monster Hunter rise and the env variable doesn't switch the drivers.

[LunaRosalie]

Capcom updated the game today which completely broke steam deck support

[SeongGino]

Just going to corroborate this with a log since @LunaRosalie neglected to provide one: steam-1446780.log

Of particular note at the end of the file, possibly(?):

55308.256:012c:0130:trace:loaddll:build_module Loaded L"C:\\Program Files (x86)\\Steam\\gameoverlayrenderer64.dll" at 00000000034C0000: native
55308.256:012c:0130:fixme:steamclient:manual_convert_Set_SteamAPI_CCheckCallbackRegisteredInProcess_func_156 not implemented!
SteamInternal_SetMinidumpSteamID:  Caching Steam ID:  76561198090576201 [API loaded no]
55308.260:012c:0130:err:seh:NtRaiseException Unhandled exception code c0000409 flags 1 addr 0x1514421a8

[ThomasT75]

Just crashes without showing a window

GPU: RTX 2060 Super
Driver: nvidia-dkms 545.29.06-1
steam-1446780-proton-experimental.log
steam-1446780-proton-8_0_4.log

[irasponsible]

Having the same issue as the above two users, game ran fine yesterday, now won't launch.
Was on Proton 8-0-4, tried Experimental, 7, and GE_8-27 with no success.

Running Steam in the console and looking at the output, this is the only thing that looks like it could be a relevant error.

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=14.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
  at InstallerMessage.Form1..ctor () [0x00063] in <fce48153e782462bbf37770256af3859>:0 
  at (wrapper remoting-invoke-with-check) InstallerMessage.Form1..ctor()
  at InstallerMessage.Program.Main () [0x0000b] in <fce48153e782462bbf37770256af3859>: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=14.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
  at InstallerMessage.Form1..ctor () [0x00063] in <fce48153e782462bbf37770256af3859>:0 
  at (wrapper remoting-invoke-with-check) InstallerMessage.Form1..ctor()
/bin/sh\0-c\0/home/ikj/.steam/debian-installation/ubuntu12_32/reaper SteamLaunch AppId=1446780 -- /home/ikj/.steam/debian-installation/ubuntu12_32/steam-launch-wrapper -- '/home/ikj/.steam/debian-installation/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/ikj/.steam/debian-installation/compatibilitytools.d/GE-Proton8-27'/proton waitforexitandrun  '/home/ikj/Games/steam/steamapps/common/MonsterHunterRise/MonsterHunterRise.exe'\0
chdir "/home/ikj/Games/steam/steamapps/common/MonsterHunterRise"

I do note it says <codecQuary>, but I can only find reference in Microsoft's docs to <codecQuery>. Typo?

[cybik]

The reference to codecQuary is likely internal code.

The true issue may be

Could not load file or assembly 'Windows.Foundation.UniversalApiContract, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=null' or one of its dependencies.

A quick sleuth around the 'net seems to indicate this (possibly missing?) library is related to the Microsoft UWP toolkit.

[alasky17]

We pushed a new build to Proton Hotfix that fixes the crash on launch. It wasn't really a Proton bug, but we were able to work around it easily :)

[cybik]

Limited play, but confirmed. The game is functional again.

[ThomasT75]

Played some online and 1 hunt offline and it works

[irasponsible]

Working again, done a few hunts and working as it was before.

[Sanaki]

Since Capcom's patch, Proton 8.0-5 works fine again. With hotfix it takes me about three attempts starting the game for it to progress past the health warning screen on steam deck. With 8.0-5 it works every time. I recommend changing the default version back to 8.0-5.

[alasky17]

@Sanaki Thank you for the report. It turns out that there was an intermittent bug that we started hitting that has been around forever and probably causing other random crashes that we could never track down. Luckily the failure was consistent enough with MHR that we were able to figure out the root cause and fix it :D The fix is in current hotfix and bleeding-edge. If you see that crash again with a Proton version newer than current hotfix or bleeding-edge, please ping me as currently I'm working under the assumption that it has been fixed. Note - the fix is not in 8.0-5 or experimental-8.0-20240111.

[clankfish]

Crashing on launch with this error:

Wine C++ Runtime Library
Assertion failed!

Program: Z:\home\pez\.local\share\Steam\steamapps\common\MonsterHunterRise\MonsterHunterRise.exe
File: ../src-wine/dlls/winevulkan/loader_thunks.c
Line: 2934

Expression: !status && "vkCreateGraphicsPipelines""

Press OK to exit the program, or Cancel to start the Wine debugger

Sometimes I reach in game, go out on a quest and then the game crashes at the loading screen instead. Sometimes I reach "compiling shaders" which seems to hang forever. The log increases rapidly in size (8gb+!) so I can't upload those logs. This log is from crashing at launch:
steam-1446780.log

[kisak-valve]

Hello @clankfish, can you check if https://gitlab.freedesktop.org/drm/amd/-/issues/3343 is relevant to your system? A quick test would be to reboot into an older kernel and see how the game behaves.

[clankfish]

Hello @clankfish, can you check if https://gitlab.freedesktop.org/drm/amd/-/issues/3343 is relevant to your system? A quick test would be to reboot into an older kernel and see how the game behaves.

Hi @kisak-valve, enabling 4g decoding and resizeable bar in UEFI settings seems to have completely fixed this issue. Thank you very much! I was starting to worry that my new gpu was faulty or something lol phew :))

[NTrixner]

I (finally) got it to work too.

Just had to remove vulkan-amdgpu-pro, so it JUST uses vulkan-radeon.

[Eckoa]

as of recently i cant get MHR to work with Proton 8, 9, or Experimental as it just closes once it reaches the Health warning. Proton 8.0-5 just crashes at launch, 9.0-2 reaches health warning as does experimental.

It works fine with Proton GE 9-7 and worked fine with regular proton as of a few weeks ago at least which was when i got my new system and was trying the game out.

There doesnt appear to be much different in the proton logs between them, it just closes.

[Sanaki]

Crash at the health warning means the anticheat triggered. I'm afraid I can't tell you what would lead to that happening though. If you use mods, try updating REFramework.

[Eckoa]

Crash at the health warning means the anticheat triggered. I'm afraid I can't tell you what would lead to that happening though. If you use mods, try updating REFramework.

dont use mods, tried with and without RE framework. Really have no clue whats happening as it use to work fine with plain jane proton but there isnt anything in the logs to give me a direction as to whats going on with proton + the new DRM. I didnt play for a few weeks and now it just stopped working, I suppose at least GE works so i can play still.

EDIT: After i said this i tried a hail mary and remove DRI_PRIME option and that fixed it, apparently forcing a specific GPU caused it