STRANGER (1902150)

[Patola]

Compatibility Report

• Name of the game with compatibility issues: STRANGER
• Steam AppID of the game: 1902150

System Information

• GPU: RX 6800 XT
• Driver/LLVM version: Mesa 22/1/7
• Kernel version: 5.19.6-269-tkg-bmq
• Link to full system information report as Gist: https://gist.github.com/Patola/e51e3af1be3c7d233b8f14fb21be1aa6
• Proton version: 7.0-4

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.

Symptoms

When starting VR mode, the game shows an OK dialog with title "The UE5-StrangerVR Game has crashed and will close" and the message "Fatal Error!" and then quits.

Reproduction

• Start SteamVR
• Start the game either via SteamVR or the game start choice "Launch XR Version in OpenXR Mode"
• In the game, select to start campaign, any level (I usually select "training mode" for the tutorial)
• The VR headset screen briefly shows a floating loading screen
• The dialog "Fatal Error!" appears on the flat screen and the game exits.

A screenshot is attached along steam-1902150.log with the proton log.

[kisak-valve]

Hello @Patola, my eyes seem to be reading an access violation (c0000005) in a thread called RenderThread 2. It's unclear from the log if the game is using AMDGPU-PRO or mesa/RADV. Can you force the game (and SteamVR) to use mesa/RADV and verify it behaves the same?

[Patola]

Is there any way to force AMDGPU? I'm using amdgpu (RADV) by default, I have amdgpu-pro installed but I'm not running anything to make it active, like settings the VK_ICD_FILENAMES to amdgpupro or something and glmark2 tells me I'm using AMD RADV SIENNA_CICHLID, so I am using the open-source driver only. Should I nevertheless run it with VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json prepended to the launch options?

[Patola]

Forced vulkan with the mentioned variables, launch options: PROTON_LOG=1 VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command% steam-1902150.log

Same result, identical as previously. Which should be, since I'm using only amdgpu and not amdgpu-pro.

[Patola]

steam-1902150-WINEDEBUG=+openxr.log And this other log uses WINEDEBUG=+openxr instead of steam-1902150-WINEDEBUG=+openxr.log PROTON_LOG=1

[Patola]

And now I actually forced amdgpu-pro (using VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd32.json:/usr/share/vulkan/icd.d/amd_pro_icd64.json PROTON_LOG=1 %command%) but the result was the same. Same dialog, and it seems the error is the very same: 100200.223:0128:012c:warn:seh:dispatch_exception "LowLevelFatalError [File:D:\\build\\++UE5\\Sync\\Engine\\Source\\Runtime\\RenderCore\\Private\\RenderingThread.cpp] [Line: 934] \nRendering thread exception:\r\nFatal error!\r\n\r\nUnhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000000\r\n\r\n0x00007f25cc0807f9 w"... steam-1902150-amdgpu-pro.log