search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.41k stars 1.03k forks source link

Horizon Forbidden West (2420110) #7590

Open agurenko opened 3 months ago

agurenko commented 3 months ago

Compatibility Report

System Information

I confirm:

steam-2420110.tar.gz runtime-information.tar.gz

Symptoms

Mouse sensitivity is off the charts, single movement results in camera moving at insane speed

Reproduction

Just load the game, try to move the mouse.

urbenlegend commented 3 months ago

Mouse works fine for me here on Nvidia X11, but I can't seem to enable DLSS. When I launch the game, it warns me about a missing graphics card: image Maybe that has something to do with it if it can't detect my Nvidia GPU at all.

agurenko commented 3 months ago

Yeah, Fedora 40 KDE is now wayland only, so it looks exactly like the Star Citizen issue on wayland :(

agurenko commented 3 months ago

Just tried GE-Proton9.2 and no issues with a mouse there!

tooSadman commented 3 months ago

@urbenlegend if you try Proton 9.0 (beta) you'll get this message: image

but still you won't be able to enable dlss for some reason

urbenlegend commented 3 months ago

Odd, I am on Proton Experimental which should have changes up to Proton 9.0 (beta 15), but it still says no graphics card detected.

tooSadman commented 3 months ago

@urbenlegend for some reason with proton 9.0 I get different message than with proton experimental

kodatarule commented 3 months ago

I tried the game on my nvidia gpu under both X and Wayland, haven't had issues with the mouse. However as stated above right you cannot get neither DLSS nor reflex(which got merged in vkd3d) to work as there seems to be an issue with the game + nvapi(you can force enable it with PROTON_FORCE_NVAPI=1 %command% however the launcher doesn't show)

Operating System: EndeavourOS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-273-tkg-bmq (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

frozen-sea commented 3 months ago

I tried the game on my nvidia gpu under both X and Wayland, haven't had issues with the mouse. However as stated above right you cannot get neither DLSS nor reflex(which got merged in vkd3d) to work as there seems to be an issue with the game + nvapi(you can force enable it with PROTON_FORCE_NVAPI=1 %command% however the launcher doesn't show)

PROTON_FORCE_NVAPI=1 makes DLSS works on Proton 8 and 9 Beta since those show the correct GPU in the warning, but on Experimental/Exp bleeding edge it says "no installed graphics card" and doesn't work.

For me the bigger issue is the audio crackles and drops out a lot. Unfortunately it doesn't get fixed by just throwing some PULSE_LATENCY_MSEC at it.

Quantum 2048 (crackle): https://www.youtube.com/watch?v=jiuqG9opsgE Quantum 512 (no crackle): https://www.youtube.com/watch?v=E2CGF7kyugc Specs: https://gist.github.com/frozen-sea/5f1442ef850a341f2a6ce4f596d820fd

EnLaLuna91 commented 3 months ago

I get the information popup too. As it doesn't detect my GPU it doesn't let me enable DLSS, but even so, ignoring the warning, the game starts perfectly.

I tried starting the game with PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1, both individually and jointly.

This is my computer information: OS: Arch Linux x86_64 Kernel: 6.8.1-arch1-1 Session: Wayland KDE Plasma Version: 6.0.2 CPU: 13th Gen Intel(R) Core(TM) i7-13700KF GPU: nvidia RTX 4080 GPU Driver: nvidia-dkms GPU Driver version: 550.54.14-5 more computer info: https://gist.github.com/EnLaLuna91/11386a00303168814015a6035e2ab0a9

urbenlegend commented 3 months ago

Oddly enough, switching to Proton 9.0 beta was enough to enable DLSS for me. I didn't need to use PROTON_ENABLE_NVAPI or PROTON_FORCE_NVAPI at all. I wonder why @tooSadman couldn't enable it at all and why @frozen-sea required PROTON_FORCE_NVAPI. Weird. What are your driver versions?

Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 550.67 Product Name: X570 Taichi

matte-schwartz commented 3 months ago

I’m also experiencing extra crunchy audio, I’m using an OLED Deck and not a Nvidia rig though. Happens regardless of proton versions I’ve tried so far.

leanija commented 3 months ago

So far, the game has been crashing right at the intro video; it would play for a sec (choppily) and crawl to 1 FPS and then crash. Sometimes it gets further, sometimes it crashes right at the start. I tried Proton Experimental (bleeding edge); Hotfix; 8; 9 Beta; and also GE-9.2.

I also get the same messages on startup claiming either there is no GPU or drivers are outdated.

This on Desktop Linux: OS: Manjaro Linux x86_64 Kernel: 6.7.7-1-MANJARO DE: Plasma 5.27.11 CPU: AMD Ryzen 5 5600H with Radeon Graphics (12) @ 4.280GHz GPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q Memory: 15846MiB

have yet to test on Steam Deck

kodatarule commented 3 months ago

Which nvidia driver are you using leanija ? Also as I can see it's a laptop do you use a Prime setup to run it or directly the nvidia ?

Wolfgang0808 commented 3 months ago

I managed to resolve the audio crackling for the most part by setting a different buffer size for PipeWire. Setting it to 50 mostly resolved it for me.

Command to run: pw-metadata -n settings 0 clock.force-quantum 50

leanija commented 3 months ago

Which nvidia driver are you using leanija ? Also as I can see it's a laptop do you use a Prime setup to run it or directly the nvidia ?

yes, its a Lenovo Legion 5 laptop, indeed. Im currently running the proprietary nvidia drivers, v 550.54.14 (NVML version 12.550.54.14) – just stock settings, so no Prime setup (I had to google what that is, to be honest)

edit: the crashlog says this: 20:17:17:895 (00000292) > [Crash] Memory statistics: 20:17:17:895 (00000292) > [Crash] Total RAM = 15.5 GB (15846 MB) 20:17:17:895 (00000292) > [Crash] Avail RAM = 11.6 GB (11925 MB) 20:17:17:895 (00000292) > [Crash] Total virtual memory = 131072.0 GB (134217727 MB) 20:17:17:895 (00000292) > [Crash] Avail virtual memory = 131071.8 GB (134217533 MB) 20:17:17:895 (00000292) > [Crash] Total page file = 32.6 GB (33354 MB) 20:17:17:895 (00000292) > [Crash] Avail page file = 28.4 GB (29032 MB) 20:17:17:895 (00000292) > [Crash] Unhandled exception at address 0x00000000fd36dd30 (code: 0xc0000005): "Access violation"

tooSadman commented 3 months ago

Oddly enough, switching to Proton 9.0 beta was enough to enable DLSS for me. I didn't need to use PROTON_ENABLE_NVAPI or PROTON_FORCE_NVAPI at all. I wonder why @tooSadman couldn't enable it at all and why @frozen-sea required PROTON_FORCE_NVAPI. Weird. What are your driver versions?

Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 550.67 Product Name: X570 Taichi

I guess I need to put to clarification one moment here. I'm able to select 'DLSS' as an 'Upscale method' parameter, albeit it's not possible to select 'DLSS Frame Generation' option: image

@urbenlegend were you able to select 'DLSS Frame Generation'?

btw my specs: OS: EndeavourOS Linux x86_64 Kernel: 6.8.1-arch1-1 CPU: AMD Ryzen 7 3700X (16) @ 3.600GHz GPU: NVIDIA GeForce RTX 4060 Ti 16GB Memory: 32015MiB NVIDIA Driver: 550.54.14

frozen-sea commented 3 months ago

I managed to resolve the audio crackling for the most part by setting a different buffer size for PipeWire. Setting it to 50 mostly resolved it for me.

Command to run: pw-metadata -n settings 0 clock.force-quantum 50

Weird. I typically run a fixed 2048 quantum to work around crackling pretty much everywhere else, but lower quantum fixes this game. 1024 still crackles, but it disappears at 512.

kodatarule commented 3 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2013684447

I can try on a Lenovo Legion 5 as well rtx 3060, but I use the built in amd as main and nvidia only does heavy lifting(prime setup) and update you with results, but it will take some time. EDIT: only difference would be cpu the 7 6800H and running 680m gpu with rtx 3060 doing the heavy lifting

Saancreed commented 3 months ago

NVAPI situation appears to be this:

… or you could wait until the fix lands in Proton proper.

were you able to select 'DLSS Frame Generation'?

Obligatory "DLSS Frame Generation is not supported in Proton" in case you guys forgot or aren't aware yet.

leanija commented 3 months ago

Replying to #7590 (comment)

I can try on a Lenovo Legion 5 as well rtx 3060, but I use the built in amd as main and nvidia only does heavy lifting(prime setup) and update you with results, but it will take some time. EDIT: only difference would be cpu the 7 6800H and running 680m gpu with rtx 3060 doing the heavy lifting

ah, thats what you meant. I deactivated the amd gpu at some point when it was making problems with something

__

in the meantime, I tried the game on Deck, it runs fine! around 25-35 with medium/high settings, FSR Balanced the input for the account linking was a bit finnicky, and upon exiting it crashed, but otherwise I had a ~1.5 hr session that was fine. I did notice the mouse speed problem as well (Having played with mouse and keyboard as well as controller)

urbenlegend commented 3 months ago

I tried the dxvk-nvapi build @Saancreed linked with Proton Experimental and it worked a treat! I get both DLSS and Nvidia Reflex and it works great so far!

kodatarule commented 3 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2013990260

I was able to test it on the Legion 5, the game booted just fine, however: the mouse snapping on wayland super hard is indeed present I assume this is something with mesa as the desktop is being rendered by the AMD gpu instead of nvidia, nvidia only does the heavy lifting in performance. I can confirm that DLSS also worked just fine. Same nvidia driver 550.54.14, you already have the DE and distro above as it is the same as the desktop.

kivoli commented 3 months ago

The mouse issue is apparently a bug in Plasma 6 under Wayland, check out #7564.

The suggested workaround with --force-grab-cursor using gamescope works for me:

gamescope --force-grab-cursor -e -W 2560 -H 1440 --adaptive-sync -f %command%

Played over an hour now and did not encounter any other issues so far. What a time to be alive!

Alexatre commented 3 months ago

I managed to resolve the audio crackling for the most part by setting a different buffer size for PipeWire. Setting it to 50 mostly resolved it for me.

Command to run: pw-metadata -n settings 0 clock.force-quantum 50

This solution works for me too! Thanks, bro!

TheWyn commented 3 months ago

In GE, Hotfix, and Expermental with args PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr %command%

Receive this:

image

With no ability to turn on Dlss or reflex, but shows GPU

image

With Proton 9 Beta via Steam Client with same args:

GPU and Driver detected:

image

With option to turn DLSS and Reflex Latency Measurement Only on:

image

Saancreed commented 3 months ago

@TheWyn Please just use bleeding edge for the time being (until next Experimental or Hotfix is released). This way you'll have both DLSS and Reflex.

PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr

Fyi this does pretty much nothing, you might as well get rid of those options when using Proton 9.

leanija commented 3 months ago

Replying to #7590 (comment)

I was able to test it on the Legion 5, the game booted just fine, however: the mouse snapping on wayland super hard is indeed present I assume this is something with mesa as the desktop is being rendered by the AMD gpu instead of nvidia, nvidia only does the heavy lifting in performance. I can confirm that DLSS also worked just fine. Same nvidia driver 550.54.14, you already have the DE and distro above as it is the same as the desktop.

thank you for testing! unfortunately no dice for me so far; i tried switching to the prime-setup as well, but it made no difference, I keep getting the same crash

kodatarule commented 3 months ago

Makes me wonder if it could be something from the kernel or an entirely different setting from Manjaro, iirc back in the days when I was testing a few distros, manjaro had very weird behavior in some games(for example in the messenger the grapple hook rope was always visible even if you don't have it, you would think it's some DRM showing despite you playing the game from steam with proton ...)

ExecutorElassus commented 3 months ago

I can't get the game to start with my Radeon RX5700 XT. It says I don't have Shader Model 6.6, but this card (from the spec page) has Shader Model 6.7. What options do I need to pass to the client to get it to start? OS is gentoo-linux-6.8.0, GPU is AMD Sapphire Radeon RX 5700XT, 32GB RAM. UPDATE: forcing Proton to use version 8.0.5 gets me to the launcher screen, but then it crashes when it starts up the Sony splash screen. UPDATE2: adding PROTON_LOG=1 to the launch options gets the game to start, and gets me to the opening screen. However, the log file fills up at a rate of about 2GB/min, and once I click "New Game" the screen goes blank and the game eventually crashes. Gist of my system info: https://gist.github.com/ExecutorElassus/1ff02a8e036828f13c733b50dd0cf251.

marco-calautti commented 3 months ago

When moving the camera, the game stutters, even though the frame graph is flat and I keep steady 60 fps. This issue seems to also occur on Windows, but there the solution seems to be to disable hardware-based GPU scheduling. How does this workaround translate to proton? I have an AMD GPU with the mesa/RADV driver.

kisak-valve commented 3 months ago

Horizon Forbidden West (2420110) exception in a noexcept function

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7601. @radkin posted on 2024-03-24T09:52:28:

Compatibility Report

System Information

I confirm:

Symptoms

The launcher does not start

full output on the command line: ``` steam steam.sh[501524]: Running Steam on ubuntu 22.04 64-bit steam.sh[501524]: STEAM_RUNTIME is enabled automatically setup.sh[501853]: Steam runtime environment up-to-date! steam.sh[501524]: Steam client's requirements are satisfied tid(501934) burning pthread_key_t == 0 so we never use it [2024-03-24 09:48:24] Startup - updater built Mar 6 2024 20:27:25 [2024-03-24 09:48:24] Startup - Steam Client launched with: '{$HOME}/.local/share/Steam/ubuntu12_32/steam' minidumps folder is set to /tmp/dumps 03/24 09:48:24 Init: Installing breakpad exception handler for appid(steam)/version(1709846872)/tid(501934) [2024-03-24 09:48:24] Loading cached metrics from disk ({$HOME}/.local/share/Steam/package/steam_client_metrics.bin) [2024-03-24 09:48:24] Using the following download hosts for Public, Realm steamglobal [2024-03-24 09:48:24] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf' [2024-03-24 09:48:24] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf' [2024-03-24 09:48:24] 3. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in' [2024-03-24 09:48:24] Verifying installation... [2024-03-24 09:48:24] Verification complete UpdateUI: skip show logo Steam logging initialized: directory: {$HOME}/.local/share/Steam/logs XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe662e9c0 XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe662d1f0 /usr/share/themes/Yaru-magenta/gtk-2.0/main.rc:775: error: unexpected identifier 'direction', expected character '}' /usr/share/themes/Yaru-magenta/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant steamwebhelper.sh[501961]: === Sun Mar 24 09:48:25 AM WET 2024 === steamwebhelper.sh[501961]: Starting steamwebhelper under bootstrap sniper steam runtime at {$HOME}.local/share/Steam/ubuntu12_64/steam-runtime-sniper CAppInfoCacheReadFromDiskThread took 25 milliseconds to initialize Steam Runtime Launch Service: starting steam-runtime-launcher-service Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 502124 bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam BRefreshApplicationsInLibrary 1: 0ms BuildCompleteAppOverviewChange: 182 apps RegisterForAppOverview 1: 9ms RegisterForAppOverview 2: 9ms fsync: up and running. /bin/sh\0-c\\0PROTON_LOG=1 {$HOME}/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=2420110 -- [MY {$HOME}/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- {$HOME}/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- {$HOME}/.local/share/Steam/compatibilitytools.d/GE-Proton9-2'/proton waitforexitandrun {$HOME}/.local/share/Steam/steamapps/common/Horizon Forbidden West Complete Edition/HorizonForbiddenWest.exe'\\0 chdir "{$HOME}/.local/share/Steam/steamapps/common/Horizon Forbidden West Complete Edition" ERROR: ld.so: object '{$HOME}.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ERROR: ld.so: object '{$HOME}/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. ERROR: ld.so: object '{$HOME}.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ERROR: ld.so: object '{$HOME}/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ERROR: ld.so: object '/{$HOME}.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ProtonFixes[503936] INFO: Running protonfixes ProtonFixes[503936] INFO: Running checks ProtonFixes[503936] INFO: All checks successful ProtonFixes[503936] INFO: Using global defaults for "Horizon Forbidden West™ Complete Edition" (2420110) ProtonFixes[503936] INFO: No protonfix found for "Horizon Forbidden West™ Complete Edition" (2420110) Game 2420110 created interface STEAMAPPS_INTERFACE_VERSION008 / Game 2420110 created interface STEAMREMOTEPLAY_INTERFACE_VERSION002 / Game 2420110 created interface STEAMUSERSTATS_INTERFACE_VERSION012 / Game 2420110 created interface SteamFriends017 / Game 2420110 created interface SteamUser023 / Game 2420110 created interface SteamUser023 / User Game 2420110 created interface SteamUtils010 / Game 2420110 method call count for IClientRemotePlay::GetSessionCount : 1 Game 2420110 method call count for IClientUserStats::RequestCurrentStats : 1 Game 2420110 method call count for IClientAppManager::GetCurrentLanguage : 3 Game 2420110 method call count for IClientUtils::RecordSteamInterfaceCreation : 9 Game 2420110 method call count for IClientUtils::GetAppID : 10 Game 2420110 method call count for IClientFriends::GetPersonaName : 1 Game 2420110 method call count for IClientUser::BIsSubscribedApp : 2 Game 2420110 method call count for IClientUser::GetAuthTicketForWebApi : 1 Game 2420110 method call count for IClientUser::GetSteamID : 4 Uploaded AppInterfaceStats to Steam ```

Reproduction

click run

hwinfo bash command output hwinfo_2024_03_24_radkin.txt Intel vendor bash commands intel_graphics_details.txt Dell Product Spec DGFWDK3.csv dmidecode bash command dmidecode.txt

TheWyn commented 3 months ago

@Saancreed Got it going now. No args used, using bleeding and got dlss and reflex on. Turning reflex + boost on causes stutter after 15-20mins likely oc failing.

jansalleine commented 3 months ago

I'm not sure if this is a Mesa issue (again) like in several other DX 12 titles with RDNA 1. But trying to play Forbidden West leads to GPU hang here. As a "wild guess", because that fixed Talos Principle 2 back then I tried RADV_DEBUG=nodcc, but that didn't help in this case.

System Information

Symptoms

GPU hangs after the first loading screen when trying to start a new game.

Reproduction

ExecutorElassus commented 3 months ago

System Information

This looks a lot like my system, and I'm having a similar issue (I get to the starting screen, click "New Game" and then the screen goes black). A couple questions:

Thanks for the help!

jansalleine commented 3 months ago

I can only get past the launcher window if I have PROTON_LOG=1 set. Otherwise it crashes out. Do you have this issue?

I must admit I don't know what "launcher window" you mean. When I start the game there's no launcher window. It immediately goes to the Sony credit screen. Maybe there's a difference between steam window and big picture mode (which I use)?

If I use any other version of Proton than Proton-8.0-5, I get an error popup that my card "doesn't support Shader Model 6.6." This is not the case, as my card is almost exactly the same as yours. Do you get this error? How do you get around it?

No, I don't get this error. I only tried "Hotfix" (which is set automatically by steam) and "Experimental" and both behave the same here.

I see you're on another Kernal version and probably another Mesa version as well (?) – that could explain problems with the game detecting your hardware. Maybe this is also the reason you get the launcher, because the hardware detection fails.

TheWyn commented 3 months ago

After playing for a day, in Proton bleeding using fullscreen exclusive was giving me very random system lockup forcing me to hard shutdown (Sometimes in 30mins, sometimes in 2 hours). Using Reflex still caused stuttering after 5-10mins, adding Boost was instant game crash loading ingame. (Arch/X11/536.25/3090/Proton Experimental bleeding)

@jansalleine Should be this launcher window: image

jansalleine commented 3 months ago

@TheWyn Thanks for the info. Nope, I never saw that one. Pressing play in steam takes me directly into the game.

radkin commented 3 months ago

Thanks for the info. Nope, I never saw that one. Pressing play in steam takes me directly back to steam as the game always crashes with exception in a noexcept function as the only possible reason.

ExecutorElassus commented 3 months ago

Yes, what TheWyn posted. I can get that far if I use Proton-8.0-5; anything else I get an error message about missing Shader Model 6.6 But I also need to have PROTON_LOG=1 set in my launch options in Steam to get past that point. If I don't, the game quits out at the Sony splash screen. If I do have logging enabled, I can get to the game's own screen (the one with music and the links for "New Game," "Settings," etc. I can change settings there, but if I click "New Game," the screen goes black and it eventually quits.

dsalt commented 3 months ago

I can't get the game to start with my Radeon RX5700 XT.

Works fine with my RX 6600 XT using the default version of Proton (which, for this game, is currently Hotfix). (Mesa 24.0.2; Xfce on Devuan stable.)

UPDATE: forcing Proton to use version 8.0.5 gets me to the launcher screen, but then it crashes when it starts up the Sony splash screen.

It crashed (Sony logo) when I tried Proton 9.0. I don't have details handy, but it's probably the same bug.

I've noticed a few graphical problems outside the initially-mapped area. Nothing serious, though: dust being blown along seems only half-rendered (sharp line at one edge, suggesting that one triangle is missing), and dust devils are rendered with simulated translucency (dithering, single-bit transparency). Also, some of these:

[drm] Fence fallback timer expired on ring comp_1.2.0
[drm] Fence fallback timer expired on ring comp_1.2.1

but only after a few “interrupt took too long” messages (unknown if related).

ExecutorElassus commented 3 months ago

I figured out my problem. I also had amdvlk installed, and mesa apparently defaults to that. This was severely interfering with vkd3d-proton, causing crashes not only with H:FW, but also EVE Online. Uninstalled amdvlk, and now both run flawlessly (well, aside from occasional slowdowns because my rig is old). Amazing, I love this game so much.

jansalleine commented 3 months ago

Mh. I'm really not sure if my problem is driver related. There seems to be a problem with the shaders. I get a ton of Fossilize WARN: Pipeline library handle 0x000079115a58a990 is not registered. warnings and after I deleted the prefix the GPU now hangs when the game tries to compile shaders.

Also, for completeness sake: as I suspected above the "launcher" is only shown when you use steam in desktop mode. In big picture mode it is skipped.

EDIT: I also checked the first posts steam-*.log file from the one with the mouse problems. There are no such warnings in that log.

ensiform commented 3 months ago

I have been able to play this game on medium/low settings up until around level 14 with Nvidia latest and 6.7 kernel when I'm in a mission called Death's Door where I was getting hangs in the water escape sequence (avoided by swimming backwards) and then a firegleam part is now where I'm stuck. The game just hangs. Sound still runs but the logs don't seem to show much interesting things other than sound message spam once the game has hung. Proton-GE only one I have been able to play successfully. I'm not sure it's fixable if I'm running out of vram but I feel like the outside world should have more issues TBH with going over capacity.

chickazee4 commented 3 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2020331165

I have had the exact same issue — I'm actually very pleased to see that someone else exists out there with the same problem, since nobody else has known what I'm talking about across the various places I've asked so far. Personally, I have 11GB of VRAM and otherwise decent specs (GTX 1080 Ti), and changing graphics settings doesn't fix the issue, so I really don't think it's because of VRAM or other technical limitations, and if it is, it shouldn't be. Various logs point to a nonspecific "access violation" (and for me, the process gets killed when it stalls out with an equally uninformative Xid 8 kernel message from the Nvidia drivers), which could mean a lot of things. If it would help the Proton devs, I can share the logs and dumps that I've gathered in the process of investigating the issue myself.

Out of curiosity, which Proton-GE version were you able to get it to work with? I tried with 9-2 and it didn't help. It would be great to be able to finally get past this quest!

ensiform commented 3 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2024184755

9.2 works for me up until here but I'm not ruling out my system just can't handle it, as I'm actually on a 980 GTX or possibly hardware fault but it would be interesting to see if there is something wrong.

chickazee4 commented 3 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2024187222

Oh, I thought you meant you were able to get through this part using Proton-GE. Given that we're both using mid-2010s GTX cards and people with more recent Nvidia and AMD cards appear not to have this issue, maybe it has something to do with older Nvidia cards? A driver issue, or the game/dxvk trying to do something that older cards don't support?

(For what it's worth, switching Nvidia drivers to any version between 525 and 550, or to 470, which the game refuses to boot with at all, doesn't appear to fix the problem. If it is a driver issue, it's not a recent regression.)

radkin commented 3 months ago

A little progress with getting the launcher to start. Seeing the following in steam output if run from the command-line

fsync: up and running.
Fossilize INFO: Setting autogroup scheduling.
/bin/sh\0-c\0/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=2420110 -- /.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/.local/share/Steam/compatibilitytools.d/GE-Proton9-2'/proton waitforexitandrun  '/.local/share/Steam/steamapps/common/Horizon Forbidden West Complete Edition/HorizonForbiddenWest.exe'\0
chdir "/.local/share/Steam/steamapps/common/Horizon Forbidden West Complete Edition"
ERROR: ld.so: object '.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object /.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ProtonFixes[20994] INFO: Running protonfixes
ProtonFixes[20994] INFO: Running checks
ProtonFixes[20994] INFO: All checks successful
ProtonFixes[20994] INFO: Using global defaults for "Horizon Forbidden West™ Complete Edition" (2420110)
ProtonFixes[20994] INFO: No protonfix found for "Horizon Forbidden West™ Complete Edition" (2420110)
fsync: up and running.
Setting breakpad minidump AppID = 2420110
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561197974549180 [API loaded no]
Fossilize INFO: Overriding serialization path: "/.local/share/Steam/steamapps/shadercache/2420110/fozpipelinesv6/steamapprun_pipeline_cache".
pid 21277 != 21276, skipping destruction (fork without exec?)
Game 2420110 created interface STEAMAPPS_INTERFACE_VERSION008 /
Game 2420110 created interface STEAMREMOTEPLAY_INTERFACE_VERSION002 /
Game 2420110 created interface STEAMUSERSTATS_INTERFACE_VERSION012 /
Game 2420110 created interface SteamFriends017 /
Game 2420110 created interface SteamUser023 /
Game 2420110 created interface SteamUser023 / User
Game 2420110 created interface SteamUtils010 /
Game 2420110 method call count for IClientRemotePlay::GetSessionCount : 1
Game 2420110 method call count for IClientUserStats::RequestCurrentStats : 1
Game 2420110 method call count for IClientAppManager::GetCurrentLanguage : 3
Game 2420110 method call count for IClientUtils::RecordSteamInterfaceCreation : 9
Game 2420110 method call count for IClientUtils::GetAppID : 10
Game 2420110 method call count for IClientFriends::GetPersonaName : 1
Game 2420110 method call count for IClientUser::BIsSubscribedApp : 2
Game 2420110 method call count for IClientUser::GetAuthTicketForWebApi : 1
Game 2420110 method call count for IClientUser::GetSteamID : 4
Uploaded AppInterfaceStats to Steam
Fossilize INFO: Setting autogroup scheduling.

Found this with a Google Search. There was an update today (may be related) and I added this to the launch options LD_PRELOAD=$HOME/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so:$HOME/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so %command%

Then, the following pop up (usually the game just silently dies) Screenshot from 2024-03-28 16-21-41

ensiform commented 3 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2024201100

Definitely still happening even with v43 hotfix

Proton log if anyone wants to look at it steam-2420110.zip

TheWyn commented 3 months ago

Played for 10 hours yesterday with 1.0.43.0 patch and 0 crashes/stutter. Arch/X11/ Nvidia 536.25 Drivers/Rtx 3090/Proton Experimental bleeding. Dynamic resolution scaling was set to monitor refresh rate, vsync and reflex off.

Also updated the DLSS version from here: https://www.nexusmods.com/horizonforbiddenwest/mods/20

@chickazee4 @ensiform Kept an eye out for the "Deaths Door" mission and other then me forgetting to put the ladders down during the puzzle it came and went in the same sitting.

Settings used: ![image](https://github.com/ValveSoftware/Proton/assets/841141/207263c5-5cc8-439b-a46f-fde166a24cf0) ![image](https://github.com/ValveSoftware/Proton/assets/841141/e690559b-2b9c-4959-b38f-8c9cb705c42a)
jansalleine commented 3 months ago

Mh. Those fossilize warnings were probably because I also tried amd vlk at one point. After deleting the shader cache and proton prefix the warnings are gone.

But the main issue (GPU crash) remains. In a "fresh" environment the crash occurs after the ingame shader compilation step. Once you start again it happens at the same moment, but without the compilation step of course.

And when I look at protondb it seems there are a couple more people having this issue (even on RDNA2 cards – so it doesn't seem to be an RDNA1 issue). Also seems most of them are also Arch users with same kernel and mesa. I also tried the mesa-git aur and lts kernel package, but that didn't help either..

So I'm still not sure where the issue lies ... proton, vkd3d, mesa, kernel ... (?)