This game seems to suffer with the same issues as RE2, RE3, RE Village, mostly all RE games with the new engine on an NVIDIA GPU where the shaders after a while would just corrupt and the game would lockup. Just like in my RE3 report I was able to get a log.

Operating System: EndeavourOS
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-273-tkg-bore (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31,3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2

steam-2050650.log

Game turned green, lots of models despawned and I crashed when I died. Using an NVIDIA GPU.

EDIT: Setting game to 30FPS fixes every issue I had.

Log attached below:
steam-2050650.log

It does work great for me without any flaws, but only when i limit the fps to 30. More than 30 fps leads to texture problems and invisible objects in the intro + crashes.

OS: EndeavourOS
X11
Kernel: 6.1.21-1-lts
GTX 1080 ti
32 gig ram

I was experiencing the same, but removing mangohud from the launch options completely fixed the startup crash for me. No idea why

@alex9k1 what mangohud version are you using?

@alex9k1 what mangohud version are you using?

0.6.8

0.6.8-5 to be precise: https://aur.archlinux.org/packages/mangohud

Welp, game is starting to hard lockup/freeze a lot starting on chapter 4

The game crashes to desktop constantly for me (every few minutes, and often when starting/loading a game). Tried disabling Steam overlay and Mangohud, with no luck.

steam-2050650.log

Here's the Proton log. My specs are:

mesa-git 23.1.0_devel.168578.79ac6197a99.932463d268438ce945b21718552d92ab-1
Proton Experimental [bleeding edge]

OS: EndeavourOS
Kernel: 6.2.8-zen1-1-zen
CPU: AMD Ryzen 9 7950X
GPU: AMD Radeon RX 7900 XTX
Memory: 64029MiB DDR5-6400
DE: Plasma 5.27.3 Wayland

If I can provide any further info, please let me know.

Game freezes at seemingly random points seconds into the new game intro cutscene up to a few minutes into Chapter 1.

Some models flicker, mostly the car in Chapter 1 intro, models get 'stuck' to others, models stretching.
Texture issues, have seen a dark patch on Leon's chin throughout the intro cutscene and persist into Chapter 1 gameplay. I have also seen 'see-through' squares on the ground in a puddle before reaching the house at the start of Chapter 1.

The model & texture problems are much less consistent, most often they are minor or there are none noticeable.

The game crashes to desktop before the splash screens if loaded with mangohud (currently using 0.6.8-5 from AUR).

Tried with Proton Experimental [bleeding edge], Proton-GE 7.53 & Proton-GE 7.51

OS: Arch Linux x86_64
Kernel: 6.2.8-zen1-1-zen
DE: Plasma 5.27.3
WM: KWin
CPU: Intel i9-9900K @ 3.60GHz
GPU: NVIDIA GeForce RTX 2080 SUPER
Memory: 32GB DDR4

Proton Log - started a new game, it froze a few seconds into the first cutscene (the ritual):
steam-2050650.log

I'm running into this graphical issue. I've tried all different types of proton. The proton that works best is GE 53. it's the only one that allows cut scenes to play normally. Otherwise it's just white static. The game is very playable aside from this very annoying graphical error. I've tried various launch options as well. No luck. The error is abscent when talking to the merchant and when in small dark areas such as caves and tunnels.
My rig:
Nobara OS
Ryzen 5 5600x
Radeon 6700xt

@TathagataDM
@AlmightyLaxz

Have you tried to set the fps to 30 (through ingame setting!) ?
You will be surprised how well it works, other graphic setting will do nothing in comparison. I am sure this is the bugfix you need till this problem gets resolved.

I have tested the game on my secondary PC by now with a Ryzen 7 4750G and a Radeon 6600XT (Mesa 23.0) and I have the exact same issues there as I mentioned initially.

Tried to edit the local_config.ini to change windows mode and resolution and uh ... that didn't exactly help :smile:

https://user-images.githubusercontent.com/46139159/227723889-5a2515bf-cb3d-48bf-b1d2-f839f820562a.mp4

Ok, not sure what did the trick, but I managed to fix my issues. I did:

use GE-Proton7-53
- edit the local_config.ini in the gamefolder (uploaded as .txt otherwise GitHub wouldn't let me upload):
local_config.txt
- use gamescope
- use gamemode
- disabled MangoHud via environment variable (I have set MANGOHUD=1 in /etc/environment) and then ran the game via the mongohud application. In the end, my launch command in Steam looks like this now:
MANGOHUD=0 gamescope -h 1080 -H 1080 -r 60 -- gamemoderun mangohud %command%

Now the game is running fine and I can even edit options. Mangohud also behaves nicely. And the game doesn't even freeze anymore when trying to exit. With Proton Experimental the performance is still abysmal and needs a lot more RAM. Using GE-Proton7-53 alone however doesn't seem to fix it. I have a feeling it's the gamescope + ge-proton combo, but don't really tinker around much more since the game eventually locks me out for a day if I start it too often. I guess that's Denuvo?

So I actually tried different things and it turned out, gamemode is the single thing, which makes the big change. Thanks to @flightlessmango I decided to dig a little depeeper. I totally forgot, that I had set GAMEMODERUNEXEC="env DRI_PRIME=0 DXVK_FILTER_DEVICE_NAME=6600 VKD3D_FILTER_DEVICE_NAME=6600" globally. After a bit of tinkering, it turns out, DXVK_FILTER_DEVICE_NAME=6600 did the trick, even without gamemode. Quite interesting, considering it's a D3D12 game and using VKD3D.

@alex9k1 can you test if gamescope is a necessary component?

@alex9k1 can you test if gamescope is a necessary component?

Checked it. Apparently gamescope doesn't make a difference. Still works fine without it.

@alex9k1 and mangohud is not acting weird?

Nope, still running it with MANGOHUD=0 gamemoderun mangohud %command% though

MANGOHUD=0 shouldn't do anything in this case as the mangohud scripts sets MANGOHUD=1 again

@alex9k1 are you sure didn't change anything else?
I'm still running into the same issue with those changes

@alex9k1 are you sure didn't change anything else? I'm still running into the same issue with those changes

You are right. I updated my comment regarding the fix. TL;DR it wasn't gamemode, it was DXVK_FILTER_DEVICE_NAME=6600

Haven't checked other Proton variants tho

Steam system information in a gist here.

Crashes on Chapter 5 repeatedly within a few minutes. Here is the Proton log attached. Briefly glancing at it, complains about vkd3d-proton pipeline.

steam-2050650.log

Popping in to say @alex9k1's solution just fixed my problems & I can now change the settings in the menu. (haven't actually played yet so idk about stability)
my launch options are as follows:

running NixOS proton GE 7-53
GAMEMODERUNEXEC="env DRI_PRIME=0 DXVK_FILTER_DEVICE_NAME=6800 VKD3D_FILTER_DEVICE_NAME=6800" gamescope -W 2560 -H 1440 -r 165 -o 165 -f -- gamemoderun %command%
Change 6600/6800 to your GPU model, this is obviously AMD and no idea about nvidia.

Popping in to say @alex9k1's solution just fixed my problems & I can now change the settings in the menu. (haven't actually played yet so idk about stability) my launch options are as follows:

running NixOS proton GE 7-53 GAMEMODERUNEXEC="env DRI_PRIME=0 DXVK_FILTER_DEVICE_NAME=6800 VKD3D_FILTER_DEVICE_NAME=6800" gamescope -W 2560 -H 1440 -r 165 -o 165 -f -- gamemoderun %command% Change 6600/6800 to your GPU model, this is obviously AMD and no idea about nvidia.

Glad I could help, but DXVK_FILTER_DEVICE_NAME=6800 %command% should be sufficient

Unfortunately no such luck on my end, still crashing with all of the above workarounds. What kind of ingame settings are others using? I wonder if one of those might be causing an issue. I'm set to 4K, variable framerate, borderless, everything maxed except motion blur and lens distortion off.

Also tried lowering framerate to 60, using vsync, using fullscreen mode, using FSR2 Quality, lowering the AO from CACAO to SSAO. Seems to crash no matter what.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1483974617

Can you report back if you also have the problem when you limit your fps to 30 without vsync? It's the only option that solved the crashing problem for me.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1484027836

So there still isn't way to run this game without capping it to 30 ?

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1484029251

Seems so. At least for me.

Edit: I eventually just did a clean install of Nobara and it works fine now, at least into the first two chapters.

The chainsaw demo worked perfectly for me with no tinkering so I thought I'd be good to go when the full game came out. Since launch I can not get above 20 FPS. Even when setting resolution to 320x200. GPU usage is always low. I've tried default proton, proton experimental, and GE-Proton-53. All my other games seem to be running fine. I can't install the chainsaw demo anymore to test that, the install button on the store just does nothing for me and it's not in my library. The game works completely fine if I boot over to windows. I've also tried reinstalling the game and deleting the compatdata folder for the game.

I tried some of the launch options posted here but no success. My gpu is a 6900xt.

@Famf did you install amdvlk? Can you post the output of vulkaninfo | grep driver?

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

I went ahead and tried 30 and still no luck, crashes anyway.

To those experiencing model and lighting glitches until the game eventually freezes on NVIDIA GPUs,

Try disabling subsurface scattering in the settings. This seemingly eliminated all the freezes I had.

To those experiencing model and lighting glitches until the game eventually freezes on NVIDIA GPUs,

Try disabling subsurface scattering in the settings. This seemingly eliminated all the freezes I had.

This allowed me to get past where it locked up at the same spot every time in Chapter 5. Till just about the end of the chapter and I hit another freeze.

I am getting seemingly random hangs with 7900XTX, nothing shows up in dmesg, not sure it's a gpu hang.

Sometimes I can play for hours, and other times a few minutes.
Tried proton stable, experimental, experimental bleeding edge.
With and without mangohud.
It eventually locks up my whole system.

sysinfo
steam-2050650.zip

@Famf did you install amdvlk? Can you post the output of vulkaninfo | grep driver?

I'm using nobara and I do not remember specifically installing amdvlk at any point.
Here's that output:
vulkaninfo | grep driver
driverVersion = 23.0.99 (96469091)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 23.1.0-devel
driverUUID = 414d442d-4d45-5341-2d44-525600000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 23.1.0-devel
VK_KHR_driver_properties : extension revision 1
driverVersion = 0.0.1 (1)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 23.1.0-devel (LLVM 15.0.7)
driverUUID = 6c6c766d-7069-7065-5555-494400000000
driverUUID = 6c6c766d-7069-7065-5555-494400000000
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 23.1.0-devel (LLVM 15.0.7)
VK_KHR_driver_properties : extension revision 1

I've tried disabling subsurface scattering but am still freezing not long after loading into chapter 1.
Still getting graphics artifacts, sometimes I see model stretching, pink bushes, disappearing models get progressively worse until the game freezes. Usually it just freezes after standing around for some time at the start.

I also tried reducing texture quality from High (2GB) to High (1GB) and High (0.5GB) - adjusting without a restart creates texture problems, Leon's jacket most frequently. 1GB appears to create obvious flickering (between texture quality) problems on some textures.

Game is currently unplayable. I'll wait for a fix rather than trying to play like it's a PowerPoint presentation (locking to 30 FPS) :P

Below is a frequent issue, a hole in poor Leon's face.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1483883543

Doesn't work for me to make it change the settings with my NVIDIA RTX 3080. I tried both the environment variables DXVK_FILTER_DEVICE_NAME=3080 VKD3D_FILTER_DEVICE_NAME=3080 and it didn't help.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1487301890

This workaround only works on AMD gpus.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1488121751

I originally came here from Reddit where a guy said he used NVIDIA and this fix worked for him.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1488140729

With NVIDIA GPU I have my launch options as:

DXVK_FILTER_DEVICE_NAME=NVIDIA VKD3D_FILTER_DEVICE_NAME=NVIDIA %command%

Currently just starting Chapter 5 and the game works pretty well so far for me, hope it could help.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1488161709

Can you change the settings?

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1488167173

Yeah, I wasn't able to change the settings before until I added the launch options.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1488175283

Weird, doesn't work for me either.

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

With NVIDIA GPU I have my launch options as:

DXVK_FILTER_DEVICE_NAME=NVIDIA VKD3D_FILTER_DEVICE_NAME=NVIDIA %command%

Currently just starting Chapter 5 and the game works pretty well so far for me, hope it could help.
Fore me everything went fine until the cabin fight, its there where the game got hard frozen 6/10 times. Intially it begins with a bright white flare and then texture disappears.

@ions98 Excuse me, what's in that reference? Did you accidentally not send the text and sent just the quote instead?

Where do you get you GPU name? i just bought an 6950RX today but entering "6950" as name doesnt work i'm getting the error "DX12-compatible DXGI adapter not found"

Quick update for the nvidia guys, while this fix is not ideal for monitors with high refresh rate, if you cap the game to 60fps it will work fine. This seems to be an nvidia driver bug which I reported to them as well(it also affects AC Valhalla): https://forums.developer.nvidia.com/t/nvidia-driver-bug-causes-vkd3d-resident-evil-ac-valhalla-to-corrupt-shaders-crash/248365

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1492436697

I have to cap it to 30 fps to work. I have a 60hz monitor and if I let it stay in 60 fps, it will run for few minutes before getting a hard freeze.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1493208956

Please add in the bug report as this only affects NVIDIA and I am unable to reproduce such problems on AMD hardware, no need to spam here as it isn't proton/vkd3d related.

EDIT: I only left it as a useful information for those that want to play the game under linux and use NVIDIA gpu.

I set it to that with the launch options and it seemed to have fixed everything except it is only taking up a 10th of my screen. Does anyone have any suggestions?

Gist

Launching with DXVK_FILTER_DEVICE_NAME=6800 %command%

I'm having trouble with constant random freezing of this title on my Steam Deck. At random points it will freeze, go to a black screen, come back (but frozen with audio still playing), and then it restarts my system. Currently running it with ProtonGE-53, but have also tried the latest Proton for the Deck.

I'm having this issue with all RE Engine titles as well.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1483737602

for anyone coming across this thread and has this same issue, updating my steam flatpak fixed it.

Wanted to confirm setting DXVK_FILTER_DEVICE_NAME worked for me as well. I had to change the value after the equal sign to match my card.

On Ubuntu 22.04 with a AMD Radeon RX 6900 XT GPU and with the non-snap version of Steam, I needed to use the kisak-mesa PPA to get rid of the artifacts shown in this comment.

After adding DXVK_FILTER_DEVICE_NAME=7900 %command% got error that DX12-compatible DXGI adapter not found.

Proton log: steam-2050650.log
System info: https://gist.github.com/NTMan/33cca4906328793206218192820779ec

Upd: Radeon 7900XTX users should used DXVK_FILTER_DEVICE_NAME=GFX1100 %command%

Proton log: steam-2050650 (truncated).log
System info: https://gist.github.com/reboot-mk/b691008a4e6d1f4b7b272423a1ac49c5

Game doesn't run well for me. No matter which graphic settings I use, the game runs at around 30fps and feels really slow. It works fine on Windows, and for what it's worth, Resident Evil Village worked fine.
I truncated my proton log because the same lines would get repeated over and over again, and the log file would be like 300MB

Is there going to be a fix for the separate ways dlc crashing on steam deck?

Separate Ways also crashing 100% of the time on the second cinematic of the game, when some doors are being opened. Steam already has downloaded Proton Hotfix for the game by itself.

System Information

• GPU: RX 6900 XT
• Video driver version: mesa 23.2.1-2
• Kernel version: 6.5.6-lqx1-1-lqx
• System info gist
• Proton version: 8.0-4

steam-2050650.zip

Regression in 8.0-4, game is again crashing during the 2nd cinematic of separate ways every time, or immediately if you attempt to skip the cinematic. This was fixed and working in 8.0-3.

Sure, thank you

gist

@magoolachub Can you verify that this now works on Proton Experimental?

Yep, works on experimental now, thank you!

Game crashes the whole SteamDeck when launching on SteamOS 3.5.1 build 20231011.100, Proton Experimental.
Note that I set the display refresh rate to 40Hz for RE4. Seem the crash occur when the SteamDeck switch from 60Hz to 40Hz.
Game works fine in Desktop mode.

Oct 14 18:56:55 steamdeck kernel: umip: re4.exe[2656] ip:1560024a5 sp:418738: SGDT instruction cannot be used by applications.
Oct 14 18:56:55 steamdeck kernel: umip: re4.exe[2656] ip:1560024a5 sp:418738: For now, expensive software emulation returns the result.
Oct 14 18:56:58 steamdeck gpu-trace[568]: INFO - Executing get tracing status command
Oct 14 18:56:58 steamdeck gpu-trace[568]: 127.0.0.1 - - [14/Oct/2023 18:56:58] "POST / HTTP/1.1" 200 -
Oct 14 18:56:58 steamdeck gpu-trace[568]: INFO - Executing get tracing status command
Oct 14 18:56:58 steamdeck gpu-trace[568]: 127.0.0.1 - - [14/Oct/2023 18:56:58] "POST / HTTP/1.1" 200 -
Oct 14 18:56:58 steamdeck kernel: umip: re4.exe[2656] ip:14ea19e17 sp:41c9e8: SGDT instruction cannot be used by applications.
Oct 14 18:56:58 steamdeck kernel: umip: re4.exe[2656] ip:14ea19e17 sp:41c9e8: For now, expensive software emulation returns the result.
Oct 14 18:56:58 steamdeck gpu-trace[568]: INFO - Executing get tracing status command
Oct 14 18:56:58 steamdeck gpu-trace[568]: 127.0.0.1 - - [14/Oct/2023 18:56:58] "POST / HTTP/1.1" 200 -
Oct 14 18:56:58 steamdeck gpu-trace[568]: INFO - Executing get tracing status command
Oct 14 18:56:58 steamdeck gpu-trace[568]: 127.0.0.1 - - [14/Oct/2023 18:56:58] "POST / HTTP/1.1" 200 -
Oct 14 18:56:58 steamdeck kernel: umip: re4.exe[2656] ip:1545b7f36 sp:41d6f8: SGDT instruction cannot be used by applications.
Oct 14 18:57:00 steamdeck wireplumber[1097]: <WpSiStandardLink:0x56130c0bac50> item deactivated before format set
Oct 14 18:57:04 steamdeck kernel: [drm] Failed to add display topology, DTM TA is not initialized.
Oct 14 18:57:04 steamdeck crash_20231014185704_37.dmp[2780]: Uploading dump (out-of-process)
                                                             /tmp/dumps/crash_20231014185704_37.dmp
Oct 14 18:57:05 steamdeck systemd[1]: Created slice Slice /system/systemd-coredump.
Oct 14 18:57:05 steamdeck systemd[1]: Started Process Core Dump (PID 2830/UID 0).
Oct 14 18:57:05 steamdeck core_handler[2831]: Cannot generate minidump /var/lib/steamos-log-submitter/pending/minidump/.staging-1697284624-steam-1398-None.dmp
Oct 14 18:57:05 steamdeck kernel: [drm] Failed to add display topology, DTM TA is not initialized.
Oct 14 18:57:05 steamdeck kernel: input: Steam Deck as /devices/pci0000:00/0000:00:08.1/0000:04:00.4/usb1/1-3/1-3:1.2/0003:28DE:1205.0003/input/input28
Oct 14 18:57:06 steamdeck systemd-coredump[2832]: Process 1398 (steam) of user 1000 dumped core.
                                                  
                                                  Stack trace of thread 1398:
                                                  #0  0x00000000f7fb4549 __kernel_vsyscall (linux-gate.so.1 + 0x549)
                                                  #1  0x00000000f7a894c7 n/a (libc.so.6 + 0x894c7)
                                                  #2  0x00000000f7a36717 raise (libc.so.6 + 0x36717)
                                                  #3  0x00000000f7a1e121 abort (libc.so.6 + 0x1e121)
                                                  #4  0x00000000e84312e7 n/a (libwayland-client.so.0 + 0x42e7)
                                                  #5  0x00000000e8431d2c n/a (libwayland-client.so.0 + 0x4d2c)
                                                  #6  0x00000000e8432012 wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x5012)
                                                  #7  0x00000000e8433934 wl_display_dispatch (libwayland-client.so.0 + 0x6934)
                                                  #8  0x00000000e5a41edb n/a (/home/deck/.local/share/Steam/ubuntu12_32/steamui.so + 0x241edb)
                                                  ELF object binary architecture: Intel 80386

Full logs:
dmesg.zip
journal.zip

Edit: Seem Steam Client Beta Update Channel Allow Tearing feature causes issue not only for this game but other game with unlocked FPS. Switch to Stable Update Channel solve my issue.

Haven't played it in a while and wanted to play the DLC now, however I'm back at this issue: https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1483840757 and the symptoms I mentioned initially: https://github.com/ValveSoftware/Proton/issues/6641#issue-1638573675

DXVK/VKD3D Filter does not help this time :( Tried Proton 8.0.4, Experimental, GE-8-19, 7.0.6, GE-7-55 but no luck

@alex9k1 Could you post a new Steam Runtime Diagnostics report from Steam and a Proton log? :eyes:

@alex9k1 Could you post a new Steam Runtime Diagnostics report from Steam and a Proton log? 👀

Here's the Runtime Diagnostics: https://gist.github.com/alex9k1/cade74516f6b6d38a38523704103538d

Proton Log will have to wait, cuz Denuvo locked me out while trying to fix it :(

Since you have both amdvlk and radv installed I suspect it is getting confused somehow. RE engine games have been a bit special in that regard, even though I didn't think this would happen anymore

Instead of AMD_VULKAN_ICD=RADV as I can see is set could you try running it with this?
DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json
When the Denuvo lockout is over ofc.

Since you have both amdvlk and radv installed I suspect it is getting confused somehow. RE engine games have been a bit special in that regard , even though I didn't think this would happen anymore

Instead of AMD_VULKAN_ICD=RADV as I can see is set could you try running it with this? DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json When the Denuvo lockout is over ofc.

It works! Thanks a lot.

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json is enough tho. I used to have that in /etc/environment, but thought AMD_VULKAN_ICD=RADV would be the way to go when it got introduced.

Unfortunately I've been unable to make it to the main menu since installing the DLC.
Proton 8.0-4, Proton Hotfix, and Proton Experimental all crash before providing a log (afaik?).

/bin/sh\0-c\0PROTON_LOG=1 /home/tux/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=2050650 -- /home/tux/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/run/media/tux/F1/Games/PC/SteamLibrary/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/run/media/tux/F1/Games/PC/SteamLibrary/steamapps/common/Proton 8.0'/proton waitforexitandrun  '/run/media/tux/F1/Games/PC/SteamLibrary/steamapps/common/RESIDENT EVIL 4  BIOHAZARD RE4/re4.exe'\0
chdir "/run/media/tux/F1/Games/PC/SteamLibrary/steamapps/common/RESIDENT EVIL 4  BIOHAZARD RE4"
ERROR: ld.so: object '/home/tux/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/tux/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/tux/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

GE-Proton8-21 draws a cursor on a black screen but crashes before any intro videos or the main menu--but does provide a proton log I've included below.

/bin/sh\0-c\0PROTON_LOG=1 /home/tux/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=2050650 -- /home/tux/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/usr/share/steam/compatibilitytools.d/proton-ge-custom'/proton waitforexitandrun  '/run/media/tux/F1/Games/PC/SteamLibrary/steamapps/common/RESIDENT EVIL 4  BIOHAZARD RE4/re4.exe'\0
chdir "/run/media/tux/F1/Games/PC/SteamLibrary/steamapps/common/RESIDENT EVIL 4  BIOHAZARD RE4"
ERROR: ld.so: object '/home/tux/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/tux/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/tux/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/tux/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/tux/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ProtonFixes[1734696] INFO: Running protonfixes
ProtonFixes[1734696] INFO: Running checks
ProtonFixes[1734696] INFO: All checks successful
ProtonFixes[1734696] INFO: Using global defaults for "Resident Evil 4" (2050650)
ProtonFixes[1734696] INFO: No protonfix found for "Resident Evil 4" (2050650)
Game 2050650 created interface STEAMAPPS_INTERFACE_VERSION006 / Apps
Game 2050650 created interface STEAMAPPS_INTERFACE_VERSION008 / 
Game 2050650 created interface STEAMREMOTESTORAGE_INTERFACE_VERSION016 / 
Game 2050650 created interface STEAMUSERSTATS_INTERFACE_VERSION012 / 
Game 2050650 created interface SteamController008 / 
Game 2050650 created interface SteamFriends017 / 
Game 2050650 created interface SteamInput006 / 
Game 2050650 created interface SteamNetworkingMessages002 / 
Game 2050650 created interface SteamUser017 / User
Game 2050650 created interface SteamUser021 / 
Game 2050650 created interface SteamUser021 / User
Game 2050650 created interface SteamUtils010 / 
Game 2050650 method call count for IClientNetworkingUtilsSerialized::GotLocationString : 1
Game 2050650 method call count for IClientNetworkingSocketsSerialized::GetSTUNServer : 2
Game 2050650 method call count for IClientNetworkingSocketsSerialized::GetCachedRelayTicketCount : 1
Game 2050650 method call count for IClientNetworkingSocketsSerialized::GetCertAsync : 1
Game 2050650 method call count for IClientHTTP::ReleaseHTTPRequest : 2
Game 2050650 method call count for IClientHTTP::GetHTTPResponseBodyData : 2
Game 2050650 method call count for IClientHTTP::SendHTTPRequest : 2
Game 2050650 method call count for IClientHTTP::SetHTTPRequestHeaderValue : 1
Game 2050650 method call count for IClientHTTP::CreateHTTPRequest : 2
Game 2050650 method call count for IClientRemoteStorage::FileExists : 135
Game 2050650 method call count for IClientRemoteStorage::GetFileTimestamp : 3
Game 2050650 method call count for IClientRemoteStorage::GetFileSize : 4
Game 2050650 method call count for IClientRemoteStorage::FileReadAsyncComplete : 4
Game 2050650 method call count for IClientRemoteStorage::FileReadAsync : 4
Game 2050650 method call count for IClientUserStats::RequestCurrentStats : 1
Game 2050650 method call count for IClientAppManager::GetCurrentLanguage : 2
Game 2050650 method call count for IClientAppManager::GetLaunchCommandLine : 1
Game 2050650 method call count for IClientAppManager::GetAppStateInfo : 1
Game 2050650 method call count for IClientAppManager::BIsDlcEnabled : 30
Game 2050650 method call count for IClientAppManager::IsAppDlcInstalled : 104
Game 2050650 method call count for IClientApps::BGetDLCDataByIndex : 130
Game 2050650 method call count for IClientApps::GetDLCCount : 5
Game 2050650 method call count for IClientUtils::RecordSteamInterfaceCreation : 19
Game 2050650 method call count for IClientUtils::GetSteamUILanguage : 1
Game 2050650 method call count for IClientUtils::GetAPICallResult : 8
Game 2050650 method call count for IClientUtils::GetAppID : 25
Game 2050650 method call count for IClientUtils::GetServerRealTime : 3
Game 2050650 method call count for IClientFriends::GetFriendPersonaName_Public : 174
Game 2050650 method call count for IClientFriends::GetClanByIndex : 83
Game 2050650 method call count for IClientFriends::GetClanCount : 1
Game 2050650 method call count for IClientFriends::GetFriendByIndex : 300
Game 2050650 method call count for IClientFriends::GetFriendCount : 2
Game 2050650 method call count for IClientFriends::GetPersonaName : 1
Game 2050650 method call count for IClientUser::BIsSubscribedApp : 30
Game 2050650 method call count for IClientUser::GetEncryptedAppTicket : 1
Game 2050650 method call count for IClientUser::RequestEncryptedAppTicket : 1
Game 2050650 method call count for IClientUser::GetSteamID : 12
Game 2050650 method call count for IClientUser::BLoggedOn : 3
Uploaded AppInterfaceStats to Steam
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely

Unhandled Exception:
System.TypeLoadException: Could not load type of field 'InstallerMessage.Form1+<CodecCheck>d__11:<codecQuary>5__2' (3) due to: Could not load file or assembly 'Windows.Foundation.UniversalApiContract, Version=14.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
  at InstallerMessage.Form1..ctor () [0x00063] in <f443aebfc45044fe842a2fa8533dcc55>:0 
  at (wrapper remoting-invoke-with-check) InstallerMessage.Form1..ctor()
  at InstallerMessage.Program.Main () [0x0000b] in <f443aebfc45044fe842a2fa8533dcc55>:0 
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeLoadException: Could not load type of field 'InstallerMessage.Form1+<CodecCheck>d__11:<codecQuary>5__2' (3) due to: Could not load file or assembly 'Windows.Foundation.UniversalApiContract, Version=14.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
  at InstallerMessage.Form1..ctor () [0x00063] in <f443aebfc45044fe842a2fa8533dcc55>:0 
  at (wrapper remoting-invoke-with-check) InstallerMessage.Form1..ctor()

System Info: https://gist.github.com/xangelix/982fc81e75a23b34286368884dd7deae
Proton log: steam-2050650.log

My system is dual gpu, 7900XTX and 6900XT. The single apu/graphics core inside the processor is disabled in the bios.
DXVK_FILTER_DEVICE_NAME="7900" appeared to make no difference to any of the crashes. I've also had the same experience on many different Arch and nobara kernels since the DLC was launched. The F1 drive where the game is installed is btrfs.

Happy to provide any additional logs or do any testing.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1784189171

Not sure exactly what change fixed it, but GE-Proton8-23 now functions on my system as expected. Experimental and Hotfix proton versions still crash before a log is created as before. AFAIK no GE specific patches were added for Resident Evil 4, so the fix for my system is probably upstream.
Current system info https://gist.github.com/xangelix/a0d348ad204cea0443f76b68f7f33cf0

Compatibility Report

• Name of the game with compatibility issues: Resident Evil 4 (Remake)
• Steam AppID of the game: 2050650

System Information

• GPU: RX 7800 XT
• Video driver version: Mesa 23.3.0 (RADV)
• Kernel version: 6.5.13-tkg-pds-gentoo-gcc-zen2
• Link to full system information: Gist
• Proton version: 8.0-4

I confirm:

• [x] that I have checked whether there are updates for my system available.

Log: steam-2050650.log
Save Data: 2050650.zip

Symptoms

Performing a specific set of actions in Chapter 4, after defeating the game's first giant, causes the game to become unable to progress in one of two fashions: either the next objective (entering the church) won't be loaded (both the inside of the church and the save/safe room won't be properly loaded and won't have floors to walk on) or they will be loaded but entering the room on the second floor the church triggers an infinite loading screen. This will occur regardless if you use Proton 8.0-4, experimental, or GE-Proton-8.xx (in my testing, 8.25).

EDIT: I've performed a process of elimination and it seems modding Ashley in any way seems to cause this.
If you so much as mod her outfit or hair, the game will throw an infinite loading screen upon opening the 2nd floor room door or the "void" issue. Which is strange, because this clearly doesn't seem to be a problem for people on Windows and there are a lot of vkd3d-proton warning messages in the log. (They're basically the entire log)

Reproduction

1. Import the save data attached
2. Load the chapter 4 MANUAL save (there's a reason for this; it seems loading the autosaves after this bug occurs corrupts the autosave)
3. If you don't know where to go, open the map and find the church on it; walk your way to the church
4. On the way, you'll find a wooden scaffolding bridge; shortly after, you'll find an earthy (non-wood) slope going upwards from you. Prepare your (sniper) rifle, don't walk up the slope yet.
5. At the top of this slope, a wolf enemy will appear and mutate; scope in on its head and wait for it to finish mutating before head-shotting it. EDIT: The method doesn't seem to matter, but that's what I did consistently in testing.

6a) At this juncture, your progress to access the church or save will be impeded in either one of two ways: you will either be unable to actually step foot inside the church nor the safe/save room, because doing so will drop you into an infinite void, or the 2nd floor door of the church (the game's next primary objective after solving the small puzzle on the 1st floor of the church) will greet you with a sudden infinite loading screen. For more specific context, in my case, I explored the 2nd floor first and found a broken phone, then turned around to open said door.

6b) Additionally, if you find that the church has not properly loaded, you will also find that you can no longer go back the way you came either. Because once you backtrack past the scaffolding bridge and into the cave just prior that you came through, your path back has also been unloaded and there is no floor to walk on. Attempting to reload your autosave in either state you have found yourself in will break the autosave and also prevent it from loading in the attempt.

Replying to https://github.com/ValveSoftware/Proton/issues/6641#issuecomment-1841121085

i have been playing and replaying the game in a super unhealthy amount on linux for a long time now, it looks like your save broke

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

i have been playing and replaying the game in a super unhealthy amount on linux for a long time now, it looks like your save broke

I'm aware, I already said this can happen and pointed out the reason why it happens Lol
On a technical level I don't understand why, because this doesn't happen with Windows users as far as I've seen, but there's something definitely going wrong here.

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

ooooh you were modding, yeah, that can cause those issues even on windows, i dont think this is a proton issue

Honestly, I wouldn't be so quick to dismiss it. The log is littered with vkd3d messages and, not that I know for certain it's vkd3d doing something wrong, but this is not an issue on Windows - as I've already stated twice.

The game launches on a black screen, any suggestions?
https://gist.github.com/xnuohz/462f79a95785c617aafd8429e420e30c

I'm getting Fatal D3D Error (6, E_OUTOFMEMORY) as soon as start new game or open options. While it was running fine on Windows.
GTX 1060 6G
Tried Proton-GE/Experimental/8.
Launch options gamemoderun %command%
Looking at nvtop it uses only half the VRAM and then crashes. Cannot change video setting because crashes in options.
Looking at the logs I think the error is followed by these

Fossilize INFO: Overriding serialization path: "/home/me/.local/share/Steam/steamapps/shadercache/2050650/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize WARN: Pipeline library handle 0x000074d28e566b60 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 0x000074d28e5804a0 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 0x000074d28e599cb0 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 0x000074d28e5aec30 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).
NVVM compilation failed: 1
NVVM compilation failed: 1

That is so stupid, but PROTON_HIDE_NVIDIA_GPU=1 fixes Fatal D3D Error (6, E_OUTOFMEMORY)

Unable to launch the game at all currently, opens the capcom crash reporter with "Error Code 0x200000" and fails to create a crash log, my specs
kernel: 6.7.9
distro: cachyos
gpu: amd 6600
cpu: Intel i7-12700K
ram: 32gb
desktop: Plasma 6.0.3
display server: Wayland (happens on both X.org and Wayland though)

steam-2050650-april-14.log
steam-2050650.log
Two generated proton logs

vulkaninfo --summary
https://gist.github.com/Funtimes909/1cbe4a8936162f864d17ca3e8bbcc998

output of "sudo pacman -Qqn | grep -i -e vulkan -e mesa"
lib32-mesa
lib32-vulkan-icd-loader
lib32-vulkan-radeon
mesa-git
mesa-utils
vulkan-headers
vulkan-icd-loader
vulkan-tools

My game currently opens with proton experimental and runs at a locked 30fps. Running Fedora 40 with gnome. Does the same thing in both X11 and wayland. Running on a 12600KF and a 3060. Runs at 30fps or lower even in gamescope, being in the title screen or in game doesn't really change the performance. Changing the settings or resolution also does nothing to the performance. Also running the RPM version of Steam.

That is so stupid, but PROTON_HIDE_NVIDIA_GPU=1 fixes Fatal D3D Error (6, E_OUTOFMEMORY)

I can confirm the option PROTON_HIDE_NVIDIA_GPU=1 prevents the game from Fatal D3D Error and random freezes when playing. The fatal error is easily triggered by entering a new area, and the game can freeze quickly by continuously shooting with Infinite Rocket Launcher.
My graphics setting memory measure is 2.82/3.94 GB, the text is still white (so no out of VRAM) and I could play the game without any problem before, maybe before the update for Separate Ways DLC.

My Specs (I tried everything i can):
Linux Mint 21.3 Cinnamon
Kernel: 5.15.0-118, 6.5.0-45, 6.8.0-40
GPU: GeForce GTX 1050 Ti Mobile 4GB
NVIDIA driver: 535.183.01, 545.29.06, 550.107.02, 555.58.02
Proton: 8.0-5, 9.0-5, Experimental, GE-Proton9-11

System Information

• GPU: Palit RTX 2070 Super
• Video driver version: 565.77
• Kernel version: 6.9.3-76060903-generic
• Link to full system information report: gist.github.com/kamilw11/e74841f425e138c2e41d0aa57f17ed4a
• Proton version: Proton Experimental
• Output from PROTON_LOG=1: Proton_log.zip

Symptoms

The issues that I have textures going missing, especially the floor which likes to happen after playing for 5-10 minutes, sometimes all the face textures turn pink, and sometimes all the meshes clump up together in one place. I haven't had a crash yet luckily. I'm only 30ish mintues into the game.

What I have tried so far:

• I have tried other proton versions: 9.04, 8.05, and Proton-GE-23
• I have disabled steam overlay as caused crashes with the other RE remakes
• I have tried to run the game with these launch options previously with no success:
  DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 2070 SUPER" VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json VKD3D_CONFIG=force_compute_root_parameters_push_ubo PROTON_LOG=1 %command% /WineDetectionEnabled:False
• I downloaded the latest vkd3d-proton .dll s and put them in the game directory, then using protontricks make the game use those instead of what proton experimental came with.

Debain Bookworm. AMD NAVI10.
game runs, but audio consistently underuns and pops.

Tried to edit the local_config.ini to change windows mode and resolution and uh ... that didn't exactly help 😄
re4flicker.mp4

@alex9k1 I got exact same problem:

• After I updated nvidia proprietary driver from 575 to 580 (My GPU is 1650Ti, Turing)
• On Proton 10+ (regardless Vanilla or GE)
• On RE4, which uses VKD3D (any DX9, DX10, DX11 games work just fine)

So, I think the problem is with VKD3D, but Proton rebased on some version that doesn't support new dirvers. Hope that helps.

And also, when I honestly don't know how game switched to windowed mode (not borderless), flickering stopped.

However, I +1 that I also have this problem.

Also, when I add PROTON_ENABLE_WAYLAND=1 to the run options, I begin to understand the problem - game fails to scale itself and detect the resolution. The window infinitely bounces between sizes which seem to create this flickering.

Hi! I was having the same issue.

I solved it adding the next config at launch options in Steam:

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%

Hope it helps! Greetings.

Hi! I was having the same issue.

I solved it adding the next config at launch options in Steam:

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%

Hope it helps! Greetings.

@isimons OMG, that helped! The only difference is I used nvidia.json (since it's the one I have) And it worked! Thanks!!!