Resident Evil 4 (2050650) #6641
Comments
kisak-valve
added
the
Game compatibility - Unofficial
|
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 Screenshots
|
|
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: |
|
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 |
|
I was experiencing the same, but removing |
|
@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. Here's the Proton log. My specs are: mesa-git 23.1.0_devel.168578.79ac6197a99.932463d268438ce945b21718552d92ab-1 OS: EndeavourOS 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. 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 Proton Log - started a new game, it froze a few seconds into the first cutscene (the ritual): |
|
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.
|
|
Have you tried to set the fps to 30 (through ingame setting!) ? |
|
Hello @GuillotineGwen, please copy your system information from Steam ( |
|
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 😄 re4flicker.mp4 |
|
Ok, not sure what did the trick, but I managed to fix my issues. I did: use GE-Proton7-53
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 |
|
@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 |
|
|
|
@alex9k1 are you sure didn't change anything else? |
You are right. I updated my comment regarding the fix. TL;DR it wasn't gamemode, it was 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. |
|
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) running NixOS proton GE 7-53 |
Glad I could help, but |
|
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. |
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. |
So there still isn't way to run this game without capping it to 30 ? |
Seems so. At least for me. |
|
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 Upd: Radeon 7900XTX users should used |
|
Proton log: steam-2050650 (truncated).log 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. |
|
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
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. |
|
Hello @magoolachub, please copy your system information from Steam ( |
|
Sure, thank you |
|
@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. Full logs: 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: #6641 (comment) and the symptoms I mentioned initially: #6641 (comment) 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? 👀 |
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 |
It works! Thanks a lot.
|
|
Unfortunately I've been unable to make it to the main menu since installing the DLC. Steam terminal log, which is the same for all official proton releases: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. Proton GE terminal log:System Info: https://gist.github.com/xangelix/982fc81e75a23b34286368884dd7deae My system is dual gpu, 7900XTX and 6900XT. The single apu/graphics core inside the processor is disabled in the bios. Happy to provide any additional logs or do any testing. |
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. |
Compatibility Report
System Information
I confirm:
Log: steam-2050650.log SymptomsPerforming 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. Screenshot:
Reproduction
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. |
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 |
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? |
|
I'm getting |
|
That is so stupid, but |
|
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 steam-2050650-april-14.log vulkaninfo --summary output of "sudo pacman -Qqn | grep -i -e vulkan -e mesa" |
|
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. |
I can confirm the option My Specs (I tried everything i can): |
and others
Compatibility Report
System Information
I confirm:
steam-2050650.zip
Not sure, what you guys can see there, but on this run where I captured the log I did:
Symptoms
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.The text was updated successfully, but these errors were encountered: