Resident Evil 4 Chainsaw Demo (2231770)

[thndgonz]

The game opens fine and I can do anything around the menu screen/options. Even when you start the game I can see a full 60FPS with proton experimental. (Doesn't work with Proton 7.0)

The thing is that the game randomly freezes after going through a "cutscene" of a deer I believe at the start. I don't know if it's a frame freeze or not because I keep hearing steps/audio.

Overall I would dare say it will probably work fine with proton experimental until completion it just that it has those weird random freezes.

[kisak-valve]

Hello @thndgonz, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, 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.

[Fothsid]

Hello. I am experiencing an issue with the settings not working as intended (can't change any options at all), as well as performance being awful with neither CPU nor GPU utilization being nowhere near 100%. Happens on both X11 and Wayland sessions for me with practically no difference. The game also doesn't close itself upon exit, having to force close it through Steam's quit button.

Here's the Proton log for the game (launch -> options -> trying to change stuff with no effect -> exit the game) steam-2231770.log

as well as a system information report from Steam: gist

[thndgonz]

steam-2231770.zip

System details

https://gist.github.com/thndgonz/271a0ec1678f3af002f04edeaad2fee5

[headlesscyborg]

Hello, I have the same issue. I have two PCs (an AMD desktop and an Nvidia laptop) and it only happens on the desktop, so I can provide logs from both, that might help.

AMD desktop

• launches in windowed mode
• impossible to change any settings (tried keyboard, mouse, controller - the game otherwise registers input correctly, for example for menu navigation)
• doesn't close on exit, needs to be force closed
• tried both Wayland and X11
• System info: https://gist.github.com/headlesscyborg/df0f25817741f69f5b9e4d3ba0695663
• Proton log: https://gist.github.com/headlesscyborg/31f3a3f98d12a891b9ad3d6beea48a55

Nvidia laptop

• launches in fullscreen mode
• any settings can be adjusted fine
• closes correctly on exit
• tried on X11 (Wayland not supported)
• System info: https://gist.github.com/headlesscyborg/4e24de3991d518cfdf1562a6be8c8acd
• Proton log: https://gist.github.com/headlesscyborg/3c56547fa8718e93f5b75de5e0b86194

Both running the same up-to-date Arch Linux with the same GNOME version and the very same Proton experimental (tried GE and Hotfix as well, no difference). (I doubt it has anything to do with GPU vendor, I'm just using it to distinguish the two machines)

EDIT 28th March: product refunded

[Barnacle]

I understand that GTX 750 is lower than minimum requirement for this game, but judging by YT videos it still should work. However I have this result on my system no matter what graphic settings I use:

• System info: https://gist.github.com/Barnacle/1174f49e722b80073d135a4ba82741a7
• Proton log: steam-2231770.zip

[kisak-valve]

Hello @Barnacle, my understanding is that Maxwell (non-refresh) lacks support for multiple Vulkan extensions which VKD3D-Proton uses to provide equivalent support of D3D12. That is a hardware limitation which is not easy or performant to workaround.

[mmbossoni]

As a comment, on NVIDIA GPU's I could run it on 30fps without crashes, 60fps crashes occasionally. Above that it crashes almost at the beginning. I have a GTX 1070. I ran with Hotfix, hotfix + latest vkd3d and GE. All with pretty much same results.

[mmbossoni]

Logs of game at 120fps (Experimental Bleeding Edge + latest vkd3d from git) Massive slowdowns, but no crashes (because of trace probably?) GPU jumps to 100% usage when the "crash" used to happen steam-2231770.log

[Fothsid]

Hello again. I've managed to fix the issue I had on my machine by manually specifying the NVIDIA Vulkan ICD file:

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json gamemoderun %command%

[DerekBoucher]

@Fothsid Thank you so much :pray: This fixed the issue for me.

For those whom this might help: I use AMD graphics, but the suggested fix still works. In my case, I had to use my radeon specific icd file:

(Ubuntu 22.10, eGPU enclosed Radeon 6950 XT)

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

[arthurbcoelho]

Hello again. I've managed to fix the issue I had on my machine by manually specifying the NVIDIA Vulkan ICD file:

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json gamemoderun %command%

Thank you, @Fothsid!! I almost gave up gaming on linux