protonscr

Monster Hunter Stories 3: Twisted Reflection Trial Version – crashes on startup on ARM64 (Proton Experimental 11.0 ARM64 / FEX / Turnip Adreno 740)

protonclosed appid 3470630
ValveSoftware/Proton#10224 · opened 2026-10-06 by festaumberto · updated 2026-10-06 · 2 comments · github · game page · search this game
Ffestaumberto 2026-10-06 github

Compatibility Report

  • Name of the game with compatibility issues: Monster Hunter Stories 3: Twisted Reflection – Trial Version
  • Steam AppID of the game: 3470630

System Information

  • GPU: Qualcomm Adreno 740 (Turnip, Mesa 26.2.3, Vulkan)
  • Device / SoC: Snapdragon 8 Gen 2
  • Video driver version: turnip Mesa driver 26.2.3
  • Kernel version: Linux 7.2.6 aarch64
  • Distribution: Armada 20260926.c2fd048
  • Proton version: Proton Experimental (ARM64), experimental-11.0-20261001-arm64
  • Steam Linux Runtime: steamrt4 4.0.20260805.254769, pressure-vessel 0.20260805.0
  • FEX version: bundled
  • Session: Gamescope (the log shows "[Gamescope WSI]")
  • DXVK 3.1.1, vkd3d-proton 3.1.0

I confirm:

  • [x] that I haven't found an existing compatibility report for this game and Proton version. Related: #10216 (full game, same ARM64 + Turnip + FEX setup, crash on startup, closed as duplicate)
  • [x] that I have checked whether there are updates for my system available.

Symptoms

The game crashes during startup, a few seconds after the first D3D12 swapchain is created. It never reaches the title screen. The crash handler (CrashReport.exe) then also crashes.

From the log, the main thread hits an access violation in the game's own executable:

Exception 0xc0000005 (EXCEPTION_ACCESS_VIOLATION)
addr = MONSTER_HUNTER_STORIES_3_TWISTED_REFLECTION_TRIAL.exe + 0x45E50BD
read access (info[0]=0) at address 0x70 (0x40 in the second run), i.e. a null pointer plus a small offset

backtrace (all inside the game exe):
  +0x45E50BD
  +0x4402B64
  +0x45BBB6D
  +0x45B3195
  +0x7857081
  +0xAB6E48

Right before the crash, the NVIDIA Streamline layer that ships with the game (v2.8.0) reports:

[streamline][error] sl.cpp:185[slValidateFeatureContext] 'kFeatureDLSS_G' context is missing.

Earlier in the same log Streamline disables all its plugins because the hardware is not NVIDIA:

sl.dlss not supported on current hardware
Disabling DLSS-G since it is not supported on current hardware
Ignoring plugin 'sl.common / sl.pcl / sl.dlss / sl.dlss_d / sl.reflex / sl.dlss_g' since it is not supported on this platform

My interpretation (not verified): the game keeps going after Streamline has rejected every plugin, gets a null context or interface, and dereferences it without checking. This may be a bug in the game's non-NVIDIA code path, but I can't rule out that it is specific to ARM64/FEX.

The crash is the same with and without PROTON_DISABLE_NVAPI=1: same address, same backtrace (only the null offset differs).

The vkd3d-proton log does not show a Vulkan or pipeline creation error before the crash. This differs from #10216, which reports vkCreateComputePipelines Exception 0xc0000005 in Unix call on an Adreno 830, so these might be two separate bugs.

Reproduction

  1. Install the Trial on an ARM64 device with Proton Experimental (ARM64).
  2. Launch the game.
  3. The game shows its window briefly, then crashes before the title screen.

Launch options tried: default, and PROTON_DISABLE_NVAPI=1 %command%. Both crash the same way.

Logs

Attached: full Proton logs (PROTON_LOG=1, with the default debug channels, +seh +unwind +loaddll +debugstr +mscoree).

  • steam-3470630.log (default options)
  • steam-3470630_1.log (PROTON_DISABLE_NVAPI=1)

Noise that is not related, for reference: the missing gameoverlayrenderer.so preload errors, winebth failing to start, err:hid ... Failed to get parent device, and CrashReport.exe failing with System.InvalidOperationException: Category does not exist (PerformanceCounter, secondary crash).

Not yet tried

  • Removing or renaming the sl.*.dll files from the game folder
  • Older Proton versions
Kkisak-valve maintainer 2026-10-06 github

Hello @festaumberto, you should have been aware of this from the other duplicate that you found, but setting that aside I'll repeat. We're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/9469#issuecomment-6017067337.

Related threads

Proton versions

Launch options

Launch lines

Upstream links

Error codes