Rise of the Tomb Raider (391220)

[karli-sjoberg]

Compatibility Report

• Name of the game with compatibility issues: Rise of the Tomb Raider
• Steam AppID of the game: 391220

System Information

• GPU: GTX 1060 & RTX 2070
• Driver/LLVM version: nvidia 460
• Kernel version: 5.11.6
• Link to full system information report as Gist: link
• Proton version: 5.13-6 & Proton Experimental

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.

steam-391220.log

Symptoms

Really strange graphical behavior with a halo of sorts emanating from the heads of enemies and friendly NPC's. They say a picture is worth a thousand words, so here's a 1 200 000 word report :smile: https://thecool.tube/videos/watch/7ec5b0cf-cb26-434d-91ef-424182a94b6f

Reproduction

Start the game with DX12 enabled and play until you meet first NPC or enemy. Would've worked around it by just using DX11 instead but the game is unplayable due to ho-o-o-orrible stuttering while processing shader data

[kisak-valve]

Rise of the Tomb Raider (391220) Crashes Immediately on Start ... After Playing for 99 min

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5236. @PorcelainMouse posted on 2021-10-21T06:28:01:

Compatibility Report

• Name of the game with compatibility issues: Rise of the Tomb Raider
• Steam AppID of the game: 391220

System Information

• GPU: AMD Radeon 5700XT
• Driver/LLVM version: AMD AMD Radeon RX 5700 XT (NAVI10, DRM 3.42.0, 5.14.9-200.fc34.x86_64, LLVM 12.0.1)
• Kernel version: 5.14
• Link to full system information report as Gist: https://gist.github.com/PorcelainMouse/501732a24b2c407b9b0e74f221aa1aa5
• Proton version: no specific version forced, using default

I confirm:

• [ x ] that I haven't found an existing compatibility report for this game (that was similar). One compatibility report exists, but symptoms where wildly different and different hardware.
• [ x ] that I have checked whether there are updates for my system available.

I tried several times to get this log, but it was never created. I checked everywhere.

Symptoms

I played ROTR for about 99 after launching it for the first time. But, after quitting the game & steam, the next time I started Steam and launched the game, it crashed and continues to crash no matter what I do. I reached on to Steam (no help) and Feral Interactive, who kindly sent me troubleshooting instructions. They suggested clearing the Steam cache and verifying the game files. I tried those and still the game crashes. This makes no sense, since it ran perfectly find just two days before. I didn't even reboot the computer between working & crashing conditions, no updates to flatpak, or system occurred between conditions. Since then, I have rebooted an updated flatpak, but not any part of my system.

I let the automated crash reporting system report the first crash dump. But, subsequent dump files have not been reported.

Reproduction

• Install ROTR
• Start game, play for an hour or so
• quit game
• quit Steam
• start Steam
• launch ROTR, crashes

Crash msg:

[kisak-valve]

Hello @PorcelainMouse, looking more closely at your issue report, you're using Feral Interactive's native linux port of the game. Proton is a compatibility layer to run Windows based games on Linux, and since you're using the native linux variant of the game, this project isn't involved at all with your issue.

[PorcelainMouse]

Thanks for looking at it! You know, that's what I thought, but I figured I didn't understand proton well enough to be sure. I was just following Steam's support instructions. I guess I'm dead in the water. Their support wasn't able to fix it, either.

[weter11]

Don't know about desktop PCs, but on my notebook {5800H & RTX3070} DLSS is not working, I tried blacklist AMD iGPU, update nvapi and nvngx_dlss, insert '__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 %command%'. Log always report: DLSS support test, code = 0x00000001, info: NVSDK_NGX_Result_Success Disabling DLSS as it is not supported on non Nvidia cards

[weter11]

I insert DXVK_CONFIG_FILE=/home/wer/.local/dxvk.conf DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 3070 Laptop" PROTON_ENABLE_NVAPI=1 %command% to game settings window. dxvk.conf contain only: dxgi.nvapiHack = False And voila DLSS working now. Its strange, but DLSS don't provide additional performance, 100fps w/o any AA and 104 with DLSS quality, also GPU heavily underclocked, sometimes only 55-65% load.

[ThisNekoGuy]

PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 DXVK_CONFIG_FILE=(path-to-file) with dxgi.nvapiHack = False is enough to get DLSS to work fine for me.

The game does still stutter pretty hard from time to time though, hanging for few seconds on a single frame, but this goes away over time the more the game is played. Though, the framerate can decide to swing wildly from time-to-time depending on the resolution set.

[hamburgerghini1]

Bug that prevents me from progressing in the game. On the other side there should be a bucket where you can attach the rope. I don't know what to do to fix this.

[ruineka]

The game works well using DX11, but when you use DX12 hair and wet surfaces tend to render as a "glowing white" texture instead of the proper render on a Intel A750 Arc GPU. Performance is also hit pretty hard compared to using DX11.

Running with Mesa 22.3.1 - kisak-mesa and kernel 6.0.6-76060006-generic on Pop OS.

steam-391220.log

[Hadrianneue]

This is a little weird to explain so bare with me here.

i'm using a Dualsense joystick and on windows the game detects it as a DS4 if steam input is disabled

on linux, first of all i changed my dualsense light bar color to steam purple and whenever steam input is on that will be the light bar color, otherwise it will be blue (games that support dualsense natively can behave differently, anyways).

so lately on linux only, by having playstation controller support setting enabled, even if steam input is disable i can tell its there somehow because the light bar is purple, even if the virtual xbox controller that steam input creates is not there its still somehow on, its just no passing any inputs...

and that seems to be interfering in this game in particular because on windows i could have dualshock 4 prompt buttons if steam input was disabled, here its no possible at all because steam input is somehow interfering, and totally disabling playstation controller support simply makes it invisible to the game...

the linux native version of the game does have generic support for all playstation controllers but for the dualsense it enumerates its properties incorrectly and the motion sensors part keeps getting in the way and the only workaround i know is to disable the motion sensor part of the controller on a system level so the game doesn't enumerate it.

this could also be fixed if steam input was also able to expose the dualsense controller and its similar capabilities as a dualshock 4 instead of a generic xbox controller...