Proton version: Proton-GE 8-7

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

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.

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.

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.

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

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

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

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

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

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

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.

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

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)

@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.

@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 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

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.

@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.

• 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

@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.

@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'

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

@phunnyguy try VKD3D_SHADER_MODEL=6_6 %command%.

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

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

@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%

@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 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.

@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.

Tried on both RX 6900XT and RX 7900XTX, crashes after a few seconds with Proton 8.0-3 unless using:

VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader

(proton log shows the "Attempting to use barycentrics in shader..." error when the extension isn't disabled)

Works without tweaks using Proton 7.0-6.
Mesa version 23.1.4
Kernel 6.4.4-200.fc38.x86_64

For what it's worth, performance is quite a bit worse than on windows.
ie. loading the save game and standing in the exact same spot on both, I get around 78+ fps in windows (w11), while only around 58fps in Proton. vsync/frame cap was disabled in both cases. Proton 7 is a few fps (2-3) faster than Proton 8.

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

You need to use mesa-git along with intel xess performance for upscaling as FSR seems to be pretty busted at least on linux. Proton 7 has worse performance than Proton 8 with mesa-git on my RX6800 by about 10fps. 1440p with XESS performance and shadows medium i get 90FPS

Replying to [#6949 (comment)](https://github.com/ValveSoftware/Proton/issues/6949#issuecomment-1653919509)

You need to use mesa-git along with intel xess performance for upscaling as FSR seems to be pretty busted at least on linux. Proton 7 has worse performance than Proton 8 with mesa-git on my RX6800 by about 10fps. 1440p with XESS performance and shadows medium i get 90FPS

Interesting!

For me FSR works pretty well on Proton 7 without mesa-git. Intel xess doesn't seem to make a big difference, for some reason. Mind if I ask what "pretty busted" means in this case?

Until two days ago, everything was working fine mostly, just a bit laggy sometimes, but now im constantly getting this crash whenever i start remnant, proton version doesnt seem to matter:

I am on arch linux with mesa-git, nvidia RTX 2080 on the latest non git drivers

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

in this case its usually 10-15FPS below XESS and excessive ghosting and temporal (i think thats the proper term?) issues with the image which isnt present on XESS.

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

It seems like this line here is the one failing https://github.com/ValveSoftware/wine/blob/proton_8.0/dlls/winevulkan/loader.c#L664

Tried on both RX 6900XT and RX 7900XTX, crashes after a few seconds with Proton 8.0-3 unless using:

VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader

(proton log shows the "Attempting to use barycentrics in shader..." error when the extension isn't disabled)

Works without tweaks using Proton 7.0-6. Mesa version 23.1.4 Kernel 6.4.4-200.fc38.x86_64

The vkd3d-proton issue tracker is the best place for any issues that are "better" on Proton 7.0-6 and need a vkd3d-proton variable on 8.0-x :). https://github.com/HansKristian-Work/vkd3d-proton.

@a3madkour I had the same problem with Diablo 4 a couple of months back (not being able to load DX12), also due to the Agility SDK. I was able to track that down to vkd3d having split up the DX12 DLL in two in a recent release, in order to better match Microsoft's DX12 binary setup. Lutris then didn't sort that out when my wine prefix was updated, so I didn't have both the necessary DLLs in my prefix. Only one of them.

But in my case I was using Lutris, not Steam. Not sure if there's some way you could have run into the same thing. But if the vkd3d version in use is new enough there should be both a d3d12.dll and d3d12core.dll file in the windows/system32 dir in the game's wine prefix.

As for how you find out if the vkd3d version is new enough to need it... :shrug: It seems vkd3d in steam's Proton 7.0-6 release (what I'm using) isn't new enough to contain d3d12core.dll, but it looks like it is in Proton 8.0-3?

Hi, I'm also having the same issue with Remnant 2. Proton 7.0-6 works without any tweaks besides some stutters when friends pick up items while in my world (this is a game issue, happens across platforms and even the first game). Proton experimental, 8.0-3 and GE 9 / 11 cant boot the game without setting the environmental variable VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader. In addition using anything newer than proton 7.0-6 leads to worse performance when compared to the latter, especially in some areas where the frame times can start to jump around quite heavily.

I'm running a 6900xt paired with a 5800x3d on fedora 38 workstation. My current kernel version is 6.4.6 and mesa and mesa 23.1. Steam has been installed through the package manager. The issues still persist with the latest updates for the games.

As a side note, XeSS seems to suffer from extreme ghosting on small particles when compared to FSR, which also has some ghosting but not nearly to the same extend. This doesnt seem to be the case on windows, so I dont know if its an issue with the implementation of linux or something related to this issue.

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

Experimental and 8.0 implement mesh shader support in vkd3d which requires the latest mesa in order for it to work. If you run mesa-git you wont require the mesh shaders be disabled. If you are against using git then obviously you have to use the workaround.

In regards to FSR This is the exact polar opposite of my experience with FSR ghosting so bad i can see the after images constantly on large and small objects along with shimmering on wet surfaces. Do you have a certain set of launch options that might cause FSR to not do this? I can only get a combination of acceptable image and performance with XESS which seems to mirror testing from others with Remnant along with XESS providing a more stable image overall which Digital Foundry also found. Im curious as you how you get a good image out of FSR when FSR seems to be provably worse than DLSS and XESS in this specific title and if there is a way to replicate your results.

Replying to [#6949 (comment)](https://github.com/ValveSoftware/Proton/issues/6949#issuecomment-1667320473)

Experimental and 8.0 implement mesh shader support in vkd3d which requires the latest mesa in order for it to work. If you run mesa-git you wont require the mesh shaders be disabled. If you are against using git then obviously you have to use the workaround.

Latest mesa + proton8 does indeed work without issues on RX7900XTX.
I do need to disable the steam overlay to avoid issues.

The latest game patch also improved performance, but at least on my setup, proton7 still performs better than proton8 on this title and both much worse than windows.

Also have something weird with this title, but if I compile proton myself, for some reason the game doesnt load/save it's save games. It starts as if I have no savegame and even if I go through creating a new one, then exit and restart, it doesn't save at all. Very strange, no idea why that happens as when I grab a release of proton GE, it works fine, or any of the official proton releases also work fine. Prevents me from trying to pinpoint where the performance loss between the proton releases happened.

Tried to compare proton logs, but there is no indication as to why it happens. Even tracing file opens with bpftrace, shows it's not even trying to open/save the savegame, probably something somewhere that fails. Even tried to compile proton on a different distro, but same issue. Tried both Fedora 38 and Ubuntu 22.04, but since the compile happens in a podman environment, it should be using the same tooling anyway.

replying to https://github.com/ValveSoftware/Proton/issues/6949#issuecomment-1670421228

Thanks for the info, I might give mesa git a try. Hows performance? Proton 7.0-6 + mesa 23.1 lacks a bit when it comes to performance.

When it comes to FSR vs XeSS, my main gripe are small particles floating around on screen. with XeSS I see huge ghosting trails, which arent nearly as bad on FSR. I find it so distracting that I cant really focus on anything else. I might give it a second try and maybe record the scenes using FSR and XeSS. Of course though youtube might kill the quality.

replying to https://github.com/ValveSoftware/Proton/issues/6949#issuecomment-1670421228

I'm now on mesa 23.1-5 on nobara, which runs mesa git. The game boots and I'm able to select my character. But when I load the world the game crahes, which also now takes desktop environment with it. Disabling the extension allows me to load into the game without any issues.

I cant say if this is a vkd3d issue or a mesa issue. I've seen others report the same crashes while using mesa git paired with a 6000 series AMD GPU.

replying https://github.com/ValveSoftware/Proton/issues/6949#issuecomment-1670746322

What version of mesa are you running, do you build mesa git yourself?

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

I use flatpak steam with proton experimental so whatever the current git flatpak provides which at this time is

Driver Version: 4.6 (Compatibility Profile) Mesa 23.3.0-devel (git-f17c5297d7)

I have found though that VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader provides a 5-15fps performance increase as i got curious if disabling mesh shaders had any effect on Nanite used in this title. My Ryzen5600x & RX6800 is able to push 80-120fps depending on the scene with this setup. Disabling Mesh shaders increased Performance in the Asylum by 15FPS and about 5FPS in Ward13.

Mesa-git with Proton Experimental on Flatpak Steam
Launch options :VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader OBS_VKCAPTURE=1 PULSE_LATENCY_MSEC=30 %command%
In Game Settings @ 1440p:
Upscaler : Xess Performance (faster GPU should be fine with balanced if 1440p or less, i stay above 60 with balanced but my target is 80+fps)
Shadow Quality : Medium
Post Processing: High
Foliage: High
Effects: Medium
View Distance: High
Detailed Shadows: Off

You can sharpen up the output with VKBasalt and a CAS shader at 0.1-0.2 strength which should give a pretty pleasing image overall (at least as pleasing as upscaling can be). On a side note after testing it Remnant 1 actually has the exact same performance characteristics as Remnant 2 (same team so makes sense). Shadows and Effects Quality will drastically lower your FPS while Post P, Foliage, and View Distance have almost no effect (except when moving from high->ultra). Those 2 settings (along with resolution/upscaling) should be the primary focus for increasing performance and hopefully they will add an option to deal with the performance hit mesh shaders seem to incur also.

EDIT: Testing further I was able to gain a further 5-10FPS with adding these options RADV_PERFTEST=cswave32,dccmsaa,gewave32,pswave32,ngg_streamout but YMMV. This pushed me to 90-100FPS in the Asylum with the above settings vs 55-80FPS without disabling mesh shaders and adding radv perftest options. Keep in mind this is just my current testing to push performance in remnant 2 and is not the necessarily universal. Ill also say dont try forcing VRS, it absolutely destroys shadows and doesnt add any FPS. If you wish to test FPS the most demanding locations i have found are the Asylum in Losom, Ward13, and many indoors/dungeons locations on N'Erud

After updating to the new kernel version and nvidia driver version (non beta), i keep getting the error "out of video memory"

I'm still getting occasional crashes on RTX 4090 driver version 535.86.05 on latest proton experimental. Graphics settings maxed on 1440p with VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader to eliminate flickering.

Not seeing too much in the log that seems like it could have to do with the crash, though I do see rare occurrences of

147181.649:0100:0110:fixme:oleacc:find_class_data unhandled window class: L"[#32769](/issue/ValveSoftware/Proton/32769)"

and

Fossilize WARN: Pipeline library handle 0x00007f126940f780 is not registered.
It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).

Works fine otherwise. Crashes are rare but game is still more-or-less unplayable because it's a bit too easy to lose a lot of progress.

Update

Played latest patch for some hours, did not experience a single crash so far (switched using both DLSS and AMD FSR).

Hi, have the same issue as @ExpandingMan (I'm using a 4090 with 535.86.05, disabled the mesh shader extension).
The game technically doesn't crash, but its threads go into an infinite loop and gets stuck.
Some extract from the logs:

ema@scv:~$ tail -40 steam-1282100.log 
200.945:0140:01a0:warn:vkd3d-proton:rs_desc_from_d3d12: Ignoring MultisampleEnable 0x1.
200.945:0140:0178:fixme:vkd3d-proton:vk_samples_from_dxgi_sample_desc: Unhandled sample count 0.
200.945:0140:0178:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: DSV format is DXGI_FORMAT_UNKNOWN.
200.945:0140:0178:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Unused input element 4.
200.945:0140:0178:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Unused input element 5.
200.945:0140:0178:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Unused input element 6.
200.945:0140:0178:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Unused input element 12.
200.945:0140:0178:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Unused input element 13.
200.945:0140:0178:warn:vkd3d-proton:rs_desc_from_d3d12: Ignoring MultisampleEnable 0x1.
Fossilize WARN: Pipeline library handle 0x00007f550da5f690 is not registered.
It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).
Fossilize WARN: Pipeline library handle 0x00007f54f55e5e90 is not registered.
It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).
200.965:0140:01b0:fixme:vkd3d-proton:vk_samples_from_dxgi_sample_desc: Unhandled sample count 0.
200.965:0140:01b0:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: DSV format is DXGI_FORMAT_UNKNOWN.
200.965:0140:01b0:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Unused input element 4.
200.965:0140:01b0:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Unused input element 5.
200.965:0140:01b0:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Unused input element 6.
200.965:0140:01b0:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Unused input element 12.
200.965:0140:01b0:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Unused input element 13.
200.965:0140:01b0:warn:vkd3d-proton:rs_desc_from_d3d12: Ignoring MultisampleEnable 0x1.
Fossilize WARN: Pipeline library handle 0x00007f551d5eed70 is not registered.
It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).
204.390:0140:02b8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
220.828:0110:0120:fixme:oleacc:find_class_data unhandled window class: L"[#32769](/issue/ValveSoftware/Proton/32769)"
220.828:0110:0120:fixme:uiautomation:uia_get_providers_for_hwnd Override provider callback currently unimplemented.
220.828:0110:0120:fixme:uiautomation:msaa_provider_GetPropertyValue Unimplemented propertyId 30024
220.829:0110:0120:fixme:uiautomation:uia_element_GetCurrentPropertyValueEx Default property values currently unimplemented
220.829:0110:0120:fixme:uiautomation:uia_element_GetCurrentPropertyValueEx Default property values currently unimplemented
220.829:0110:0120:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
220.829:0110:0120:fixme:uiautomation:nc_provider_GetPatternProvider 00000000004A7D30, 10002, 0000000001B2EC90: stub
220.829:0110:0120:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 00000000004A7CA0, 10002, 0000000001B2EC90: stub
229.689:0134:0138:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 0000000000B9FE80
229.690:00e8:03e4:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
230.178:0030:03e8:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
230.179:0030:03ec:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
230.179:0030:03f0:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
230.179:0030:03f8:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
230.179:0030:03f4:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
pid 8437 != 8436, skipping destruction (fork without exec?)

I think this

Fossilize WARN: Pipeline library handle 0x00007f551d5eed70 is not registered.
It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).
204.390:0140:02b8:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.

Is the main issue.

As he mentioned the game works fine 99% of the time, but when it gets stuck you lose your progress; as a suggestion, rest to checkpoints often, this will minimize the amount of time lost.

Anyhow, there's a brand new patch - will test and report back.

After the latest hotfixes, im experiencing very strong lags when bosses do stuff like lasers

@Emanem Definitely off-topic for this thread, but I don't have a better place to communicate this to you right now (@kisak-valve feel free to mark as off-topic :). Hotfix is the branch we use for one-off builds to fix a specific game instead of doing an emergency experimental release. It only gets updated when we have a new game that needs it, so it can get quite stale when there are no "emergencies".

@Emanem Definitely off-topic for this thread, but I don't have a better place to communicate this to you right now (@kisak-valve feel free to mark as off-topic :). Hotfix is the branch we use for one-off builds to fix a specific game instead of doing an emergency experimental release. It only gets updated when we have a new game that needs it, so it can get quite stale when there are no "emergencies".

Cool, have done it, so far I had no crashes for a good 45 mins session. Shall I enable mesh shaders or not?

Hi, unfortunately another crash with Experimental. Here the proton log - let me know if you need more info.

On my RX 6950 XT the game is rock solid with Proton 7.

My wife has, however, experienced some crashing on her Vega 56. Installing the "Tasty Potato" mod seems to have remedied it. Might be worth giving it a go, if you are desperate

On my RX 6950 XT the game is rock solid with Proton 7.

My wife has, however, experienced some crashing on her Vega 56. Installing the "Tasty Potato" mod seems to have remedied it. Might be worth giving it a go, if you are desperate

Proton 7 seems to be for me as well - is just I would like to use DLSS instead of FSR for upscaling and that is only available with Proton 8+ AFAIK.

Minor update: I tried many different versions of Proton (from 7, to 8 to Experimental to GE 8.11) and all were crashing sooner or later (this location was a crashfest no matter which version of Proton I was using).
Since the latest update of the game I don't wasn't getting a log error pre-crash, but mostly warnings.

I then removed the constraint VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader and lo and behold the game now seems much more stable and seems working fine (Experimental and 8) - no crashes as of yet.
Of course, this is not great performance wise because it seems that some other contention is present and the GPU (4090) doesn't get fed enough work, hence the FPS drops from a stable V-Sync'ed 75 to sometimes 50; again, this seems to be due to some locking/wait mechanism.

7 hasn't crashed for me yet after a few hours, but indeed in my experience this has been one of the most problematic games I've ever tested, whatever is happening is very intermittent and seems to change in unpredictable ways based on options and which proton version is used. It doesn't even seem to always get stuck on the same warnings in the log.

I have the same issue with both games

My

$ glxinfo | grep "OpenGL version"
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.1.0-devel

I am in Rx6750 XT, i try reinstall all my AMD drivers and mesa too according to the lutris Docs, but it dont work me. How can i upgrade to Mesa 23.3 not 1 ? Should i try it for dx12 ?

Other games like PathOfExile with DX12 Enabled works nice for me, but Insurgency and Remnat 2 dont work
I also try many enviroments variables like VKD3D_DISABLE_EXTENSIONS=VK_EXT_mesh_shader, but nothing works.

I am in ubuntu studio LTSC 22.04 with Cinnamon Desktop
Help me please

PD: my kernel version is

$ uname -r
6.2.0-1009-lowlatency

Could be it the problem?

For anyone who experienced random GPU hangs while playing Remnant 2, try switching to Experimental bleeding edge, a fix for a scary bug arrived less than 24 hours ago and that bug is the most probable cause of hangs I had myself (according to logs made with breadcrumbs enabled).

For anyone who experienced random GPU hangs while playing Remnant 2, try switching to Experimental bleeding edge, a fix for a scary bug arrived less than 24 hours ago and that bug is the most probable cause of hangs I had myself (according to logs made with breadcrumbs enabled).

Seems like since this fix I experienced no crashes/hangs!

For anyone who experienced random GPU hangs while playing Remnant 2, try switching to Experimental bleeding edge, a fix for a scary bug arrived less than 24 hours ago and that bug is the most probable cause of hangs I had myself (according to logs made with breadcrumbs enabled).

This is now live on the main Proton Experimental branch - no more need to use bleeding-edge :)

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

I've found a solution for this problem and writed a guide:
https://github.com/Milor123/Remnat-2-FIX-Dx12-Linux

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

Thanks, this works, altho gives performance hit.

I'm guessing NVIDIA driver issue and still not fixed? https://github.com/HansKristian-Work/vkd3d-proton/issues/1664

Edit: Seems to be fixed in experimental bleeding edge now:)

Seems like FSR 3 Frame Generation isnt working in this title. Toggling it on does nothing from what i can tell either good or bad.

Arch Linux
Plasma 6
Mesa 24.0.2
Kernel 6.6.20-1-lts
Latest Proton-Experimental

So upon further testing it does actually work, You have to

1. Enable Vsync
2. Set framerate limit to 1/2 your refresh rate
3. Enable FSR 3 at Quality Mode or lower
4. Do not toggle on FSR 3 Frame Generation but leave it "toggled off"

This will enable frame generation for some reason by having it "off" and running the game at 1/2 refresh rate. Changing to Native AA for FSR or toggling frame gen "on" makes it turn off and setting the FPS to your refresh rate or disabling vsync turns it off also

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

I wonder if this is related to FSR3 frame gen seaming to be default enabled when it shouldnt be? What are your current graphics settings?

Frame Generation disables/interferes with the epic overlay and this is a known issue with the game on Windows also.

https://github.com/ValveSoftware/Proton/issues/6949#issuecomment-1986255498

This game don't install EOS by default and manually install EGL don't seem to work.

One way to enable the overlay is to install it via legendary (using the version ship with heroic in my case.)

Try install the overlay with

legendary eos-overlay install --path [path to eos overlay] --prefix [path to steam compatdata]/1282100/pfx

the default eos overlay path for heroic is $HOME/.config/heroic/tools/eos_overlay

I can also confirm that crossplay is working (pc and xbox series s )

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

This worked! Thank you so much for the tip!

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

even though you can see the framerate doubling by doing this, it isn't actually working, it doesn't look smooth as it should (it does on windows) you can also tell its not working because the crosshair should flicker a little bit when FG is actually working (as seen when running with FG turn on on windows)

Replying to [#6949 (comment)](https://github.com/ValveSoftware/Proton/issues/6949#issuecomment-1975815359)

even though you can see the framerate doubling by doing this, it isn't actually working, it doesn't look smooth as it should (it does on windows) you can also tell its not working because the crosshair should flicker a little bit when FG is actually working (as seen when running with FG turn on on windows)

On my end its very much smoother than when i have it toggled "on" or when running FSR3 with the frame limiter set to my screen refresh rate.

When toggled "on" or set to my screen refresh rate the game gets stuck to a stuttery 75-83fps (only when using FSR3). When setup as i described above it similar to when i use XESS on performance or balanced which i get 110-120FPS with XESS. I had a friend verify with their 6600xt (without telling them the expected outcome) and got a similar result on their end though with a lower total FPS as their refresh rate is 75hz.

Something is definitely not working as expected, exactly what i cant be sure but at the very least when running it the way i describe above things act very bizarre with the FPS counter in steam and manghud along with seeing artifacts that are in line with what FSR3 should be producing :shrug:

EDIT: Just to add After testing the latest Game Patch + Proton EXP the toggle for FG now seems to work as expected, toggling it off with FSR 3 Balanced gets ~96 FPS (as is expected and what i got with FSR2) and toggling it on gets 160-180 FPS in Ward 13. Vsync and frame limiter also dont appear to cause problems anymore.

I noticed the same thing as @Hadrianneue - FPS said 120 but it felt significantly choppier than 60 when testing the "disable frame generation to make it work". This was on both Experimental and the latest GE-Proton at the time you originally reported it.

However, I can also confirm that Proton Experimental seems to make the whole system work properly! It does break/disable VRR, but as long as you can stay above your monitor's refresh rate Vsync seems to do the job quite well and I haven't noticed any stuttering in the 15 minutes or so I tested it in Ward 13 and Yaesha.

I got the Epic Social Overlay working the flatpak version of steam. Here are the steps I used:

1. Download heroic launcher and install the EOS Overlay from the advanced settings page:
   
2. Install legendary: python3 -m pip install --upgrade legendary-gl
3. Give the steam flatpak permission to access the eos_overlay directory ~/.config/heroic/tools/eos_overlay or ~/.var/app/com.heroicgameslauncher.hgl/config/heroic/tools/eos_overlay if heroic launcher is flatpaked. (you can use flatseal for this)
4. Install EOS Overlay to the game prefix: legendary eos-overlay install --path ~/.var/app/com.heroicgameslauncher.hgl/config/heroic/tools/eos_overlay --prefix {your Steam library}/steamapps/compatdata/1282100/pfx
5. Make sure frame generation is disabled in game or it wont display.