Horizon Forbidden West (2420110) #7590
Comments
kisak-valve
added
the
Game compatibility - Unofficial
|
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: |
|
Yeah, Fedora 40 KDE is now wayland only, so it looks exactly like the Star Citizen issue on wayland :( |
|
Just tried GE-Proton9.2 and no issues with a mouse there! |
|
@urbenlegend if you try Proton 9.0 (beta) you'll get this message: but still you won't be able to enable dlss for some reason |
|
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. |
|
@urbenlegend for some reason with proton 9.0 I get different message than with proton experimental |
|
I tried the game on my nvidia gpu under both X and Wayland, haven't had issues with the mouse. Operating System: EndeavourOS |
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 |
|
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 This is my computer information: |
|
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 |
|
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. |
|
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: have yet to test on Steam Deck |
|
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 ? |
|
I managed to resolve the audio crackling for the most part by setting a different buffer size for PipeWire. Command to run: |
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: |
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: @urbenlegend were you able to select 'DLSS Frame Generation'? btw my specs: |
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. |
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. |
|
NVAPI situation appears to be this:
… or you could wait until the fix lands in Proton proper.
Obligatory "DLSS Frame Generation is not supported in Proton" in case you guys forgot or aren't aware yet. |
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 |
|
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! |
I was able to test it on the Legion 5, the game booted just fine, however: |
|
The mouse issue is apparently a bug in Plasma 6 under Wayland, check out #7564. The suggested workaround with Played over an hour now and did not encounter any other issues so far. What a time to be alive! |
This solution works for me too! |
|
In GE, Hotfix, and Expermental with args Receive this:
With no ability to turn on Dlss or reflex, but shows GPU
With Proton 9 Beta via Steam Client with same args: GPU and Driver detected:
With option to turn DLSS and Reflex Latency Measurement Only on:
|
|
@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.
Fyi this does pretty much nothing, you might as well get rid of those options when using Proton 9. |
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 |
|
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 ...) |
|
FSR 3.1 causes serious frame pacing issues that are not visible in mangohud in Horizon: Forbidden West under Proton Issue transferred from #7883. Compatibility Report
System Information
I confirm:
SymptomsFSR 3.1 seems to be broken under Proton for Horizon: Forbidden West. This is not true for every game -- only this specific title, and only under Proton. I do not experience this issue on Windows. When enabling FSR 3.1 Frame Generation, steam and mangohud will report a stable framerate, but the framepacing of the image gets noticeably bad, with microstutters and an overall lack of smoothness. Disabling Frame Generation fixes the issue. This issue is NOT visible in mangohud, or in the steam framerate counter. According to those reports, the performance is fine. The issue is extremely noticeable to the naked eye, though -- the game looks like it's running at 30 FPS. Reproduction
|
As per the report that kisak-valve copied over here, I'm experiencing the same issue. It seems to actively cause frame pacing issues when enabled. |
btw this issue doesn't seem to be driver related, tested on amdvlk as well and pretty much got the same results (performance wise, amdvlk has graphical issues), FSR3 FG is not generating half as many frames as it does on windows |
btw did you remembered to enable FSR3 FG when logging that? i just checked now and i get this log spam, which doesn't appear on ratchet & clank: rift apart, which also has the same FSR3 FG version FSR3FG is likely working fine but for whatever reason the generated frames are not being drawn properly |
|
commit HansKristian-Work/vkd3d-proton#2082 did improve frame generation reasonably, not up to par with windows still. |
|
Horizon Forbidden West Freezes at Compiling Shaders Screen Issue transferred from #8188. Compatibility Report
System Information
I confirm:
SymptomsThis issue does not happen on my Steam Deck or my Gaming Laptop with Nvidia running Arch.The game starts and launches properly. When you either start a new game or continue a previous game the "compiling shaders" screen will then come up but freeze shortly after. The following lines are some errors I saw in the terminal when running steam from there.
I tracked down the pNext and sType as to something to do with vulkan variables but didn't dig much farther than that. ReproductionI can reproduce this on my PC every time I install this game. It even happens on other distros such as Ubuntu and Fedora.
|
|
After a recent Steam client update (since last week) I've been running into what seems like an out-of-memory problem. Several things happen: multiple sound channels cut out (background music, spoken dialogue, environmental sounds like wind; but not footsteps or animal sounds), then I see a whole lot of tall grass in places where it shouldn't be -- like all over a settlement --, the world map won't load (I just see a black screen with the animated cauldrons icon in the bottom left), and then lastly the textures of clothes get scrambled. |
|
Many other users reported a bug similar to yours - including myself (it's probably the same). The only fix was restarting the game. Honestly I didn't try with an older GE-Proton version though... |
|
This only started for me last week. However, I had many of the same problems -- texture corruption, prolific tall grass -- before FSR 3.1 was added. Horizon Forbidden West accumulates graphics/audio errors and then crashes Issue transferred from ValveSoftware/steam-for-linux#11462. Your system information
Please describe your issue in as much detail as possible:Since last week's update the game rapidly accumulates the following errors:
Steps for reproducing this issue:
I did not have any of these problems after the game updated to its current version over the summer. This only started happening after the Steam client updated last week. I am using GE-Proton-9.{11,15,19}, but that doesn't seem to have any effect. |
|
@ExecutorElassus Please launch the game with stock proton 9.0-3 and leave the game's launch parameter with just the following: |
|
steam-2420110.log I don't know if it matters, but I also see the following errors repeated in the console when starting the client: The first pair (for the "setenv" count) is new. |
|
@kisak-valve , thank you for moving the issue. Sorry for mis-filing it. |
|
Hello @ExecutorElassus, |
|
Hi @kisak-valve , thanks for the tip. Do I need to reboot after changing that file? I'm using PAM, so I changed the limits.conf file and re-logged my user. But that doesn't seem to have helped. |
|
That's a different resource limit, give something like |
|
Still no joy :( |
|
@ExecutorElassus I haven't reproduced the issue yet, at least where I am in the game, which isn't far from the start. What mesa version are you using? and I don't think you can revert client updates, you can just choose between the default and beta clients. |
|
@simifor I'm using mesa-24.2.6 with the following features: |
|
@ExecutorElassus nothing seems to be out of the ordinary there, but I can't reproduce the issue on my setup and haven't seen other reports about this. Just to check it off the list, have you tried to verify the game files? |
|
@simifor I verified everything just now, though it didn't find any issues. But I'll try playing again and see if it runs into any problems (I hope you're enjoying the game, btw). So far, since last week, I've only played long enough to fast-travel back to the mountains west of The Base, said, "yup, there's tall grass everywhere where it shouldn't be," and exited again. Maybe that's just a generic texture bug, but I don't think so. As for other reports, take a look at daniele-athome's post just above mine from two days ago: it links to the protondb page where lots of people are reporting issues similar to mine. This message also appears when I reset it to use stock Proton, and my client is currently set to use 9.19, not 9.11, so I'm not sure what this message is. Is there something here I can safely delete? |
|
UPDATE: hrm. Welp, after a couple days, in which I didn't play it at all, I did a couple things. One, I verified all the files, as you suggested. But then I found that I had a config file from pipewire (needed for the ardour audio editor) that sets a hard limit on memlock of 8152 kbytes. I set that to unlimited. I have no idea if that makes any difference (I still get the mmap error), but I just played the game for maybe 40 minutes without any issues with textures, music, the map, etc. I dunno. I got nuthin'. I'll try a longer play session in a day or two and see if I can cause any errors. |
|
I see the launcher but as soon as I click on "Play" it crashes. Rebooting into the standard Debian kernel version 6.1 did not help. System Information
I confirm:
steam-2420110.log.gz |
|
Hello @gurubert, |
Thank you! After installing the newer mesa package from Debian backports the game starts and runs smoothly. Never thought of that. |
|
Hey, somewhat unrelated, in that nothing is currently breaking on my build of the game (though I do still occasionally get the tall-grass-everywhere bug sometimes after fast-traveling): is there anywhere where we can see a changelog of patches for the client? Because my game client seems to have installed a patch every day this week and I'm curious what was being changed. |
|
Also, another addendum (I'm not sure if this is the correct place to report it): there is still a bug in my version that Erund, Alva, and Kotallo don't correctly despawn after you talk with them after Singularity. I'm not sure if this is because I didn't go talk to them until after I was finished with the Burning Shores, or if that's always going to be an issue. I'll try to remember on this, my fifth playthrough, to talk to them before I head to the Burning Shores, to see if it works correctly then. But it's also clear that the conversations with them are rendered differently (it uses the gameplay engine rather than the cinematic one you see on all other conversations) so maybe it goes deeper than that. Also, has the bug with the explosive canisters/traps been fixed (previously, only damage from the first one or two canisters/traps would apply), or is that still an issue? |
and others
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.
The text was updated successfully, but these errors were encountered: