Open agurenko opened 5 months ago
Ancient77
commented
4 months ago Does anyone else have a weird bug where after playing for a while the voices just stop but all the other sound still works? Nvidia RTX 3070 - 525.147.05 Debian Testing/Trixie Proton Experimental
ensiform
commented
4 months ago Does anyone else have a weird bug where after playing for a while the voices just stop but all the other sound still works? Nvidia RTX 3070 - 525.147.05 Debian Testing/Trixie Proton Experimental
Yeah it happens for me too. I think it happened in HZD as well
ensiform
commented
4 months ago Replying to https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2027703511
Yes but you have a modern card, we have considerably older cards.
agurenko
commented
4 months ago Does anyone else have a weird bug where after playing for a while the voices just stop but all the other sound still works? Nvidia RTX 3070 - 525.147.05 Debian Testing/Trixie Proton Experimental
Yes, but it's not linux specific according to Steam Discussions. I had it yesterday and restart fixed it.
EphemeralDev
commented
4 months ago https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2020331165
I have the same issue, right after the boss battle in the water. If I stay above water it does not appear to crash, when i dive under water is when I crash. I've swam/dove throughout various bodies of water up to that point so I think it's something unique to the area. Game settings are mostly all medium and vsync is off
Some info on my setup:
dsalt
commented
4 months ago More info re. [drm] Fence fallback timer expired on ring comp_1.2.0 (for various values of 2 and 0): trigger unknown, but I see a brief pause 50s after each message. I suspect that the message is being output 10s and the brief pause 1 minute after the timer was set.
(Mesa 24.0.2, Linux 6.5.13, RX 6600 XT)
junx404
commented
4 months ago https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2013647730
I have the same problem on pretty much the same hardware, a Lenovo Legion 5. Tried with Proton 8.0-5, Experimental (bleeding edge), GE9-2, GE8-32 and 9.0 beta. Makes no difference. Some of them gives me a dialog box saying i have no GPU, some say my GPU is supported but runs an old version of the driver, 536. In reality i run 550.
OS: Arch Linux Kernel: 6.8.2.arch2-1 WM: bspwm CPU: AMD Ryzen 5 5800H with Radeon Graphics (igpu diabled in bios) GPU: NVIDIA GeForce RTX 3070 Mobile Memory: 16GB
Also tried to run it ono my Steam Deck and it starts and runs with no problems.
ensiform
commented
4 months ago Replying to https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2028513247
Not an expected workaround for most but I was able to get past it only by having the game installed on another PC and then finishing the cutscene at the firegleam on that level and then letting the save resume back on my PC. Been working mostly okay since. Few random things like the sound but no hangs that seem similar so far.
hrkrx
commented
4 months ago On my steam deck Proton GE-8 and 9 work, but if i access the menu and try to switch to the "quests" or "notes" the entire device crashes, after short flickering, then reboots.
here are my logs, I shortened one version to make it "more" readable, but it still is a lot. the log only contains the actions GameStart -> Continue -> Menu -> QuestLog -> Crash SHORT_steam-2420110.log FULL_steam-2420110.log
frozen-sea
commented
4 months ago On my steam deck Proton GE-8 and 9 work, but if i access the menu and try to switch to the "quests" or "notes" the entire device crashes, after short flickering, then reboots.
here are my logs, I shortened one version to make it "more" readable, but it still is a lot. the log only contains the actions GameStart -> Continue -> Menu -> QuestLog -> Crash SHORT_steam-2420110.log FULL_steam-2420110.log
Tried it out on mine and didn't experience any issues, but this was on default Proton and SteamOS Preview, so my suggestion would be to try that.
I've put about 18 hours into it on desktop and it's been rock solid there as well. 4070 Ti with driver 550.67, Proton Experimental bleeding-edge.
jansalleine
commented
4 months ago Okay, after lastest kernal and mesa updates (Arch Linux) I finally got it to run. Unfortunately with horrible foliage flickering. kernel 6.8.2-arch2-1, mesa 24.0.4-2, RX 5700
I worked myself through the game settings, but nothing really changes the flicker.
kisak-valve
commented
4 months ago Hello @jansalleine, it looks like the game sees both mesa/RADV and AMDVLK, and it's not immediately clear from your Proton log which Vulkan driver is being used by the game. So that there's no finger pointing between driver devs, can you test how the game behaves when it can only see one Vulkan driver vendor at a time?
jansalleine
commented
4 months ago @kisak-valve Well, I don't know why this was a problem in this game (I had set this up so that radv should be default), but uninstalling amdvlk completely fixed it. Thanks for the hint. Didn't see that because I was grep-ing for "amdvlk" / "radv" over the log file.
TheWyn
commented
4 months ago hrkrx
commented
4 months ago On my steam deck Proton GE-8 and 9 work, but if i access the menu and try to switch to the "quests" or "notes" the entire device crashes, after short flickering, then reboots.
here are my logs, I shortened one version to make it "more" readable, but it still is a lot. the log only contains the actions GameStart -> Continue -> Menu -> QuestLog -> Crash SHORT_steam-2420110.log FULL_steam-2420110.log
I fixed it, the "Shading at half rate" option causes the UI rendering to crash the system and it does not only affect the quest/notes tab (it's just a 100% chance to crash in those), it can happen randomly at any point where UI is rendered.
junx404
commented
4 months ago https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2028854128
Update on this issue: There was some update today but also a new proton update, but one of those made it possible for me to get into the game menu. Now it gets past the logos and instead crashes when i hit continue game. It's something ¯\(ツ)/¯
TheWyn
commented
4 months ago If you aren't using precaching leave it on the main menu, you'll see it build in the background (in ".config/nvidia" I think), it'll build up to around 1.3gb. It won't crash after.
On April 11, 2024 4:49:49 p.m. EDT, junx404 @.***> wrote:
https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2028854128
Update on this issue: There was some update today but also a new proton update, but one of those made it possible for me to get into the game menu. Now it gets past the logos and instead crashes when i hit continue game. It's something ¯\(ツ)/¯
-- Reply to this email directly or view it on GitHub: https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2050514445 You are receiving this because you were mentioned.
Message ID: @.***>
junx404
commented
4 months ago Thanks, with precaching on it doesn't crash! Was easier to track it that way. Now i can start the game but the graphics are very glitchy and laggy.
I still get this message right before the launcher pops up, could it have anything to do with it?
Replying to https://github.com/ValveSoftware/Proton/issues/7590#issuecomment-2050713541
radkin
commented
4 months ago There was an update (1.2.48.0) and the launcher starts when I'm running the game in compatibility mode "experimental". Everything looks great until it gets to the "compiling shaders" screen. The first time, progress bar started at about 75% and when it looked done the "spinner" animation above the bar froze. The music continued. After some time I restarted the game and the screen was blank for a while and the compiling shaders screen was back with a full progress bar. Then, after a brief period the spinner froze again. It's progress ..
Lukas-Heiligenbrunner
commented
4 months ago Launcher doesn't start on Intel Arc A770 LE GPU. Are there Vulkan features missing in mesa driver required by this game? Kernel 6.8.4; Mesa-git on Arch here. Can't read that much from log:
chickazee4
commented
4 months ago Replying to #7590 (comment)
For those without access to a different GPU, I just did some more troubleshooting and the Death's Door crash point affecting GTX 1000 series graphics cards can be avoided by downgrading Nvidia drivers to major version 515 — after doing that, the quest and subsequent cutscene run smoothly. I originally only downgraded step-by-step to 525, which has the issue, and then skipped down to 470 (since the versions between 470 and 525 are not packaged by my distribution anymore), which was too old for the game to start on, so I just barely missed the Goldilocks zone.
hrkrx
commented
3 months ago I have now 20h+ played on a steamdeck (non oled) and i have to say it is fully playable. 30+ FPS in 98% of game play situations. Only when flying and there are very many things in view the FPS can drop below 20
I hasn't bothered me much so i did not try any special settings to mitigate that, but if one tries, there is surely a way to get a constant 30+ FPS
My settings:
30Hz
framecap
no tearing
no half shader
no tdp limit
no manual gpu freq
auto scaling
FSR (max / 5)
Game settings:
texture Res High
texture filter Tri
shadows Very Low
screenspace shadows no
Env. Occlusion no
Screenspace Reflections no
details Very Low
Hair Very Low
People Very low
Terrain/Water/Clouds Very Low
Transparency Default
Parralax Occlusion no
FOV 0
depth of field no
leanija
commented
3 months ago I've not commented here in a while since I played through the game on Windows in the meantime; but I tried the latest patches and Proton versions recently, and it still had the same stuttering problems. It would reach gameplay, but would be unplayable. It feels like its restarting the game engine (most likely not a correct term). I noticed the same behaviour in games in Horizon Zero Dawn (here, I also notice speeding up: sometimes, menu changes count require a confirmation and have a 15 second countdown before an automatic revert: this can happen within seconds) and the Ubisoft games Assassins Creed Valhalla and Immortals Fenyx Rising - both these games appear to reset the light sources every second or so. I should maybe try Death Stranding with also uses the Decima engine like HFW and HZD (while ACV and IFR uses Ubisofts engine). I assume these two engines in combination with the current Nvidia drivers, and maybe Manjaro and/or my hardware specifically cause this. Im unsure its something that can even be fixed in Proton itself, but who knows; I felt like I should just add this to my other comments.
ensiform
commented
3 months ago Proton-GE 9.5 introduced a regression for my system with the 980GTX whereby I get an error from the game during map load that I've run out of memory in pagefile/vram. Forcing GE 9.4 instead of using the AUR Proton-GE always updated version still works. I assume this could be tied to changes in upstream vkd3d but not sure. It no longer complains about the lack of a video adapter on startup with 9.5 but yeah can't actually load into the game world.
kisak-valve
commented
3 months ago Hello @ensiform, can you check how the game behaves with Proton Experimental as another data point?
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.
hrkrx
commented
3 months ago I have now 20h+ played on a steamdeck (non oled) and i have to say it is fully playable. 30+ FPS in 98% of game play situations. Only when flying and there are very many things in view the FPS can drop below 20
I hasn't bothered me much so i did not try any special settings to mitigate that, but if one tries, there is surely a way to get a constant 30+ FPS
Additional Remark:
The DLC burning shores seems to be harder on the hardware, so I noticed more drops below 20FPS while playing
EphemeralDev
commented
2 months ago Update to my previous post
Basically i've updated to the latest ubuntu and new drivers. I confirmed that the crash still exists.
However thanks to a ProtonDB report, I was able to successfully complete Deaths Door without a crash! The fix was to add the following launch option VKD3D_DISABLE_EXTENSIONS=VK_EXT_descriptor_buffer %command%. Haven't done any further testing, unsure if the launch option is necessary for the remainder of my playthrough. I plan to leave it unless advised otherwise.
zaps166
commented
2 months ago I'm playing on DualSense 5 gamepad - no rumble, but R2 button has haptics :roll_eyes:
Hadrianneue
commented
1 month ago game got a FSR3 frame gen update but it isn't working properly on linux, not generating many frames, works fine on windows 10.
Even triggered a gpu timeout but i missed that crash log.
kisak-valve
commented
1 month ago FSR 3.1 causes serious frame pacing issues that are not visible in mangohud in Horizon: Forbidden West under Proton
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7883. @tfinnegan937 posted on 2024-07-09T22:16:01:
FSR 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.
tfinnegan937
commented
1 month ago game got a FSR3 frame gen update but it isn't working properly on linux, not generating many frames, works fine on windows 10.
Even triggered a gpu timeout but i missed that crash log.
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.
Hadrianneue
commented
1 month ago game got a FSR3 frame gen update but it isn't working properly on linux, not generating many frames, works fine on windows 10. Even triggered a gpu timeout but i missed that crash log.
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
Hadrianneue
commented
1 week ago 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 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
49109.713:0124:04ac:warn:threadname:NtSetInformationThread Thread ID 04b0 renamed to L"AMD FSR Presenter Thread"
49109.714:0124:0128:warn:vkd3d-proton:d3d12_command_list_update_graphics_pipeline: No graphics pipeline bound, skipping draw.
49109.714:0124:0128:warn:vkd3d-proton:d3d12_command_list_DrawInstanced: Failed to begin render pass, ignoring draw call.
49109.715:0124:0128:warn:threadname:NtSetInformationThread Thread ID 04b4 renamed to L"AMD FSR Interpolation Thread"
49109.715:0124:04b4:warn:threadname:NtSetInformationThread Thread ID 04b8 renamed to L"AMD FSR Presenter Thread"FSR3FG is likely working fine but for whatever reason the generated frames are not being drawn properly
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.