Resident Evil Village (1196590)

[NTMan]

Compatibility Report

• Name of the game with compatibility issues: Resident Evil Village
• Steam AppID of the game: 1196590

System Information

• GPU: AMD Radeon 6900XT
• Driver/LLVM version: Mesa 21.3-git/12.0.0
• Kernel version: 5.13-rc0
• Link to full system information report as Gist
• Proton version: experimental-6.3-20210507

I confirm:

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

steam-1196590.log

Symptoms

1. Impossible to change display settings. Clicking on "Display" item in options has not any effect.
   

2. The game crashes after start.

Reproduction

Always.
Below the demonstration video (will opened on youtube)

[kisak-valve]

Hello @NTMan, /usr/include/c++/11/array:188: std::array<_Tp, _Nm>::value_type& std::array<_Tp, _Nm>::operator[](std::array<_Tp, _Nm>::size_type) [with _Tp = unsigned int; long unsigned int _Nm = 512; std::array<_Tp, _Nm>::reference = unsigned int&; std::array<_Tp, _Nm>::size_type = long unsigned int]: Assertion '__n < this->size()' failed. looks like a line of interest from the log.

[AwesamLinux]

System Information

• GPU: RX 5700
• GPU Driver: 21.1.0 - kisak-mesa PPA
• Kernel version: 5.10.35-051035-generic
• Distro version: Mint 20.1 (64bit) (Cinnamon)
• Proton version: experimental-6.3-20210507
  system_info.txt

Compatibility Report

With Proton Experimental (6.3-20210507) I'm able to get into gameplay (played only like ~10 minutes though so far of the beginning). I can confirm that the display settings can't be changed. Also the cut-scene videos are just a place-holder image.

With regular Proton-6.3-3, the game crashes on launch.
steam-1196590-experimental-6.3-20210507.log.zip
steam-1196590-proton-6.3-3.log

[NTMan]

In Proton experimental-6.3-20210512b fixed bug with unable changing display settings. But the game still crashing at start.
steam-1196590.log

UPD: Updating mesa solve this issue.

[arzardk]

Game is fully playable for me but returning to main menu crashes GPU
Pop!_OS 20.10
Vega 56, Mesa 21.0.0
steam-1196590.log

[CarnageDevs]

Game works perfectly (excluding cutscenes) but I'm having an issue where after viewing notes, my mouse is unfocused on the game window and camera movement no longer works until I press ESC to open the pause menu and resume the game.

Happens on both borderless and fullscreen.

Running KDE on OpenSUSE Tumbleweed
RTX 2080 Ti, driver ver 460.73

[Realitaetsverlust]

System Information:

• GPU: RX 6800 XT
• GPU Driver: 4.6 Mesa 21.0.3
• Kernel version: 5.12.1-2-MANJARO
• Distro version: Manjaro Linux
• Proton version: experimental-6.3-20210514
• Full system information as https://gist.github.com/Realitaetsverlust/dd33e42b7bb0f8eaa3ab1f4640e5dae6

Compatibility report
Game works in general (apart from the graphics menu as OP described), but I have some very weird stripes in the game.

Cutscenes are all placeholders too, but that is due to media foundation afaik, so not unexpected.

[kisak-valve]

Hello @Realitaetsverlust, we'll probably want to re-evaluate rendering issues in this game and mesa/radv after https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10692 lands (or try a build of mesa which includes that merge request).

[Realitaetsverlust]

Hello @Realitaetsverlust, we'll probably want to re-evaluate rendering issues in this game and mesa/radv after https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10692 lands (or try a build of mesa which includes that merge request).

Thanks for the answer! I used whatever mhwd delivered me as driver, so I guess I'll just wait for the next rolling update. Thanks for the reply! :)

[Hunk4TH]

Working so far for me with Proton Experimental. However I notice fps drop when shooting an enemy or reloading. Anyone else experience this? I'm using a GTX 1070 I don't get this in Windows.

[DomiStyle]

@Hunk4TH Digital Foundry had the same issue. So it seems like it can happen on Windows too.

Not sure what causes it though, the demo ran perfectly fine on an AMD card.

[Hunk4TH]

@Hunk4TH Digital Foundry had the same issue. So it seems like it can happen on Windows too.

Not sure what causes it though, the demo ran perfectly fine on an AMD card.

That's odd. I beat it on Windows 10 and never encountered that issue. Of course everyone's setup is different. It's still enjoyable imo. Hopefully that occurrence can be fixed though! Of course I'm running KDE Plasma maybe that could be the issue too?

[Equivocal90]

Game has been running well with Proton Experimental. Running it on mesa-git has resolved the striping issue that @Realitaetsverlust mentioned.

I've ran into a consistent crash to desktop attempting to cross a bridge several hours into the game. I ran the game again with logging enabled and caused the crash. Here is the log steam-1196590.tar.gz

It crashed 5-6 times at roughly the same spot and I tried to changing all the graphics settings to minimum at 720p but the crash still occurred.

[kisak-valve]

Hello @Equivocal90, in your log, it looks like the game hit the same assert as the opening post #4811 (comment).

[SergeyLatyshev]

The game stopped working after today's update. I see a black screen, and then the game closes. It worked fine before that (except for crashes when it ate too much VRAM, and also sometimes I saw white space instead of map and inventory).
steam-1196590.zip

[AwesamLinux]

System Information

• GPU: RX 5700
• GPU Driver: Mesa 21.3.0-devel (git-8413c57 2021-07-19 focal-oibaf-ppa)
• Kernel version: 5.11.0-22-generic
• Distro version: Linux Mint 20.2 (64 bit) (Cinnamon)
• Proton version: 6.3-5

Retest Compatibility Report

Can confirm the game crashes on launch after todays update, just a window with a black screen that then closes.

Tried also with Proton Experimental and 6.12-GE-1

steam-1196590-6.12-GE-1.log
steam-1196590-experimental-6.3-20210719.log
steam-1196590-proton-6.3-5.log
system_info.txt

[kisak-valve]

Hello @SergeyLatyshev, these look like some lines of interest from your log:

328:err:vkd3d_dxil_log_callback: dxil-spirv: Raw 16-bit load-store was used, which must be implemented with SSBO or BDA.
328:err:vkd3d_dxil_log_callback: dxil-spirv: Failed to convert function.
328:warn:create_shader_stage: Failed to compile shader, vkd3d result -3.
328:warn:d3d12_pipeline_state_init_compute: Failed to create Vulkan compute pipeline, hr 0x80070057.
[...]
324:err:vkd3d_dxil_log_callback: dxil-spirv: Invalid component type for image.

Which is followed by an access violation (c0000005). It hints that the game's trying to do something that VKD3D-Proton hasn't been taught to handle yet.

[SergeyLatyshev]

the game's trying to do something that VKD3D-Proton hasn't been taught to handle yet.

So, Capcom added something new and I'll have to wait for further VKD3D progress?

[jarrard]

Did this just start happening when you used a newer proton version? Maybe try a older proton version and see what happens.

Always possible they overwrite the workaround for this.

[SergeyLatyshev]

Did this just start happening when you used a newer proton version? Maybe try a older proton version and see what happens.

No, it was the same Experimental and 6.12-GE. What was changed is the game itself, it got an update yesterday that added AMD FSR and some changes regarding Denuvo.

Actually, I updated the Nvidia driver today from v465 to 470, and after that the game launched once. It ran at exactly 9 fps and crashed as soon as I pressed the inventory key. I had Proton logging turned off, so I don't have a log file, and the game cannot launch since that.

[jarrard]

Yeah maybe something in FSR support not quite ready for Linux atm. Hopefully very soon.

[ChrisLauinger77]

It does also not start any more for me after the update :(
https://gist.github.com/ChrisLauinger77/ac3f8a7cf89c1499688617bbad1d0cdb

[Oschowa]

The crashes with the new update are caused by the added fp16 FSR shaders and should be fixed in vkd3d-proton master. Users on older AMD gpus will also need this Mesa patch for FSR to look correctly: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12004
I hope the vkd3d-proton fixes can make it into the next experimental update, in the meantime, you can manually overwrite the 64bit d3d12.dll shipped by Proton with a build of vkd3d-proton master to make it work again.

[Oschowa]

Also the game needs to be launched with WINEDLLOVERRIDES=dxgi=b %command% to get any kind of decent performance as recent Proton is missing the dxgi factory workaround for dxvk's dxgi.

[NTMan]

Also the game needs to be launched with WINEDLLOVERRIDES=dxgi=b %command% to get any kind of decent performance as recent Proton is missing the dxgi factory workaround for dxvk's dxgi.

Also without WINEDLLOVERRIDES=dxgi=b %command% the current Proton Experimental 6.3-20210723b leads memory leak.

steam-1196590-without-overrides.log

[SergeyLatyshev]

Updated today Proton Experimental runs the game fine, even FSR works (but sometimes the game crashes when I change FSR settings). The game consumes too much RAM though, about 17 GB, even with WINEDLLOVERRIDES=dxgi=b.

[ChrisLauinger77]

It works 4 me as well - could finish the game now

[Mershl]

Proton experimental + Latest Game Patch shows blue flames on pillars while FSR is enabled. The issue is immediatly fixed once FSR is disabled.

proton-experimental-20210730 + mesa 21.1.6 + RADV + RX6800
Screencast of the issue: https://streamable.com/terer1

[TimeFreeze1337]

Resident Evil VIllage is always crashing on startup no idea why but i guess it doesnt hurt to post the proton log maybe it helps. This log was generated when using Proton Experimental, Proton GE doesnt work either.

steam-1196590.log

[kisak-valve]

Hello @TimeFreeze1337, these look like some lines of interest from your log:

440:warn:vkd3d_allocate_device_memory: Memory allocation failed, falling back to system memory.
440:err:vkd3d_allocate_device_memory: Failed to allocate device memory (size 16777216, type_flags 0x1, type_mask 0x80).
[access violation c0000005]

It should be noted that your 750 Ti has half the VRAM of the game's listed minimum requirements.

[TimeFreeze1337]

Yes i know but it should still at least let me into the Game? On Windows i could get into the demo just fine. And looking at some videos on youtube it seems like the 750 TI can play the game just fine with 2GB.

[Venemo]

@TimeFreeze1337 As this is a different problem from what was reported here, I suggest you to open a separate bug report for this.

The crash is this line:

Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x0000000143c980fc).

Unfortunately it contains very little useful information.

[Venemo]

Sorry, that's my mistake - I was unaware of the rules of this bug tracker. Feel free to discuss other problems with Resident Evil Village here.

[ghost]

MF cutscenes in-game show distorted video in those sections:
Castle Section:

• The scene that Alcina Dimitrescu is looking at a mirror shows distorted video

House Beneviento Section:

• The section that you have to mess around a film puzzle, after getting all of them in the correct order it plays a video in the wall that is also distorted. https://www.gamesradar.com/resident-evil-village-film-puzzle-solution-house-beneviento/

Tested in Proton Experimental 26/10/2021 (DD/MM/YYYY)

[ngreve]

System:

OS: Arch Linux
KERNEL: 5.15.5-arch1-1
CPU: AMD Ryzen 7 3700X 8-Core
GPU: AMD Radeon RX 6900 XT (SIENNA_CICHLID, DRM 3.42.0, 5.15.5-arch1-1, LLVM 13.0.0)
GPU DRIVER: 4.6 Mesa 21.2.5
RAM: 16 GB

With Proton 6.3-8: The intro "cutscene" in which the RE engine logo should be presented just shows this placeholder (works with 6.21-GE-2):

I already had the same issue in RE7. Every cinematic only showed this placeholder image when cinematics/cutscenes should be played.

Proton 6.3-8 and Proton 6.21-GE-2: Text in settings is not shown:

Only the display settings do show the quality statistics:

I don't know if it helps in any way but the game also does not start in fullscreen.

[Venemo]

@ngreve Please upgrade to the latest mesa and let us know if that still has this issue or not.

[ngreve]

Updated to GPU DRIVER: 4.6 Mesa 22.0.0-devel (git version). Exact same issues as before. (Also Updated and clarified my original post)

[Oschowa]

@ngreve it seems to me like you are actually using the proprietary vulkan driver from amdgpu-pro to run the game and not mesa, i can reproduce this issue only on amdgpu-pro 21.40.1, not on Mesa/RADV or amdvlk 2021.Q4.1-1.

[ngreve]

Using 6.21-GE-2 it seems to run perfectly. I have to explicitly use RADV by setting the launch options to VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%. Thanks for the hint!

Using 6.3-8 it seems that the issue with the placeholder image is still there, at least for the startup scenes when the RE Engine logo is presented. Multiple users at ProtonDB reported the same issue for cutscenes in general.

Thanks again and thanks for your work in general. I will use 6.21-GE-2 for now.

[ThisNekoGuy]

The new Proton Experimental version causes the game to not start now; I just had it running before I updated experimental just now...
steam-1196590.log
PROTON_LOG=1 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr gamemoderun %command%

[ghost]

the resident evil village gold edition demo is broken
you can't interact with objects in-game, tried from experimental to stable proton and none of them worked
might be DRM related

[headlesscyborg]

Hello, I'm not able to reach a playable state when it comes to this game.

Proton experimental: crashes on start
Proton 7.0-5: crashes on start
Proton GE 7-43: runs but freezes within 5 minutes

System info:

• CPU: i5 10500H
• GPU: NVIDIA RTX 3060 Laptop GPU
• RAM: 16GB DDR4
• OS: Arch Linux + GNOME
• Steam system information: https://gist.github.com/headlesscyborg/e9a2ac00fbf8034284fb29e443b8295e

Logs:

• terminal output (first launched using Proton experimental, then launched using Proton 7.0-5): https://gist.github.com/headlesscyborg/cac494b055c939af99f5923c1eb2d9e7

I can only play the game with Proton GE but in that case the game keeps freezing, for example it's impossible to leave the first building in the forest but the game also crashes prior to that.
It would be much appreciated if someone could look into it, it seems I'm not alone (see ProtonDB). if there's anything you need to investigate it, just let me kno.w

[X6205]

MF cutscenes in-game show distorted video in those sections:

House Beneviento Section:

• The section that you have to mess around a film puzzle, after getting all of them in the correct order it plays a video in the wall that is also distorted. https://www.gamesradar.com/resident-evil-village-film-puzzle-solution-house-beneviento/

I have noticed yesterday that game has "Verified" status, so i decided to give it a try and load some old save.. Film puzzle in House Beneviento does not play movie, but only green screen is visible. This i have discovered by accident loading game exactly at this part.

Running Ubuntu 22.04 with RX 6700 XT and mesa 23.0.1 from Kisak Mesa repo and default Proton 7.0.6

[ParaSait]

CPU: AMD Ryzen 5 3600XT
GPU: AMD Radeon RX 5600 XT
RAM: 16GB
OS: Arch Linux
Kernel: 6.2.12
Mesa: 23.0.2
Proton: experimental-8.0-20230417

The game works fine except for frequent crashing on a highly irregular and random basis. Sometimes I can play for hours, other times I don't even last a few minutes, and I sometimes have to retry a couple of times to get past a single checkpoint. I can see no rhyme or reason in when it happens - it can occur at any point; it even happened while I was in a shop menu once.

What happens is that the game window ceases rendering (it freezes and turns black when the window is moved), and the game locks up, but the background audio keeps playing until I terminate the process.

I have tried to collect a log with PROTON_LOG=1, but the logging ceases once a crash happens and I see nothing out of the ordinary appear in it the moment it happens.

[Shallrath]

I could play the base game with only 2 or 3 crashes in total but the DLC Shadows of Rose keeps crashing every 5 minutes so it is barely playable. Happens with both Proton 8.0-4 and experimental. I wonder what makes the difference that the base game works close to perfectly and the DLC is basically unplayable. I was using the same graphics settings obviously. Only thing I can think of is that the DLC forces you to play in 3rd person view and I played the whole base game first person.

i7-6700K
GTX 1070
Arch Linux, Kernel 6.6.7, Nvidia 545.29.06-6