Monster Hunter Rise Demo (1641480)

[ryliejamesthomas]

Compatibility Report

• Name of the game with compatibility issues: Monster Hunter Rise Demo
• Steam AppID of the game: 1641480

System Information

• GPU: RX 570
• Driver/LLVM version: 4.6 Mesa 21.2.3
• Kernel version: 5.14.11-arch1-1
• Link to full system information report as Gist: https://gist.github.com/ryliejamesthomas/dea2b8c3485237f21825857069b8953c
• Proton version: 6.3-7, and 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-1641480.log

Symptoms

Game closes itself. With Proton Experimental it crashes on the first options screen (where it asks for language, etc.), with 6.3-7 it crashed when compiling shaders (which is after this options screen), but trying a few times I got to the title screen. Entering options from here also crashes.

Controllers don't seem to work, but haven't dug into that much. I have Switch Pro Controller, XBox 360 Wired, and a PowerA XBox One wired controller all plugged in.

Worth noting that this is a RE Engine game?

Reproduction

Install and run game.

[nadanke]

Couldn't get it to work with Proton Experimental, but works perfectly with current Proton GE. Arch, current stable drivers and kernel, RTX 3080

Edit: Just tried it again with Experimental, and it works now. It did definitely crash on first launch (with Experimental), though.

[ryliejamesthomas]

Should note this thread on the Steam forum, where people are having a variety of results: https://steamcommunity.com/app/1446780/discussions/0/3122675677663493291/

[itinerare]

I've consistently gotten as far as the title screen/menu with Proton Experimental after a false start when first launching it, but I can't convince controller (DS4, wired) to work despite some fiddling with it/digging into the issue so haven't gone further. Distro is Ubuntu/Pop!_OS 21.04 specifically if it's of help.

Edit: Convinced controller to work on Proton GE after trying it again (had issues the first time or two like Experimental).

[Oschowa]

You need to enable shader pre-caching in steam for it to not crash on videos during start-up on experimental. It also requires RADV_DEBUG=invariantgeom %command% as launch option on AMD RDNA2 GPUs for the time being.

[DonKatsu]

This might be a GCN1 GPU issue that needs to be reported to mesa. But I'll start here since I'm no expert.

• GPU: R9 280
• Driver/LLVM version: 4.6 Mesa 21.1.8
• Kernel version: 5.14.11-301.fsync.fc34.x86_64
• Full system information: Gist
• Proton version: 6.3-7, Experimental, 6.13-GE-1, 6.19-GE-2

My game's initial shader compilation seems to be hanging with ACO. I can leave the game running for an hour with the loading image spinning in the corner but nothing happens.
This happens with all the above Proton versions. As an aside, I have to change the OS version of 6.3-7 and 6.13-GE-1 to Windows 8.1 using protontricks or else the game gives an "Unsupported OS" error.

When I launched the game with the launch option RADV_DEBUG=llvm, it compiled its shaders. Took around 20 minutes.
I can get in a hunt, and I'm pretty sure everything looks as it should. I've set the framerate to unlimited to see how high it goes in a hunt. It hovers in the high 70s, but there's constant stutter and judder that brings it way down as it occurs.

If I start the game without llvm, it tries to compile shaders again and fails. Then when I switch back to llvm, the game again goes straight from splash screens to the title screen.
Where does the game store its shaders anyway? It still retains them even after renaming its compatdata and shadercache folders. There's an 8 byte shader.cache file in the game folder but removing that does nothing either.

I had tried 6.13-GE-1 at a steam user's suggestion, which is what lead to me trying llvm. With this version it instead crashes a few moments after the game goes to full screen. In the log, I see the following error at the bottom. I had this exact kind of ACO error (with a differing opcode) early this year with a program that used vulkan. It got fixed in a mesa update after it was brought to their attention.

ACO ERROR:
In file ../src/amd/compiler/aco_assembler.cpp:88
Unsupported opcode: v2b: %162:v[20][0:16] = v_mul_f16 %113:v[20][0:16], %113:v[20][0:16]

6.19-GE-2 with no launch options gets to the initial shader compilation screen like 6.3-7 and Experimental, but hangs as well. Both GE builds work the same as 6.3-7 and Experimental when using llvm.


Logs:
steam-1641480 6.13-GE-1 ACO.log
The one containing that ACO error.

steam-1641480 6.3-7 ACO.log
steam-1641480 Experimental ACO.log
steam-1641480 6.19-GE-2 ACO.log
Hanging at the initial "Compiling shaders" screen. The game has to be closed through the library. Closing with alt+f4 leaves it running in the background.
Refreshing the log at the "Compiling shaders" screen, the last message that comes up until the game is closed is err:virtual:virtual_setup_exception stack overflow. The game's CPU usage drops off from 40% to 15% at this point.

steam-1641480 6.3-7 llvm.log
steam-1641480 Experimental llvm.log
steam-1641480 6.13-GE-1 llvm.log
steam-1641480 6.19-GE-2 llvm.log
Launched with RADV_DEBUG=llvm. Quit game from title screen.

[Oschowa]

RADV_DEBUG=invariantgeom on RDNA2 as mentioned in my comment here #5223 (comment) isn't necessary anymore with the recent Experimental update and vkd3d-proton 2.5.

[kisak-valve]

Tracking note: Keeping the Mesa / RADV labels for @DonKatsu's feedback.

[hakzsam]

@DonKatsu Could you try with a more recent Mesa? 21.1.8 is old and I'm pretty sure your issue has been fixed since.

[DonKatsu]

I can let you know after Fedora gets a newer version of Mesa, since I'm not inclined to compile and install the latest version myself.

[DonKatsu]

Well that was some timing. Upgraded to Fedora 35, which came with Mesa 21.2.5.
Removed the RADV_DEBUG=llvm launch argument, and the game generated its shaders without issue. No stuttering or hitches in menus or in a hunt. FPS was stable at the cap I had set.

[jorgerf05]

Hi! I'm having some massive fps drops and weird camera movement when looking a certain direction in this demo, but it ran without any issues about 2 or 3 weeks ago. Is it just me? Does the game still runs fine in your PC's?
So far I've tried reinstalling steam, re-downloading the game, reinstalling proton, changing proton version and changing mesa-git back to mesa 21.2.5. I used to be able to run this game at +100 fps, now it barely can reach 60 when I look at the ground or a wall, and goes to 1-2 fps when I look at the center of the map.
Other games in my system run as expected (Rocket League and The Witcher 3, running with Wine GE/Wine lutris), so i'm guessing that it is not a system-wide issue. After closer inspection using a system monitor, I saw that when I looked in a specific direction, my GPU and GPU usage dropped dramatically. I can record a video and post the link here if it's allowed and helpful.
I'm running a Radeon RX 5600XT + Ryzen 3 3300x + 2x8GB@3200MHz RAM, kernel 5.15.2-arch1-1

[DonKatsu]

@jorgerf05
I fired it up again, and while it's not as bad as your case I've lost at least 30 frames on average as well with lots of judder.
Graphics pipe in radeontop seems to top out at around 50% with occasional spikes to 60%. My mesa is still 21.2.5. However, looking at my update history, I see I got 21.2.5-2 yesterday.

Proton 6.3-7 and Experimental are the same. Proton 6.20-GE-1 doesn't even launch the game anymore. Proton 6.21-GE-2 is the same as the first two.
Made some new logs. Went in to the Mizutsune hunt and ran to the stone arch in each one, then quit to the main menu to exit the game. Except for 6.20-GE-1, since that doesn't launch. Don't know if they mean anything, but two things I notice immediately are 6.3-7 and 6.20-GE-1 going for esync instead of fsync, and all logs get a little spam about not being able to open libgamemode.so when I have it installed.
steam-1641480 6.3-7.log
steam-1641480 experimental.log
steam-1641480 6.20-GE-1.log
steam-1641480 6.21-GE-2.log

[jorgerf05]

After switching to 6.21-GE, the game now won't start. Going back to experimental didn't help, now the game won't start at all.
Other games such as Paladins or Aimlab work as expected with proton.
steam-1641480-proton6.3-7.log
steam-1641480-6.21GE-2.log
steam-1641480-experimental.log

[DonKatsu]

Tried again. Framerate back to mostly maintaining my set limit of 90. No judder. Feels like it did for me on the 3rd. However unlike then, Proton 6.20-GE-1 still won't launch the game.
Not sure what graphics pipe used to be before this last issue but now it's staying between 60 to 70% in hunt at my desired settings. CPU settles in around 70 to 80% on all four cores. Seems about right overall given the listed requirements.
My mesa is still 21.2.5-2, so I could only speculate on what might have changed to help.

[jorgerf05]

I decided to give it a go today. It is working as expected now. No idea what changed, but I'm glad it runs fine now:)

[jolty1]

It launches but then crashes for me with my Switch Pro Controller connected. Works fine disconnected,

steam-1641480.log