protonscr

Monster Hunter Stories 3: Twisted Reflection

protonopen appid 2852190Game compatibility - Unofficial
ValveSoftware/Proton#9581 · opened 2026-03-17 by TheMCNerd2017 · updated 2026-07-02 · 7 comments · github · game page · search this game
TTheMCNerd2017 2026-03-17 github

Compatibility Report

  • Name of the game with compatibility issues: Monster Hunter Stories 3: Twisted Reflection
  • Steam AppID of the game: 2852190

System Information

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.

Proton log: steam-2852190.log

Symptoms

Like in the free demo, textures of objects constantly flicker in and out while in the overworld, cutscenes and battles along with bright light flashes if it occurs during certain cutscenes or in certain areas of the game. I have attached a few screenshots of this occurring in a later area of the game. This only occurs if the game is running at a frame rate higher than 30; capping frame rate in the in-game settings results in the flickering stopping completely.

What is more strange about the full game is that this has a rare chance of not happening during an entire session; the first time I played the full game while transferring my demo progress, I was able to play the game for a couple hours at 60 FPS without the flickering issue coming up. However upon starting another session the next day (software version on my laptop did not change during the period in which I did not play), the flickering issue returned. All other sessions I had afterwards had the flickering issue present.

Image

Image

Image

Image

Reproduction

  1. Open the game and either create a new save file, load a save file, or transfer your demo progress.
  2. Play the game normally.
  3. After around a couple minutes, the textures of objects start to flicker in and out randomly.
Cchnpn 2026-03-18 github

In my case, the game can crash or completely freeze at any time. This happens unpredictably — sometimes right after launch, and other times after long sessions (e.g., 10+ hours of gameplay). There doesn’t seem to be a consistent trigger. I've tried various Proton versions, all having the same crash.

Logs: https://gist.github.com/chnpn/3d0754a840e5c816066298ab29bc2139

System:

  • OS: Bazzite (bazzite-gnome:stable)
  • Kernel: Linux 6.17.7-ba28.fc43.x86_64
  • CPU: AMD Ryzen 9 7900
  • GPU: AMD Radeon RX 6900 XT
  • RAM: 32 GiB
Ccameronbosch 2026-03-18 github

I've had very different experiences with different GPUs from different brands.

I have had the same issues as others have mentioned here on my both my Nvidia RTX 5090 laptop and my desktop with an RTX 4090, both when they were on the 590 driver stack. This is a known issue with the Nvidia 590 drivers and RE Engine games like this one. Updating the driver to 595 in my system fixes the issue, but as far as I know, Arch Linux does not have the driver in their repos yet and it's been over a week since it was released by Nvidia. I had to install them using these instructions just for this game and any RE Engine games so that this wouldn't happen and basically make the game unplayable. #9469 has a bunch of users noting the same thing. Below is me recording the issue on my laptop (the one with the 5090 laptop GPU) freehand because I would have 1% issues whenever I tried to run the game and OBS Studio together. This was the demo but this was still happening in the fiull game, and since the full game has Denuvo with the "5 installs per 24 hours" option enabled (which if you know every time the Proton version is changed it counts as a new install), this is not great for users with Nvidia.

https://github.com/user-attachments/assets/e2d44868-c336-4333-9fe1-4829637d9ee1

@chnpn I will note that I did have a crash on my Legion Go 2 running CachyOS Handheld (the AMD Z2 Extreme model), but only once and only after I was playing for almost two hours straight. While running around the first town/castle area in Azuria, the Wine debugger window popped up and the game crashed. I have not been able to replicate this again though. What graphical settings did you use on the game and what FSR settings were you using? I was using high settings except with motion blur disabled and shadow quality set to medium instead of high, as well as FSR 4 set to performance (I was using FSR 4 with the FSR DLL replacement hack).

I do find it strange that Bazzite with 595 still seems to have graphical issues with RE Engine games. @TheMCNerd2017 are you sure that the Nvidia open kernel modules and the proprietary user-space utilities are the same version?

I really hate that all three GPU vendors seem to not give 💩💩 about gaming right now...

TTheMCNerd2017 2026-03-18 github

@cameronbosch The Nvidia open kernel modules and the proprietary user-space utilities should be the same version as it's usually the exact same as what's in Fedora. How should I check for sure though just in case one utility is an older version? Nvidia-smi and Nvidia X Server settings are all the same version as the drivers.

Also, could my GPU being classified as a professional workstation GPU make a difference?

I just think it's very strange that I was able to have one play session where the graphics didn't do the flickering, then all future play sessions have the issue.

Cchnpn 2026-03-20 github

@cameronbosch I’ve also experienced a few crashes on my Legion Go 1 (Bazzite-dx-deck). I haven’t had a chance to collect logs yet, and since I’ve been tinkering with Decky FrameGen and Lsvk, I’m not sure if it’s the same issue as on my PC. That said, it does feel more stable overall compared to my PC.

On my PC, I’m playing at high settings in 4K resolution without upscaling. I hope this may be resolved with future updates, as my GPU had a similar issue with Monster Hunter Wilds at launch, and it has since become quite stable.

Ccameronbosch 2026-03-26 github

Turns out Nvidia is at it again. Heck, even Capcom seems fed up with Nvidia's crap (in addition to DLSS 5's "reveal"):

"Riders on PC, we've identified that there are some crash related issues for Monster Hunter Stories 3 with some Nvidia drivers, such as 595.79 and 595.97.
We are investigating this as a priority directly with Nvidia. Thank you for your feedback and reports on this, we hope to have more to share with you soon."

Funnily enough, I've had no issues on 595 apart from having to install it manually because Arch Linux still does not include any version of 595 in their repos despite 590 being completely unusable in any RE Engine game. (For those who are wondering, it's the 595.58.03-1 nvidia-open-dkms drivers.)

I'm more surprised that AMD is also having issues! Likely not to the same degree as Nvidia, but still!

AArnagos 2026-05-15 github

@cameronbosch I'm using driver 595.71.05 with a 4090 and still have disappearing geometry. I don't think this issue is actually fixed yet. The only difference is that I'm playing Pragmata and not MHS3.

Ccameronbosch 2026-07-02 github

I'm using driver 595.71.05 with a 4090 and still have disappearing geometry. I don't think this issue is actually fixed yet. The only difference is that I'm playing Pragmata and not MHS3.

Did you try again after the early April update? Still very strange that is is happening in some games but not other RE Engine games, and especially only on Nvidia.

It appears that in Resident Evil Requiem and Monster Hunter Stories 3 Twisted Reflection (https://github.com/ValveSoftware/Proton/issues/9469) where I and user @TheMCNerd2017 had the issue on that game that Capcom themselves had tracked down the issue to Nvidia and their drivers being so horrifically bad.

Despite the message from Capcom, I only had serious issues with RE Engine games on 590, not 595. And never on AMD or Intel GPUs.

AFAIK, this plot just keeps thickening and it's infuriating that Nvidia still cannot or will not fix the VKD3D issues that make Linux gaming so bad (because non Nvidia dGPUs do not exist on laptops right now since 2025 and the price of GPUs and RAM keeps climbing because of the AI bubble)...

Upstream links