ValveSoftware / Proton

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

Ghost of Tsushima DIRECTOR'S CUT (2215430) #7735

Open Niedzwiedzw opened 4 months ago

Niedzwiedzw commented 4 months ago

Compatibility Report

System Information

I confirm:

The game launches up to the main menu, but gamepad is not detected.

EDIT: Managed to finish the prologue with a single crash caused by a rogue desktop notification , other than that runs very well

kisak-valve commented 4 months ago

Hello @Niedzwiedzw, please copy the compatibility report template from https://github.com/ValveSoftware/Proton/issues/new?template=compatibility-report.md to this issue report and fill out the requested details.

Bitwolfies commented 4 months ago

Curious if the lack of working MP is due to proton inaccuracies and can be fixed overtime, or a conscious block from Sony/Anticheat.

Niedzwiedzw commented 4 months ago

Curious if the lack of working MP is due to proton inaccuracies and can be fixed overtime, or a conscious block from Sony/Anticheat.

what's MP?

Bitwolfies commented 4 months ago

Curious if the lack of working MP is due to proton inaccuracies and can be fixed overtime, or a conscious block from Sony/Anticheat.

what's MP?

Multiplayer, devs made a post before release taking about how it runs fine on deck but marked unsupported due to broken multiplayer, their wording implied it was "only supported on windows" but didn't elaborate if this was a intentional choice or just due to proton bugs.

Really hope they didn't do something like disable the option on deck if it's a fixable proton bug.

hamburgerghini1 commented 4 months ago

screenshot_2024-05-16T20:39:53 Got this error, intro logos played after that the game froze. Proton Experimental & Arch

Bitwolfies commented 4 months ago

screenshot_2024-05-16T20:39:53 Got this error, intro logos played after that the game froze. Proton Experimental & Arch

May be related to https://gitlab.freedesktop.org/drm/amd/-/issues/3343

christofdamian commented 4 months ago

I first got Wine errors before the main menu, now it is going a bit further and stops in the middle of the intro scene. This does look similar to the related issue @Bitwolfies mentioned above.

image

dennis1248 commented 4 months ago

For me the game seems to run fine aside from controller issues. I am using a Dualsense controller and in-game whenever I press a button it rapidly switches between Xbox and Playstation prompts, and it press buttons many times repeatedly. Same issue both wired and wireless. Proton experimental. I am going to try some different versions to see if it makes a difference.

Edit: Mmm... it seems to do this with all input devices, might be an issue with the game itself.

Edit: It was a Steam bug, I restarted the client and the problem is now gone. Unsure if Steam Input related, disabling it made no difference in testing.

Bitwolfies commented 4 months ago

Confirmed the game locks out the multiplayer if they detect you're on deck, if it's just a proton bug preventing the mp, it might forever be disabled on deck if a fix isn't out soon enough, devs really don't like to undo their weird hacks.

powerofthe69 commented 4 months ago

To add onto issues I'm experiencing with this game:

I'm using Proton Experimental on Fedora Silverblue 40 with the Flatpak mesa version 24.0.6 drivers. I have an AMD 7900 XTX, and a 7900X3D.

I have horrible flickering and pop-in that my friend on Windows using a 4070 Ti isn't experiencing. Here is a short clip of the issue in question: https://streamable.com/7eha3o

There is also a separate issue experienced when turning on AMD FSR 3 Frame Generation, which is the frame timing being extremely jittery and occasionally leading to crashes.

This is present on Proton Experimental, 9, 8, and GE 9-5 at least. I haven't tested further versions.

Breaking it down as per the compatibility report template:

GPU: AMD Radeon RX 7900 XTX Kernel: 6.8.9-300.fc40.x86_64 (Fedora Silverblue 40) Video driver version: Mesa 24.0.6 Proton Version: Experimental, 9, 8, GE 9-5

Proton Log output attached from a recent FSR 3 Frame Generation crash. steam-2215430.log

christofdamian commented 4 months ago

I enabled the 4G memory thing in my BIOS, now it works, and the Wine errors are not happening any more. This is apparently a problem with recent kernels combined with this BIOS option. Thanks for the link @Bitwolfies You might want to try this too @hamburgerghini1

hjpaul7 commented 4 months ago

For anyone on Nvidia, 525/535 drivers results in a bunch of missing textures. Latest Nvidia drivers solve it.

K0bin commented 4 months ago

@powerofthe69 Do you still have your save standing at that spot or close to it? If so, can you upload it?

powerofthe69 commented 4 months ago

@K0bin I had to make a new manual save next to the outpost, but I can upload that now.

To be clear, this is also happening on the title screen and everywhere else in the overworld as well. I just thought it was most egregious at that one fence. Here is a link to the title screen flickering, and here is another video approaching the outside of the same outpost in the original video I'd posted.

Here is the save file I made - I had to rename it to .log to be able to upload it here for some reason, so this file should be modified to be .sav instead. manual_0002.log

Hadrianneue commented 4 months ago

MP does not work, pssdk tries to install itself but it ends up removing itself when launched, manually initializing the pssdkappmgr.exe results in wine not supported error, bypassing it by hiding wine version still gives pretty much the same error image

Bitwolfies commented 4 months ago

MP does not work, pssdk tries to install itself but it ends up removing itself when launched, manually initializing the pssdkappmgr.exe results in wine not supported error, bypassing it by hiding wine version still gives pretty much the same error image

Installing via standard wine actually brings up a crash window with a crashtrace, which ive linked below. backtrace.txt

Though you mentioning an explicit "wine not supported" error message really makes me wonder if they borked this on purpose.

simifor commented 4 months ago

@powerofthe69 I tried on my rdna2 gpu and I haven't seen anything off on either mesa 24.0.7 or .6 (just in case). I haven't seen any oddities with the frametimes when FG is enabled, but I haven't used it enough to rule out crashes.

powerofthe69 commented 4 months ago

@simifor thank you for letting me know. I'm currently verifying my files then going to try again. Maybe something got messed up during preload. If the issue persists, I'll do a complete uninstall / reinstall and see if that helps.

clnne commented 4 months ago

I'm not sure if this problem is related to Proton itself, but this game keeps freezing/crashing every 2-4 minutes and I need to kill the process. This is not happening on any other game. I am running Proton Experimental.

Every time it crashed, I kept getting this error message:

[2024-05-17 19:58:49] Nothing to do radv: GPUVM fault detected at address 0x8000a45ba000. GCVM_L2_PROTECTION_FAULT_STATUS: 0x501430 CLIENT_ID: (SQC (data)) 0xa MORE_FAULTS: 0 WALKER_ERROR: 0 PERMISSION_FAULTS: 3 MAPPING_ERROR: 0 RW: 0

GPU: AMD Radeon RX 7900 XTX Kernel: 6.7.12-amd64 Video Driver: Mesa 24.0.7-1

powerofthe69 commented 4 months ago

@clnne crashes like that happened to me only while using FSR 3 Frame Generation. If you have it on, that's probably the culprit. There's a Reddit post about it as well.

clnne commented 4 months ago

@powerofthe69 Thanks, but I've already tried that, but unfortunately it didn't help.

simifor commented 4 months ago

@powerofthe69 Some further testing with FG and over 1 hour and a half session and no crashing. However, I am noticing some jittering, specially when in battle and other dynamic situations where the framerate varies.

Checking on windows, the framerate is equivalent to linux with both FG on and off, however, with FG on, the frame times seem a bit more consistent than on linux. At least with my rx 6600.

powerofthe69 commented 4 months ago

I was able to install mesa-git finally, so now my current driver version is 24.2.0-devel, but the issue is still persisting with the intense flickering, and it seems no better at all.

structnull commented 4 months ago

getting this error randomly on arch linux using steam flatpak

image

JonathanxD commented 4 months ago

@powerofthe69 Some further testing with FG and over 1 hour and a half session and no crashing. However, I am noticing some jittering, specially when in battle and other dynamic situations where the framerate varies.

Checking on windows, the framerate is equivalent to linux with both FG on and off, however, with FG on, the frame times seem a bit more consistent than on linux. At least with my rx 6600.

@simifor Are you running under Gamescope with Mangohud? I was running with:

MANGOHUD=1 gamescope -f -e --adaptive-sync -W 2560 -H 1440 -- vk_radv %command%

And the frame pacing was atrocious with FG3 enabled on my RX6800. It went from stable 90fps to unstable 110fps, which was pretty obvious that something was messing with FSR3 FG. With V-Sync enabled (which is the recommended for FSR3 FG) things improved a bit, but it was still very weird, going from 90fps to 110fps instead of doubling. I tried to put a FPS limit directly on Manghud and the game would always run 20fps lower than the set limit.

So I tried running without Mangohud (which is known to cause performance problems in some cases) and Gamescope, now FSR3FG is working flawlessly, actually, it's the best implementation of FSR3FG I've ever seen (it's actually FSR 3.1). It still need V-Sync ON as recommended by AMD, otherwise you'll get a weird motion effect whenever the frame rate drops.

edit: a minor problem that I've noticed is that the game renders some moving UI elements at Native Frame Rate, if you have a high enough frame rate natively, this is not noticeable, but for lower native frame rates, the UI looks like it's "skipping".

powerofthe69 commented 4 months ago

@simifor I found last night that the frame times become more consistent when V-Sync is disabled. This is most likely due to the frame gen producing higher frames than my monitor's maximum refresh rate. Nvidia's DLSS 3, however, automatically turns off V-Sync and doesn't allow you to modify it at all. AMD's FG doesn't turn it off and you have to do that manually, but when I did that I no longer had jitteriness nor did I have any crashes while FG was enabled.

ghtesting2020 commented 4 months ago

Does anyone get graphics driver warning when launching? Playing via Bottles Steam. The game gives me completely different versions than what is true. I'm on latest nvidia Linux drivers 550.78 When launch game a warning says blahblah recommend at least 552.44 I will have issues current driver which is 552.12. Does Proton/Wine map Linux drivers to a different version number? Game runs perfectly fine I just don't like the warning pop up every time I launch (often as i'm an Uber driver) and I must dismiss it by pressing OK.

matte-schwartz commented 4 months ago

@ghtesting2020 yes I get that warning on my NVIDIA rigs as well, probably something that will be worked out with a Proton update hopefully.

Niedzwiedzw commented 4 months ago

apparently disabling motion blur reduces the freezes. freezes tend to happen when I open the game menu / map while character is doing something (landing or something) - seems like a bug in the game intself

Atmudia commented 4 months ago

I get a random freeze and then I have to restart the game, sometimes it's during startup, sometimes while playing. Here steam logs: steam-2215430.log

Niedzwiedzw commented 4 months ago

I get a random freeze and then I have to restart the game, sometimes it's during startup, sometimes while playing. Here steam logs: steam-2215430.log

yeah same here, its getting worse as the game progresses it seems, at this point it freezes every time I open the map, I'm on second island

Atmudia commented 4 months ago

I get a random freeze and then I have to restart the game, sometimes it's during startup, sometimes while playing. Here steam logs: steam-2215430.log

yeah same here, its getting worse as the game progresses it seems, at this point it freezes every time I open the map, I'm on second island

The worst thing is that even the game won't show the Sony logo and it will crash anyway

Atmudia commented 4 months ago

and randomly as frick

simifor commented 4 months ago

@powerofthe69 for the record, I already had vsync disabled as the game ran over 60 fps for me and it'd have affected comparisons in the end by capping what the game can show. That said, I retested in fairer conditions by having both being after a fresh boot and the result is basically the same to my eyes.

@JonathanxD I wasn't using gamescope.

@KomiksPL Any particular reason you're using GE proton for this title? The current default for this game is proton experimental, do you get such issues there as well?

@Niedzwiedzw I haven't had the game freeze on me, tried to show and dismiss the map continuously to no effect, with motion blur enabled. You say that progression might be affecting frequency, but were the issues present from the start? Could you upload a save file for me to check? And could you upload a proton log where the issue occurs? Simply add PROTON_LOG=1 %command% to the game's launch parameters and next time you run the game you'll get a steam-2215430.log in your home folder.

Atmudia commented 4 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/7735#issuecomment-2119382445

I have the same error on Proton Experimental and GE

Atmudia commented 4 months ago

From what I noticed, this bug occurs when you run FSR3, without it the game does not seem crash.

powerofthe69 commented 4 months ago

So I'm still having the issue with the awful pop-in to the point where I've shelved the game because it's detrimental to the experience. However, in doing some digging in the logs, I noticed that my logs for Horizon Forbidden West (another Nixxes port) display a driver version for my AMD GPU, but my logs for Ghost of Tsushima do not. My logs for Ghost of Tsushima also explicitly state "Loading ADL... Failed to load ADL!" earlier in the logs. I'm attaching my Ghost of Tsushima logs.

The lines in question are lines 39 & 40 and line 153. Can someone else (on AMD) please compare their own logs to mine? Ghost of Tsushima DIRECTOR'S CUT.log

NOTE: These are the only discrepancies between my GoT logs and my HFW logs. On Mesa 24.0.6 Flatpak drivers, using Proton Experimental, tested within minutes of each other.

E3FxGaming commented 4 months ago

@powerofthe69

Can someone else (on AMD) please compare their own logs to mine? Ghost of Tsushima DIRECTOR'S CUT.log

My Ghost of Tsushima DIRECTOR'S CUT.log

Your and my log file compared with Kdiff3 (timestamps at the beginning of lines removed, so that the comparison can actually identify equal lines)

powerofthe69 commented 4 months ago

Thanks so much for going the extra mile to compare things. I'm starting to wonder if this might be an issue specific to the Flatpak runtime for Mesa as it seems like those on Arch that (I assume) are running system libraries aren't having these issues, and I don't think anyone else has specified that they're using Flatpak either....

I should think that if someone else is using Flatpak then we should see similar issues, rather than it only be me, since we'd have the exact same libraries.

powerofthe69 commented 4 months ago

I layered the system version of Steam on Fedora Silverblue 40 and all my visual glitches that I'd been experiencing lately have been resolved. No more flickering in Ghost of Tsushima, no more weird lighting shimmering on certain textures like skin in basically any game, and no more flickering in Lords of the Fallen.

PSA: Steam Flatpak is botched 🤷🏻‍♂️

kjeremy commented 4 months ago

I get a random freeze and then I have to restart the game, sometimes it's during startup, sometimes while playing. Here steam logs: steam-2215430.log

yeah same here, its getting worse as the game progresses it seems, at this point it freezes every time I open the map, I'm on second island

I just ran into this after playing the game for over 8 hours on my OLED Steam Deck.

simifor commented 4 months ago

I'm curious if anyone is having freezing issues after today's update. I managed to get them twice before today's update, but given that it took 90 minutes each time, it's not something I can check easily for what's to blame for them.

To be precise, the freezing issue I observed allowed some environment sound to keep playing from the game (though nothing related to player input), it didn't affect the gpu, or the desktop environment, and there were no other effects to the system after closing the game.

afettouhi commented 4 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/7735#issuecomment-2118137769

I am having the same issue under Arch (Plasma6) with a 1080 GTX card (FRS 3 is off).

afettouhi commented 4 months ago

I'm curious if anyone is having freezing issues after today's update. I managed to get them twice before today's update, but given that it took 90 minutes each time, it's not something I can check easily for what's to blame for them.

To be precise, the freezing issue I observed allowed some environment sound to keep playing from the game (though nothing related to player input), it didn't affect the gpu, or the desktop environment, and there were no other effects to the system after closing the game.

After the new patch the freezing is worse for me now to where I can only play for 1 or 2 minutes.

simifor commented 4 months ago

@afettouhi does audio keep playing when the game freezes? Can you add logs for the game? Go to the game/s properties on steam and add the following to launch parameters PROTON_LOG=1 %command%, this will create a file called steam-2215430.log, upload it here. If the file is too big, then zip it before uploading it.

afettouhi commented 4 months ago

@afettouhi does audio keep playing when the game freezes? Can you add logs for the game? Go to the game/s properties on steam and add the following to launch parameters PROTON_LOG=1 %command%, this will create a file called steam-2215430.log, upload it here. If the file is too big, then zip it before uploading it.

Yes, the audio keeps running.

afettouhi commented 4 months ago

Here is the steam log output steam-2215430.zip

marco-kretz commented 4 months ago

I tried several Proton versions, different combinations of Upscaling/FG. The only configuration that makes this game an absolute dream with zero crashes and/or microstutters is the following:

If you are, like me, on NVIDIA, DISABLE NV-API!! This is night and day. With NV-API enabled I get bad frametimes with DLSS/FSR3 and only ~120FPS. Without tho, I get completely stable frametimes and contant 130-150FPS.

For Proton8, just don't add PROTON_ENABLE_NVAPI=1, for Proton9 add PROTON_DISABLE_NVAPI=1 to the start command.

My System:

I don't know why this behaves the way it does. One would guess DLSS and NV-API would increase performance on an NVIDIA card, but in this case it does not. Hope this helps some people.

EDIT:

Also works with Proton9 when setting PROTON_DISABLE_NVAPI=1

robotman40 commented 4 months ago

Does anyone happen to know why the PS Overlay isn't functioning at the moment? Is it due to Proton bugs not allowing it to function or smth?

Hadrianneue commented 4 months ago

Does anyone happen to know why the PS Overlay isn't functioning at the moment? Is it due to Proton bugs not allowing it to function or smth?

pssdk that comes with the game doesn't install itself, even if you get them files from windows and try starting manually it will just error out, check my last comment above