search

ValveSoftware / Proton

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

Returnal (1649240) #6538

Open alosarjos opened 1 year ago

alosarjos commented 1 year ago

Compatibility Report

System Information

I confirm:

steam-1649240.log

Symptoms

Freezes while preloading the shaders at 72% and ends up showing an error (Have retried multiple times)

alosarjos commented 1 year ago

Game is running fine if using mesa-git.

LordDaveTheKind commented 1 year ago

It works perfectly for me when switching Steam offline. I spotted it by noticing that the Epic Online Service executable was crashing, and blocking the game. Here below my running specs: HW: AMD Radeon RX 6900XT Driver: Mesa 22.3.5 Proton version 7.0-6

braiam commented 1 year ago

Changing launch options to "Returnal/Binaries/Win64/Returnal-Win64-Shipping.exe" avoids EOS crash, while also allowing EOS login. Why it crashes when launched by the default launcher but not when inderectly by the game? I have no idea.

alosarjos commented 1 year ago

Hmmm, not crashing for me without doing any of that. Maybe something related to Proton Experimental?

ClearlyClaire commented 1 year ago

I hit the same issue with the game systematically hanging between 50% and 80% of precompiling shaders, no matter how many times I tried and which version of Proton I tried to use (but I didn't try a wide range of them). Eventually, I found this issue and the suggestion of running Steam in offline mode. I did so and I got past the shaders precompilation step. I just retried online and I have not encountered an issue yet.

EDIT: Changed Proton versions to test something, and it caused the shader precompilation step to trigger again. This time, going in offline mode doesn't help (but EOS tries to connect anyway), so I wonder if it was just a coincidence.

Mesa: 22.3.5 GPU: AMD Radeon RX 6900 XT Linux: 6.1.8

zrooda commented 1 year ago

Not working for me in either Steam offline mode or using the launch param as @braiam suggested, game always hangs during shader compilation while EOS tries to connect.

LordDaveTheKind commented 1 year ago

Changing launch options to "Returnal/Binaries/Win64/Returnal-Win64-Shipping.exe" avoids EOS crash, while also allowing EOS login.

Thanks mate. It worked for me too.

Bitwolfies commented 1 year ago

As a counterpoint, EOS posed no issues for me, and the shaders compiled with no issue, on Bleeding edge + gtx3080

iihmsunn commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/6538#issuecomment-1432103585

I have a somewhat similar case of getting past the shader precompilation yesterday without doing anything at all, it just seemed to skip the precompilation on second launch after crashing and i thought it must have finished it before it crashed. This was on proton-ge 48. But then I updated to 49, the cache got invalidated and now I can't get past the precompilation no matter what version of proton i use, deleting compatdata doesn't help, offline mode and launch parameter don't work either

I use flatpak steam on linux 6.1.11. I also tried running with mesa-git from flathub-beta and it doesn't work at all, just shows some error even before the intro movies. Edit: stable mesa on flatpak is 22.3.4 and I'm on Radeon rx6600 Edit: another (irrelevant to me) thing i've noticed is steam offline mode doesn't actually stop EOS from connecting during precompilation. What does is setting "start game in online mode" to off during your first launch of the game. I still have a crash when it's not trying to connect

Hadrianneue commented 1 year ago

game presents shadow cascade issues doesn't matter which graphics preset i'm using, game allows -dx11 and it also happens there.

https://user-images.githubusercontent.com/24306541/219292201-81bab26a-8750-4e63-bff4-d7577cd91b90.mp4

RX 6500 XT / vkd3d 2.8 / dxvk 2.1 / mesa-git

iihmsunn commented 1 year ago

Unless this is an another coincidence, launching the game with -dx11 parameter completely skipped shader precompilation for me and the game is now playable.

@Hadrianneue not sure if this is relevant to shadow problem but I keep using proton-ge 49 (was 48 last time i played successfully) and I didn't have any graphics or performance issues. Playing on high settings, rx6600.

edit: pretty sure -dx11 consistently solves the shader problem. Game seems to look the same

ClearlyClaire commented 1 year ago

I can confirm -dx11 does indeed skip shader precompilation, thanks! It seems to come at the cost of some stuttering though.

I'm still not sure what helped me get the shaders precompilation step to work the first time around. I'll try with mesa-git if I can find the time.

On a side note, DualSense features do not fully work on stock Proton, but I wrote a set of patches a while ago that does work with it (see https://github.com/ValveSoftware/Proton/issues/5900)

EDIT: tried with mesa from git, and starting it without -dx11 crashes right after the playstation logo, but maybe I did something wrong

iihmsunn commented 1 year ago

i only tested for a few minutes but yeah, i think the game was smoother without -dx11 even though it still shows over 60 fps all the time. I hoped the issue may be temporary while dxvk is caching shaders the old way or something like that. Guess i'll see later today, have no time to play atm

DomiStyle commented 1 year ago

I also had issues with the game freezing at 52% shader compilation. I let it sit there for a few more minutes and it launched just fine on the second attempt. Didn't change anything between starts.

Other than the game taking like 30 seconds to launch everything seems good so far.

game presents shadow cascade issues doesn't matter which graphics preset i'm using

Will have to look out for that one today but I didn't see any shadow issues yesterday. Certain god rays look awfully blurry on Ultra though, not sure if that's on the game or on Proton but its pretty much the only negative I have to say about the graphics.

ClearlyClaire commented 1 year ago

Talking with radeon/mesa devs, the game hanging while precompiling shaders is apparently a known issue with RADV and should be fixed in the next mesa releases (22.3.6 and 23.0): https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21231

This is also known to sometimes randomly pass.

kisak-valve commented 1 year ago

Hello @Hadrianneue, 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. Also, 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.)

DomiStyle commented 1 year ago

Played a little bit more and Returnal freezes every time the second boss fight starts so I can't progress any further for now.

Proton log: steam-1649240.zip

System info: https://gist.github.com/DomiStyle/469868200b81dca041f0df02bc247d3b

kisak-valve commented 1 year ago

Hello @DomiStyle, are you able to test with a build of mesa that includes the mesa 21231 merge request mentioned a few comments ago?

DomiStyle commented 1 year ago

are you able to test with a build of mesa that includes the mesa 21231 merge request mentioned a few comments ago?

Yep, tried with mesa-git just now and boss is now toast.

So the next Mesa release is also required to get past the second boss.

ClearlyClaire commented 1 year ago

How does one start a Steam game using a mesa build that is not installed system-wide? It seems that Steam/Proton overrides LD_LIBRARY_PATH even if i set it in the game's launch options

alosarjos commented 1 year ago

@ClearlyClaire Since it's a vulkan layer,

VK_ICD_FILENAMES=$MESA/share/vulkan/icd.d/radeon_icd.x86_64.json

Where $MESA is where your custom mesa is installed

Hadrianneue commented 1 year ago

Hello @Hadrianneue, 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. Also, 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.)

the same also happens on windows... either in dx11 or dx12... so its not a vkd3d/dxvk/proton issue... i`ll attach log and system info anyway.

keep in mind that i own the EGS version launched through steam system info -> https://gist.github.com/Hadrianneue/155d4b156bf044d24fb692c1433b7d6a proton log -> https://gist.github.com/Hadrianneue/93534e3cb742776d411533943bcac2ff

ClearlyClaire commented 1 year ago

VK_ICD_FILENAMES=$MESA/share/vulkan/icd.d/radeon_icd.x86_64.json

Thanks, that does the trick! I can confirm that latest mesa git runs the game fine on my computer, not causing any issue in the shader compilation step.

However, when switching Proton versions, I lost my entire progress. And now I'm noticing it does not upload anything to Steam cloud. Is that something other people are running into as well?

iihmsunn commented 1 year ago

for people running steam in flatpak i've learned that using mesa-git, as in FLATPAK_GL_DRIVERS=mesa-git flatpak run com.valvesoftware.Steam actually only works with proton builds that are installed as literal flatpaks, such as com.valvesoftware.Steam.CompatibilityTool.Proton builds installed via protonup-gui flatpak don't work nor do native steam proton versions like proton-experimental

edit: com.valvesoftware.Steam.CompatibilityTool.Proton-Exp seems to be the best one, stable has some audio issues during the intro and GE goes to black screen after shader compilation, probably outdated

norbertkeri commented 1 year ago

Game seems to work fine for me, apart from 2 things:

Got DLSS working, you have to use proton experimental, and launch with PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command%

RTX 3070, nvidia 525.89, arch linux

salixor commented 1 year ago

Started encountering the same issue described above, where my game will randomly slow to low FPS numbers. Panning the camera around sometimes brings FPS back to normal, but panning back slows the game once again. It stays in this state, with the game coming back to normal for a few seconds here and there.

There are no reproducible scenarios. It just randomly happens, when a fight starts, by simply moving around, ... and makes the game almost unplayable.

Running the benchmark, changing some graphical settings, or simply restarting the game, seem to always solve this issue. But it will randomly come back.

It seems to happen with any Proton version (tried stable, experimental, and GE 7.43). Since disabling Vsync, it looks like this weird issue is no longer occurring. I'll edit if the issue does present itself again.

iihmsunn commented 1 year ago

@salixor i had the same thing, the game runs at 60+ fps, including the entire benchmark, but at random moments during fights when looking at enemies it may start drop to 5-20. I think this never happens when i change graphics preset to medium. I was thinking this can be related to particle effects or something like that but i didn't test any individual settings.

Also i think some of the times i got this was after i disabled vsync so it's probably not that. I've actually seen some people having unstable fps on windows and saying it's "not the best pc port" but i don't know the details yet, i'll try to ask to see if it's similar

update: it did happen with medium settings once

Neyvermore commented 1 year ago

@norbertkeri @salixor @rjawiygvozd and everyone having the gaming slowing down randomly, just found a workaround : whenever it happens, pause the game and go to the tutorials menu. It should reset your performances.

I tried it twice so far, and it worked both times.

Hadrianneue commented 1 year ago

@norbertkeri @salixor @rjawiygvozd and everyone having the gaming slowing down randomly, just found a workaround : whenever it happens, pause the game and go to the tutorials menu. It should reset your performances.

I tried it twice so far, and it worked both times.

question, are you vram limited or close to when that happens? could you check with radeontop when it happens again? (because in-game statistics on the graphics tab is not reliable)

liaralabs commented 1 year ago

I'm unable to get past the EOS Online services issue at all. In order to play the game I have to prevent the installation of the EOS online services by renaming the executable to prevent it from automatically being installed by the launcher on the first run. I'm likely killing the ability to do online play with this hack though

When accounting for the above work around, seems to work well and was able to get DLSS settings enabled with the NVIDIA and NVAPI variables above:

nvidia 3060 Ti AMD 5900x Arch Linux 6.1.12

salixor commented 1 year ago

@norbertkeri @salixor @rjawiygvozd and everyone having the gaming slowing down randomly, just found a workaround : whenever it happens, pause the game and go to the tutorials menu. It should reset your performances. I tried it twice so far, and it worked both times.

question, are you vram limited or close to when that happens? could you check with radeontop when it happens again? (because in-game statistics on the graphics tab is not reliable)

I'm on an Nvidia GPU, using Mangohud indeed reports VRAM as limited. There's a whole 2GB difference between what the game reports and what is actually being used ... Reducing options heavy on VRAM usage seem to prevent the issue.

Weird.

Hadrianneue commented 1 year ago

@salixor @norbertkeri @rjawiygvozd are you guys all using nvdia? is the framerate drop really severe like @rjawiygvozd described (5-20 fps) or just mild?

I'm on an Nvidia GPU, using Mangohud indeed reports VRAM as limited. There's a whole 2GB difference between what the game reports and what is actually being used ... Reducing options heavy on VRAM usage seem to prevent the issue.

Weird.

i could be the drivers... idk much about Nvidia but on AMD, RADV does present these issues where AMDVLK does not when VRAM limited (when AMDVLK works that is).

i wanted to say that its VKD3D to blame but while DXVK and consequently DX11 -> Vulkan seems less VRAM intensive, if i push the graphics settings up i will also experience the same slowdowns... so its something related to Vulkan. especially UE4/5 titles when even changing settings on the fly can causes these issues, and as suggested @Neyvermore, pausing, or in my case changing settings like fullscreen>window mode, can fix these slowdowns.

norbertkeri commented 1 year ago

I'm on nvidia yes (rtx 3070, 525.89.02) and the frame drop is very severe, it makes the game unplayable. The suggested workaround of entering the tutorial menu does not fix it for me, I have to completely exit the game and restart.

I lowered my graphical settings from epic to high, and it seems to have decreased the frequency of how often it happens.

edit:

It's the worst in biome 4 (overgrown ruins) so far, and I'm currently in biome 5. In biome 4 I can't get through it in a single playthrough, I always have to exit and restart at least once. I'll change my settings to medium, and see if that helps.

It is possible to complete the level despite this, you just have to be patient, and exit immediately if it gets bad. The game checkpoints automatically, so even if the option of "suspend and exit" is not available in the menu (like in the middle of fights), you can just kill the application, and you will continue close to where you were.

Hadrianneue commented 1 year ago

Tested recently with (DX11) AMDVLK+mesa-git, and while the overall framerate is lower than RADV, it mitigates the slowdown cause by low vram, not entirely but it takes a lot longer to occur. it stutters more so dxvk-async may be desirable...

iihmsunn commented 1 year ago

the vram issue exists on windows as well or at least the issue described similarly as framerate eventually dropping until you restart the game

OHNONOTAMOTH commented 1 year ago

it doesent work anymore it starts compiling shaders and it gets to like 73% and then freezes and crashes

Hadrianneue commented 1 year ago

game is running better with AMDVLK with dx11 for those limited by VRAM, it stutter a whole lot though (maybe dxvk-async can save it)

OHNONOTAMOTH commented 1 year ago

i installed mesa from git and now iit wont even start

OHNONOTAMOTH commented 1 year ago

i uninstalled mesa git and used -dx11, the program starts but when it tries to load the title screen or The Benchmark then my computer glitches for a couple seconds and then reboots

braiam commented 1 year ago

I'm using mesa 22.3.6 on Debian testing and proton 7.0-6, no crashes.

Blisto91 commented 1 year ago

@OHNONOTAMOTH Post a proton log from a game launch where you have issues. Just standard game so without -dx11

Mershl commented 1 year ago

Returnal has Dualsense (PS5 controller) specific support (like adaptive triggers) on Windows. Did anyone manage to have Returnal via Proton detect a Dualsense controller properly?

ClearlyClaire commented 1 year ago

Returnal has Dualsense (PS5 controller) specific support (like adaptive triggers) on Windows. Did anyone manage to have Returnal via Proton detect a Dualsense controller properly?

Proton needs a few additional patches for the audio-based features (mostly, advanced rumble) to work. See https://github.com/ValveSoftware/Proton/issues/5900 for more information. In addition, Steam Input must be disabled for the game and/or for Playstation controllers, otherwise it takes precedence and the game won't detect the DualSense as such.

kisak-valve commented 11 months ago

Returnal crashes at random times

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7153. @BeauTaapken posted on 2023-10-05T19:56:43:

Game: Returnal (https://store.steampowered.com/app/1649240/Returnal/) Proton: Proton - Experimental (Bleeding Edge) GPU: RTX 4090 Driver: 535.113.01

When i play Returnal, sometimes I can play for multiple hours without having this issue, and other times it crashes the instant the game shows anything 3d, this happens with raytracing on and off steam-1649240.log