Open alex9k1 opened 1 year ago
kodatarule
commented
1 year ago 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.
mslauson
commented
1 year ago 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?
Launching with DXVK_FILTER_DEVICE_NAME=6800 %command%
SteadfastRPD
commented
1 year ago 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.
blahbleepew
commented
1 year ago 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.
vectorphresh
commented
1 year ago 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.
oliverklee
commented
1 year ago 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.
NTMan
commented
1 year ago 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%
reboot-mk
commented
1 year ago 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
ffrasisti
commented
11 months ago Is there going to be a fix for the separate ways dlc crashing on steam deck?
alosarjos
commented
11 months ago 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.
magoolachub
commented
11 months ago 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.
kisak-valve
commented
11 months ago Hello @magoolachub, please copy your system information from Steam (Steam -> Help -> System Information) and copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.
magoolachub
commented
11 months ago Sure, thank you
Blisto91
commented
11 months ago @magoolachub Can you verify that this now works on Proton Experimental?
magoolachub
commented
11 months ago Yep, works on experimental now, thank you!
ngoquang2708
commented
11 months ago 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 80386Full 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.
alex9k1
commented
11 months ago 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
Blisto91
commented
11 months ago @alex9k1 Could you post a new Steam Runtime Diagnostics report from Steam and a Proton log? :eyes:
alex9k1
commented
11 months ago @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 :(
Blisto91
commented
11 months ago 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.
alex9k1
commented
10 months ago 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=RADVas 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.jsonWhen 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.
xangelix
commented
10 months ago 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?).
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.
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.
xangelix
commented
9 months ago 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
ThisNekoGuy
commented
9 months ago Log: steam-2050650.log Save Data: 2050650.zip
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)
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.
ghost
commented
8 months ago 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
ThisNekoGuy
commented
8 months ago Replying to #6641 (comment)
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.
ghost
commented
8 months ago Replying to #6641 (comment)
ooooh you were modding, yeah, that can cause those issues even on windows, i dont think this is a proton issue
ThisNekoGuy
commented
8 months ago 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.
xnuohz
commented
8 months ago The game launches on a black screen, any suggestions? https://gist.github.com/xnuohz/462f79a95785c617aafd8429e420e30c
qwelias
commented
7 months ago 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: 1That is so stupid, but PROTON_HIDE_NVIDIA_GPU=1 fixes Fatal D3D Error (6, E_OUTOFMEMORY)
Funtimes909
commented
4 months ago 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
JamDoggie
commented
3 months ago 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.
vanphong1310
commented
3 weeks ago That is so stupid, but
PROTON_HIDE_NVIDIA_GPU=1fixesFatal 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
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.