Remnant 2 (1282100)

[Equivocal90]

Compatibility Report

• Name of the game with compatibility issues: Remnant 2
• Steam AppID of the game: 1282100

System Information

• GPU: 6800 XT
• Video driver version: Mesa 23.1
• Kernel version: 6.3.11
• Link to full system information report as Gist:
• Proton version: Proton-GE 8-7

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-1282100.log

Symptoms

Game launches and shows a black screen for a few seconds and then exits.

Reproduction

Simply attempt to launch the game.

[DanMan]

Proton version: Proton-GE 8-7

You're in the wrong place for that. Only report problems with vanilla Proton here.

[zrooda]

Game loads at first, then crashes to desktop on the "Optimizing settings" screen. Afterwards it doesn't show anymore graphics and crashes after several seconds of black screen. Tried with Proton Experimental, Proton 8.0-3, Proton GE 8-7.

edit: Loads and works fine with Proton 7.0-6. Sometimes mouse clicking doesn't seem to interact with the UI elements, Alt-Tabbing makes it work. Performance is underwhelming, not even reaching 60 fps on 5800X3D & 6700 XT.

[Equivocal90]

Proton version: Proton-GE 8-7

You're in the wrong place for that. Only report problems with vanilla Proton here.

Sorry, forgot to mention that I also tried with vanilla Proton Experimental and got the same result.

[rainyaura]

I also have a 6800 XT, with driver Mesa 23.1.3.

Using Proton Experimental or Proton 8.0-3: The game briefly launches black, but crashes before the Title screen.

Using Proton 7.0-6: The game reaches title screen, and even character creation. However, Only my iGPU saw usage in the title screen, but while at character creation neither my iGPU nor discreet GPU saw any usage, resulting in frame rates below 1fps.

I tried multiple commands to use the discreet GPU instead of the iGPU, but these either had no effect, crashed before character select (where 3D first appears) or didn't launch at all.

[Eckoa]

You need to be on Mesa Git for it to work, i dont believe this is a proton issue specifically. Im running Flatpak Steam with latest Mesa git on proton 8.0-3 and the game works OOTB with an RX6800. I just booted the game right up the minute it was available.

Current spec

Processor Information: CPU Vendor: AuthenticAMD CPU Brand: AMD Ryzen 5 5600X 6-Core Processor

Operating System Version: Freedesktop.org SDK 22.08 (Flatpak runtime) (64 bit) Kernel Name: Linux Kernel Version: 6.3.12-200.fc38.x86_64 X Server Vendor: The X.Org Foundation X Server Release: 12201009 X Window Manager: KWin Steam Runtime Version: steam-runtime_0.20230606.51628

Video Card: Driver: AMD AMD Radeon RX 6800 (navi21, LLVM 15.0.7, DRM 3.52, 6.3.12-200.fc38.x86_64) Driver Version: 4.6 (Compatibility Profile) Mesa 23.3.0-devel (git-539bf3929b) OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 59 Hz VendorID: 0x1002 DeviceID: 0x73bf Revision Not Detected Number of Monitors: 2 Number of Logical Video Cards: 1 Primary Display Resolution: 2560 x 1440 Desktop Resolution: 2560 x 2520 Primary Display Size: 23.62" x 13.39" (27.13" diag), 60.0cm x 34.0cm (68.9cm diag) Primary VRAM: 16384 MB

[Cxpher]

Lots of graphical glitches with NVIDIA card. NVIDIA RTX 2080 Super here.

Transparent see through walls etc. Settings don't seem to fix that.

[d10sfan]

Game works on Proton 7 but not Exp for me, on 6700 xt

[xpander69]

Lots of graphical glitches with NVIDIA card. NVIDIA RTX 2080 Super here.

Transparent see through walls etc. Settings don't seem to fix that.

try with VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader %command%

seems to fix all the grass/leafs flickering

[aiudirog]

Replying to https://github.com/ValveSoftware/Proton/issues/6949#issuecomment-1646684299

I found the same thing - on my 6950XT, Proton 7 works with Mesa 23.1.3 but Proton 8 seems to require Mesa 21.2.0-rc1 or mesa-git.

From the log in the OP, it looks like a shader compilation error is causing the crash and I found some recent commits in Mesa referencing that shader extension (something about barycentrics? I don't know much about GPU programming). Maybe an older version of vkd3d had a polyfill/stub for that extension but it's been dropped in favor of a native implementation in Mesa that's isn't quite working right in the current release?

Edit: maybe this commit is where the problem started? https://github.com/HansKristian-Work/vkd3d-proton/commit/2f6a8b306f4ee8296ab4ec6f98a481d32aa9390d

[zrooda]

Only my iGPU saw usage in the title screen, but while at character creation neither my iGPU nor discreet GPU saw any usage, resulting in frame rates below 1fps.

Even though I have no iGPU, I have a tangentially related issue where the game sometimes launches only using ~40-60% of available dGPU power and only a restart fixes that. I would say it happens 4 out of 10 times I run the game and the result is obviously poor framerate (about half). That said I've seen this happen with other games (D4 recently), so it might be something with proton or mesa and not directly related to Remnant, but perhaps worth a mention. My original report stating low framerate is where I actually experienced this issue several times in a row.

[Matt-1-2-3]

I have the same issue as well AMD 6800xt. Proton 8 doesnt work. black screen at launch and then crashes. Proton 7 works just fine

[a3madkour]

I am getting a very different issues that I am not seeing reported on here or ProtonDB. Game launches a pop up that tells me that "DirectX 12 is not supported on your system. Try running without the -dx12 or -d3d12 command line argument" no matter what proton version I try. I tried using the -dx11 and -d3d11 command line arguments and I get another error that states "Unable to launch RHI'DirectX 11' since the project is not configured to support it. "

I am using relatively old hardware Here are the specs: abridged sanitized output of lshw -short /0/3c memory 32GiB System Memory /0/45 processor Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz /0/100/1/0 display GP102 [GeForce GTX 1080 Ti]

I am running arch,xorg and using the following version of the NVIDIA driver: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.86.05 Fri Jul 14 20:46:33 UTC 2023 GCC version: gcc version 13.1.1 20230714 (GCC)

[leaty]

@a3madkour Not sure how you got this issue on steam, but regardless this usually happens when the windows version is set too old, try bumping it in winecfg, I think 8 or higher is required in UE5. A more rare reason could be vkd3d not working properly but I doubt it.

[a3madkour]

@leaty thanks for the reply! I checked winecfg and it was set to windows 10, I bumped it to 11, and tried down to 8 and it still didn't work. I also tried installing the git version of vkd3d on the AUR and that did not resolve the issue. I have not had this issue with dx12 games in the past, Elden Ring worked fine for example, though I don't think I have tried a UE5 dx12 game before remnant 2.

[kisak-valve]

Hello @a3madkour, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

[a3madkour]

@kisak-valve thanks for the follow up! I attached the log file and here is the gist: gist: https://gist.github.com/a3madkour/a2797f0879afb119c4dbc98706aa9f56 steam-1282100.log

[kisak-valve]

Thanks, skimming over the Proton log, I'm not seeing where the game is having a hard time. Also, your system information looks healthy overall. Unfortunately, that means there's something more subtle going on and I don't have any suggestions to try as a quick fix.

[macktab]

Have somebody met issue with running on embedded graphics? I have added "DRI_PRIME=1 %command%" to launch options, but according to fps and nvtop output - it is still working on embedded instead of dedicated.

[E3FxGaming]

@a3madkour I've got the same problem with the same GPU (GTX 1080 Ti) too.

This problem also exists for a quite a lot of Windows users, there are multiple Steam Discussion threads about it, including a discussion about DirectX Agility, though opinions seem split about whether or not that's the root of the problem. I don't believe DirectX Agility affects us on Linux at all, considering there are Linux users playing the game just fine.

According to a Steam Discussion comment the devs said on the Discord server that they are looking into the problem, though I couldn't find that developer response on the Discord server.

On the remnantgame Discord server there are also people voicing their concerns about not being able to play because of this DirectX 12 problem. One person wrote they were able to play last weekend for 20 hours (during the early access phase), but can't play anymore because of the DirectX 12 error message, so maybe it's a problem introduced with the day 0 game update.

Edit: here is a developer blog post about DirectX 12 issues, though I really hope they address the problem with a game update, because those tips don't help at all on Linux.

[frozen-sea]

• GPU: 4070Ti
• Video driver version: 535.86.05
• Kernel version: 6.3.12
• Link to full system information report as Gist: here
• Proton version: 8.0-104

Some foliage flickers transparent and/or black. Also tested Proton GE 8-9 and Experimental bleeding-edge, no difference so recorded and logged on the default one. This bug is visible in the very first few seconds of starting a new game.

Lots of graphical glitches with NVIDIA card. NVIDIA RTX 2080 Super here. Transparent see through walls etc. Settings don't seem to fix that.

try with VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader %command%

seems to fix all the grass/leafs flickering

Can confirm this fixes, no obvious visual degradation on the foliage either. Might be causing some very sporadic large black flickers though, not sure since I couldn't reproduce those consistently.

video steam-1282100.log

[phunnyguy]

@E3FxGaming @a3madkour I'm getting the same DX12 error and I'm also using a GTX 1080 (non Ti however).

Also hoping the devs can come out with a patch for this soon. Seems that it's still affecting some Windows users despite them following the TSing article that the devs posted on their blog.

[macktab]

@phunnyguy I have resolved some dx12 error with setting 'DXVK_FILTER_DEVICE_NAME="AMD Radeon RX 5500M" %command%' . Got value for this from 'vulkaninfo|grep deviceName'

[phunnyguy]

@macktab Just tried that with DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce GTX 1080" %command% and no luck, still getting the same error.

[Kron4ek]

@phunnyguy try VKD3D_SHADER_MODEL=6_6 %command%.

[phunnyguy]

@Kron4ek God bless your beautiful soul, that got me in.

[a3madkour]

@E3FxGaming did @Kron4ek 's solution work for you? It did not for me unfortunately

[E3FxGaming]

@a3madkour The game actually starts for me with the launch arg from @Kron4ek .

My setup: i7-4770k (I know this is below min-spec, I'll get a new PC at some point) Asus Strix 1080 Ti OC Manjaro Linux XFCE (up-to-date)

GE-Proton-8-9 Nvidia driver: 535.54.03 Launch arg: VKD3D_SHADER_MODEL=6_6 %command%

[rainyaura]

@phunnyguy I have resolved some dx12 error with setting 'DXVK_FILTER_DEVICE_NAME="AMD Radeon RX 5500M" %command%' . Got value for this from 'vulkaninfo|grep deviceName'

This also solved my issue of the game using the iGPU instead of my discreet GPU! I wrote in "AMD Radeon RX 6800 XT" and suddenly had more than 0.5fps at character creation. Running on 7.0-6, also hosted some multiplayer too successfully.

Edit: closed the game and came back for some more multiplayer, but interestingly it's not working now. I did not even reboot.

Performance-wise, I think ultra settings is a bait. Game looks quite good on low, and performance gains at lower settings are substantial.

[leaty]

@leaty thanks for the reply! I checked winecfg and it was set to windows 10

@a3madkour Ah unlucky it wasn't as simple as that, sorry.

This problem also exists for a quite a lot of Windows users, there are multiple Steam Discussion threads about it, including a discussion about DirectX Agility

@E3FxGaming Thanks a lot for the info.

@phunnyguy try VKD3D_SHADER_MODEL=6_6 %command%.

@Kron4ek This makes me think the game (latest patch?) is just coded wrong at the moment, there is no way a GTX 1080 couldn't run DX12. The only other thing I could think of is using not up-to-date drivers (same for the Windows users who are also struggling), but it doesn't seem like that's the case. So, is there anyone with enough knowledge of VKD3D to know why VKD3D_SHADER_MODEL=6_6 is able to bypass this? I thought that was for much older gpu's. Any thoughts?

Also Just FYI, as far as I know VKD3D_SHADER_MODEL=6_6 can cause slowdowns in some cases, but it's better than nothing. Let's see what the Remnant devs come up with, hopefully the same solution works for you in the meantime @a3madkour.

Personally I'm having a blast on RX 6900 XT, runs perfectly besides some pretty bad optimization in some areas, hopefully they patch that.

[Kron4ek]

@leaty As far as i know, the problem is not in the game, vkd3d-proton does not expose shader model 6.6 by default on Pascal and older Nvidia GPUs for some reason. I don't know exactly why, perhaps some needed functions are not implemented for those GPUs in the videodriver. The same issue happens in The Last of Us.