Resident Evil 4 (2050650)

[alex9k1]

Compatibility Report

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

System Information

• GPU: Radeon RX 7900XTX
• Driver/LLVM version: Mesa 22.3.6
• Kernel version: 6.3.0-rc2 mainline
• Link to full system information report as Gist: https://gist.github.com/alex9k1/98e7217ac2156c3d4634f524ae887359
• Proton version: Experimental

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

steam-2050650.zip

Not sure, what you guys can see there, but on this run where I captured the log I did:

• start the game
• try to change settings
• load a save game
• quit the game

Symptoms

• Game immediately crashes with Proton 7.0.6, needs Experimental or GE-Proton7-51 to run
• Can't change any settings
• Performance was fine on first run, but seems to be 20-30fps, dropping to what feels like > 10 fps at some places. Deleting the prefix does not help
• Game freezes when trying to exit (to desktop)
• Game is using ~20 - 24GB RAM. Not sure if that's a bug, but that doesn't seem normal
• MangoHud goes bonkers, refreshes extremely fast and shows 0 fps

Reproduction

Start the game from steam, try to change any settings and start a new game.

Further notes

In the meantime, I managed to fix my issues. Apparently, it needed to filter the right GPU with DXVK_FILTER_DEVICE_NAME=6600 (6600 cuz I have a 6600XT in my secondary PC where I found the fix), still running on ge-proton7-53. Quite surprising, considering it's a D3D12/VKD3D game. Without the filter, Mongohud still reports, that the 6600XT is being used, so no clue what's going on.

[kodatarule]

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

Screenshots

  

steam-2050650.log

[Spencer-0003]

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

[Eisendroid]

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

[hjpaul7]

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

[flightlessmango]

@alex9k1 what mangohud version are you using?

[alex9k1]

@alex9k1 what mangohud version are you using?

0.6.8

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

[hjpaul7]

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

[TathagataDM]

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.

[AlmightyLaxz]

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

[GuillotineGwen]

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

[Eisendroid]

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

[kisak-valve]

Hello @GuillotineGwen, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[alex9k1]

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.

[alex9k1]

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

[alex9k1]

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.

[flightlessmango]

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

[alex9k1]

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

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

[flightlessmango]

@alex9k1 and mangohud is not acting weird?

[alex9k1]

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

[flightlessmango]

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

[flightlessmango]

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

[alex9k1]

@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

[hjpaul7]

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

[noelpilled]

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.

[alex9k1]

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

[TathagataDM]

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.

[Eisendroid]

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.

[ions98]

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 ?

[Eisendroid]

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

Seems so. At least for me.

[Famf]

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.

[mbriar]

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

[TathagataDM]

Replying to #6641 (comment)

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

[Fothsid]

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.

[hjpaul7]

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.

[gort818]

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]

@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

[AlmightyLaxz]

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.

[iddm]

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.

[ions98]

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

This workaround only works on AMD gpus.

[iddm]

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.

[Arnesfield]

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.

[iddm]

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

Can you change the settings?

[Arnesfield]

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.

[iddm]

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

Weird, doesn't work for me either.

[kisak-valve]

Hello @Arnesfield, @vityafx, full quoting in your reply chains of consecutive comments adds pages of redundant information and is wholly unnecessary to understand the discussion. Please try to avoid the excess (pages) of quotes.

[ions98]

Replying to #6641 (comment)

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.

[iddm]

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

[joeblack2k]

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"

[kodatarule]

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

[ions98]

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.