search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.58k stars 1.07k forks source link

Monster Hunter Rise (1446780) #5495

Open dorni1234 opened 2 years ago

dorni1234 commented 2 years ago

Compatibility Report

System Information

I confirm:

steam-1446780.log

Symptoms

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

Reproduction

Start the game.

wwmm commented 1 year ago

@Billli11 is there anything suspicious in the output of sudo journalctl -b | grep -i steam after the game crashes? Since the launch day I have seen random crashes in this game. When they happen usually relaunching the game 3 or 4 times in a row is enough to "make it work". It is almost like it has to invalidate some kind of bad data in the shader cache or something similar and repeated attempts to launch somehow make it fix itself for a while.

alasky17 commented 1 year ago

@Billli11 Wow, thank you for testing all those variables! Those were definitely the major suspects I had after looking at your dist output :D. I have a couple more suggestions in addition to @wwmm ... 1) Could you try adding "VKD3D_CONFIG=swapchain_legacy %command%" to the launch options? 2) If (1 doesn't fix the problem, we very conveniently have experimental-7.0-20221115 pinned as a branch right now. Could you verify that version still works and doesn't crash? 3) If that (2 is a yes, then could you try dropping the vkd3d-proton files from that build (or from 7.0-5) into experimental-7.0-20221129? I think the easiest way is to copy the contents of Proton Experimental/files/lib/wine/vkd3d-proton and files/lib64/wine/vkd3d-proton when you are on the experimental-7.0-20221115 branch and drop them back in place after switching to 1129. Then you can flip-flop experimental branches again or save the original 1129 files before messing around to get back to the original shipped version.

Billli11 commented 1 year ago

After switching proton experimental from pinned version back to main branch, the game now working now.

So may be there are some corrupted files when proton updated to build id: 10039633 and got fixed by re-downloading the affected files?

I recall having verified integrity of proton's file when the problem happen but it all validated.

I would like to test swapping vkd3d but I can't reproduce the problem and currently locked out by denuvo.

@wwmm Noting weird show up in journalctl. And I tried remove the game's shader.cache2, vkd3d-proton.cache and steam's shadercache.

So it's not likely to be shader compilation problem.

alasky17 commented 1 year ago

@Billli11 Oh shoot - denuvo :(

So may be there are some corrupted files when proton updated to build id: 10039633 and got fixed by re-downloading the affected files? That is definitely possible. "verify integrity of files" unfortunately doesn't work properly with Proton Experimental specifically right now because the system doesn't treat nested symlinks properly. So switching branches to trigger a reinstall is a better bet.

It sounds like you are no longer seeing the problem with "stock" experimental-7.0-20221129? Just verifying that I understood you correctly and the problem is fixed :)

Billli11 commented 1 year ago

@Billli11 Oh shoot - denuvo :(

So may be there are some corrupted files when proton updated to build id: 10039633 and got fixed by re-downloading the affected files? That is definitely possible. "verify integrity of files" unfortunately doesn't work properly with Proton Experimental specifically right now because the system doesn't treat nested symlinks properly. So switching branches to trigger a reinstall is a better bet.

It sounds like you are no longer seeing the problem with "stock" experimental-7.0-20221129? Just verifying that I understood you correctly and the problem is fixed :)

Yes. Both pinned version and "stock" version of experimental are working before i got locked out.

alasky17 commented 1 year ago

Yes. Both pinned version and "stock" version of experimental are working before i got locked out.

Awesome :D In that case (in case it wasn't clear), seems unnecessary to do more testing. Luckily the ban is only 24 hr not longer 😅

ingramchen commented 1 year ago

Getting some vertex explosions with the new nvidia driver 525.60.11-1 on a 2070 using arch linux. Downgraded to 520.56.06-12 and everything is fine again. The lucent nargacuga hunt was a consistent way to get the bug to show. Anyone else having the same?

I also have same problem with 525 driver, my system is nobara on a 3080.

Keelhauled commented 1 year ago

I also have same problem with 525 driver, my system is nobara on a 3080.

Forgot to mention it in my post but I'm also using flatpak steam. What about you?

ingramchen commented 1 year ago

I also have same problem with 525 driver, my system is nobara on a 3080.

Forgot to mention it in my post but I'm also using flatpak steam. What about you?

mine is from rpmfusion, so I guess steam version has nothing to do with this issue

Exestens commented 1 year ago

Compatibility Report

System Information

I confirm:

Symptoms

Game crashes when trying to join or create a lobby. Here is the log: steam-1446780.log

Reproduction

Create or join a lobby

Additional Comments

I'm not sure this is a problem with Monster Hunter Rise or with steam. The core dump from coredumpctl dump steam gives

          PID: 33277 (steam)
           UID: 1000 ([REDACTED])
           GID: 1000 ([REDACTED])
        Signal: 6 (ABRT)
     Timestamp: Sat 2022-12-17 10:29:28 CET (1min 22s ago)
  Command Line: /home/[REDACTIED]/.local/share/Steam/ubuntu12_32/steam
    Executable: /home/[REDACTED]/.local/share/Steam/ubuntu12_32/steam
 Control Group: /user.slice/user-1000.slice/session-1.scope
          Unit: session-1.scope
         Slice: user-1000.slice
       Session: 1
     Owner UID: 1000 ([REDACTED])
       Boot ID: 3c24d012f18f4bcb855d9c58253cf3f7
    Machine ID: 457fe70eb0ae401798aad8134b283d11
      Hostname: [REDACTED]
       Storage: /var/lib/systemd/coredump/core.steam.1000.3c24d012f18f4bcb855d9c58253cf3f7.33277.1671269368000000.zst (present)
  Size on Disk: 60.0M
       Message: Process 33277 (steam) of user 1000 dumped core.

                Stack trace of thread 33391:
                #0  0x00000000f7ed0549 __kernel_vsyscall (linux-gate.so.1 + 0x549)
                #1  0x00000000f7a89667 n/a (libc.so.6 + 0x89667)
                #2  0x00000000f7a35677 raise (libc.so.6 + 0x35677)
                #3  0x00000000f7a1e126 abort (libc.so.6 + 0x1e126)
                #4  0x00000000edbcf235 n/a (/home/[REDACTED]/.local/share/Steam/ubuntu12_32/vgui2_s.so + 0x15235)
                ELF object binary architecture: Intel 80386
Zukureneno commented 1 year ago

Compatibility Report

System Information

I confirm:

Symptoms

Missing textures / flickering and black boxes while running game above 60 fps limit cap. Doesn't matter the quality settings 20221213012740_1

20221217142416_1

Reproduction

Set FPS cap above 60 (mainly 120+)

kisak-valve commented 1 year ago

Hello @Zukureneno, it might be worthwhile to also mention your rendering issue to the VKD3D-Proton devs at https://github.com/HansKristian-Work/vkd3d-proton/issues.

eldritchScholar commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/5495#issuecomment-1356144832

I'm experiencing the same issue, same core dump output. I have yet to try running with the logging cranked to max, but that's my planned next step.

LAlto96 commented 1 year ago

@YoungMaestro, @kisak-valve

Anything I can try to fix it? edit: Running this command allowed me to use the graphics card and put the game full screen although now is a complete black screen and I can interact with the game (hear intro music and Navigate through the start menu) WINEDLLOVERRIDES="dxgi=b" DRI_PRIME=1 %command%

I had exact same issue : #6342

The launch parameters given by Maestro (WINEDLLOVERRIDES="dxgi=b" DRI_PRIME=1 %command%) fixed the issue forr me.

My specs are: Nvidia RTX 2060 AMD Ryzen 3600 16 Gb RAM Running on Nobara Linux

Exestens commented 1 year ago

The real issue is this one : when I try to connect to a lobby or create mine, the game and Steam both crash. (I tried both Steam and Steam flatpak, as well as regular Proton, Proton GE 43, Proton experimental and Proton Hotfix) First, the game freezes when it tries to find / create the lobby, then it closes and Steam crashes with it. Anyone else experiencing this issue?

This is the same issue that I have, and it appears one other person has. I personally haven't made any progress on this at all since I posted my report, and I am at a loss at what to try next, more or less. It doesn't seem like anything can be changed on my end to fix this issue, but I would love suggestions.

kisak-valve commented 1 year ago

Steam beta client crash Monster Hunter Rise (1446780)

Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/9093. @Billli11 posted on 2023-01-12T11:02:31:

Your system information

Please describe your issue in as much detail as possible:

The latest steam client update cause monster hunter rise (1446780) to crash after shader compile, before RE Engine intro video.

Steps for reproducing this issue:

  1. Join Steam beta
  2. Restart Steam
  3. Start Monster Hunter Rise
  4. Wait for crash

Tested the following.

  1. Revert to stable client.(linux and Steam Deck client). Running
  2. Switch proton version. Not working
  3. Set VKD3D_CONFIG=swapchain_legacy. Not working
  4. Remove shader cache. Not working
  5. Re-download game files. Not working

steam-1446780.log

@minecraft2048 commented on 2023-01-12T11:28:23:

Seconded this, Arch Linux KDE Wayland

kzdixon commented 1 year ago

Compatibility Report

System Information

I confirm:

Symptoms

Monster Hunter Rise never fully compiles shaders on RX 7900 XTX.

Reproduction

  1. Launch Monster Hunter Rise
  2. Watch as it "compiles" shaders
  3. See that it never finishes even if left open for hours

Tested on all versions of Proton I usually use: Proton 7.0-5/6, Proton Experimental (Bleeding-Edge) and GE-Proton7-43.

Update: This is fixed a recent mesa merge (see https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20941). Should be released in the near future I assume.

I believe the fix has been merged in and released as of mesa 22.3.5.

Bisc0tt1 commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/5495#issuecomment-1380390130

Very likely this issue wasn't specific to MHR, and the game would merely crash due to the excessive amount of X11 clients spawned due to a bug in the Steam client beta, see here: https://github.com/ValveSoftware/steam-for-linux/issues/9094. This issue has been fixed and the game launches fine now.

maliciousbanjo commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/5495#issuecomment-1356271126

I have also been experiencing this exact issue.

System OS: Linux Mint 21.1 x86_64 Kernel: 5.15.0-58-generic GPU: Nvidia RTX 3080 TI GPU Driver: 525.78.01-0ubuntu0.22.04.1

The issue appears to be related to the Nvidia driver; rolling back to 515.86.01 resolves the problem. I first saw this issue on 525.60.11.

sclu1034 commented 1 year ago

System Information

steam-1446780.log.gz

Symptoms

The game window never goes into fullscreen. When trying to make it fullscreen via the window manager, it will go back to windowed immediately. It also re-positions itself to 0, 0 when moved. At the same time, the game's display options are set to fullscreen. Attempting to change any game option related to the display (e.g. Output Display, Screen Mode, Resolution, Display Frequency) is not possible. When trying to select another value for one of those options, it'll jump back immediately. Moving the window between screens does make it snap to that screen's 0, 0, and the Output Display option changes. But it changes to "4. Display", when there are only three screens physically and only two of them active.

Additionally, the Display Frequency option does not recognize that one display's maximum refresh rate is higher than the other. It only goes up to 144Hz for both of them, but one is capable of 165Hz.

Lastly, the game does not use the hardware potential at all. It sits at around 30 - 32 FPS and the GPU at ~30% utilization. And MangoHUD shows 0 FPS.

ingramchen commented 1 year ago

@sclu1034 I have the same GPU which works fine (though I am on nobara, mesa 22.3). Maybe you can try to disable integrated graphics in BIOS

sclu1034 commented 1 year ago

@sclu1034 I have the same GPU which works fine (though I am on nobara, mesa 22.3). Maybe you can try to disable integrated graphics in BIOS

That did help, thanks. Guess I'll have to make due without the iGPU for the time being.

0xC0ncord commented 1 year ago

System Information

Note that I've had to add an LD_PRELOAD entry for libstdc++ or else the Steam client will crash on startup due to the presence of libc++ on my system (see https://github.com/ValveSoftware/steam-for-linux/issues/8923#issuecomment-1356656896). I've manually set LD_PRELOAD='' in the game's launch options to ensure this wasn't causing any issues.

Symptoms

Since update 14.0.0 to the game was released a few days ago, I have been completely unable to launch it. Steam will launch the game, and after about 10 seconds, the game crashes with no errors or warnings visible. No game window ever appears (unless it's Denuvo telling me I've reached the activation limit for the day). Prior to this update, everything was perfectly fine. No amount of switching Proton versions, clearing the shader cache, or reinstalling the game has helped thus far. I've also tried running the game under the Flatpak version of Steam without success.

steam-1446780.log

faattori commented 1 year ago

After the recent Proton Experimental version update from 7 to 8, my game crashed at the beginning during the intro videos.

Deleting the prefix fixed the issue.

90958566 commented 1 year ago

After finishing a ingame quest, black squares artifacts appear prior to the Quest Cleared logo. Always. This seems to happen after Sunbreak Title Update 5 [15.0.0.0 game version). I tried both the 7-XX and 8-XX GE-Proton branches. I have been playing on Linux since day one and this is my first issue (anything else works fine). I'm not sure if this is the best place to report it though. Anyway, let me thank you for your hard work.

kisak-valve commented 1 year ago

Hello @90958566, can you reproduce the rendering artifacts with a mainline Proton version?

Please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, 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.

0xC0ncord commented 1 year ago

Not sure if this is the right avenue to report this issue, but recently I picked up a Steam Deck and I'm able to reliably reproduce a game freeze. (This issue isn't related to the problems I described above.)

If I connect an external controller to the Deck over USB-C and launch Monster Hunter Rise, the game freezes whenever the controller is supposed to rumble (e.g. when a monster roars). This happens even after disconnecting the external controller and using the Deck's built-in gamepad. A reboot of the Deck without the external controller connected is what is needed to resolve it.

kisak-valve commented 1 year ago

Hello @0xC0ncord, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the freeze, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

0xC0ncord commented 1 year ago

@kisak-valve Turns out in order to reproduce the freeze, the external controller must be disconnected after connecting it at least once. Just to make sure we're on the same page, here is what I did to reproduce it:

  1. Log into the Steam Deck.
  2. Connect an external controller to the Deck. In my case I have a USB hub connected over USB-C with a Steam controller dongle connected.
  3. Disconnect the Deck from the USB-C hub (and thus the Steam controller).
  4. Start Monster Hunter Rise.
  5. Do anything in-game that causes the controller to rumble and the game will freeze.

Also note that I was able to reproduce this on Proton 7.0-6 and Proton 8.0-2. Here's the log. Thanks!

steam-1446780.log.gz

KuraiSiruru commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/5495#issue-1103134357

My issue is very similar. It compiles shaders, then freezes on the health warning screen. except i have an RTX3060, not an AMD GPU

kisak-valve commented 1 year ago

Monster Hunter Rise

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6769. @KuraiSiruru posted on 2023-05-12T16:21:46:

Compatibility Report

System Information

I confirm:

steam-1446780.log

Symptoms

Most versions of Proton produce a black windowed screen. Proton 8.0-2 allows the game to process shaders, however it freezes on the health screen directly after.

Reproduction

start the game

foolishprogrammer commented 1 year ago

Compatibility Report

System Information

I confirm:

steam-1446780.log

Symptoms

Game status is running, but sometimes show blank window and then goes invisible. My mouse and gamepad still interact with the game. Once in a while, the game runs as usual, usually after i play another game like DOTA2 or MH World. But most of the time, even after playing another game, the same symptom occur. I try to go with the GE version, the same symptoms occur, or just the game keep blinking (more like STROBING like strobe light effect). I try to run steam back into stable version, the same symptom still occur. The game runs well before on 7.0-6 on gnome43, after updating to gnome44, this start to occur. When I try to run it on steam --debug from terminal, I can see the "Fossilize" unable to handle the pipeline. There is a lot more memory address spewed on the error, but one of the Fossilize WARN is like this :

Fossilize WARN: Pipeline library handle 0x00007fe021bc33e0 is not registered.

It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).

Reproduction

Start the game, or Start the game after playing another game.

SeongGino commented 1 year ago

~~Seems like this game has an issue with the shaders having to be built every time. And sometimes during said every-boot shader compilation, it crashes with a Fatal D3D Error (6). 2023_07-14 114450-Error The crashing isn't very consistent; it happens maybe once every other boot. This is with the game installed fresh from Steam.~~

~~Proton Log here (Experimental). steam-1446780.log~~

EDIT: Both shaders not saving/shaders compiling on every boot and the crashing seems to have been resolved by NVIDIA 535.86.05 (was using 535.54.03 when this problem was observed)

mattipulkkinen commented 1 year ago

There's an issue with flickering reflections or glare on the water in the Frost Islands map. The issue is dependent on which antialiasing setting you're using, specifically so that the flickering is present if TAA is not enabled.

I'm using Proton Experimental.

I recorded a short demonstration of what this looks like: https://gofile.io/d/8u32x1

System:
  Kernel: 6.4.4-200.fc38.x86_64 arch: x86_64 bits: 64 Desktop: GNOME v: 44.3
    Distro: Fedora release 38 (Thirty Eight)
Machine:
  Type: Desktop Mobo: ASRock model: X570 Taichi serial: <superuser required>
    UEFI: American Megatrends v: P5.01 date: 01/18/2023
Battery:
  ID-1: hidpp_battery_0 charge: 88% condition: N/A
CPU:
  Info: 8-core AMD Ryzen 7 5800X3D [MT MCP] speed (MHz): avg: 1807
    min/max: 550/4550
Graphics:
  Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] driver: amdgpu
    v: kernel
  Device-2: Realtek Streamplify CAM driver: snd-usb-audio,uvcvideo type: USB
  Display: wayland server: X.Org v: 22.1.9 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu
    resolution: 2560x1440~240Hz
  API: OpenGL v: 4.6 Mesa 23.1.4 renderer: AMD Radeon RX 6800 XT (navi21
    LLVM 16.0.6 DRM 3.52 6.4.4-200.fc38.x86_64)
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
  Device-2: Intel I211 Gigabit Network driver: igb
Drives:
  Local Storage: total: 1.82 TiB used: 1.09 TiB (60.1%)
Info:
  Processes: 517 Uptime: 42m Memory: available: 31.25 GiB
  used: 5.02 GiB (16.1%) Shell: Zsh inxi: 3.3.27
kisak-valve commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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: 20230809172402_1 20230810183025_1

alasky17 commented 1 year ago

@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 commented 1 year ago

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

steam-1446780.log

Blisto91 commented 1 year ago

@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 commented 1 year ago

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.

https://github.com/ValveSoftware/Proton/assets/13204623/2a89bc59-bff1-4e86-b3b0-6c835a329bc4

steam-1446780.log runtimeDisagnostics.txt

Jorgee1 commented 1 year ago

Compatibility Report

Name of the game with compatibility issues: Monster Hunter Rise

Steam AppID of the game: 1446780

System Information

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

I confirm:

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

monster hunter error

Already tried the following launch options without success:

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 commented 1 year ago

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

Jorgee1 commented 1 year ago

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

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

Regards

Jorgee1 commented 1 year ago

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.

Screenshot from 2023-10-21 16-13-25

LunaRosalie commented 10 months ago

Capcom updated the game today which completely broke steam deck support

SeongGino commented 10 months ago

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 commented 10 months ago

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 commented 10 months ago

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 commented 10 months ago

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.