search

ValveSoftware / Proton

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

STARS WARS Jedi: Survivor (1774580) #6729

Open wwmm opened 1 year ago

wwmm commented 1 year ago

Compatibility Report

System Information

I confirm:

Sometimes when trying to start the game it gets stuck in a black screen with the game music playing in the background. Initially I thought that dxgi.deferSurfaceCreation = True would solve the problem but is still random. Sometimes it starts just fine but sometimes it doesn't. If we keep trying it eventually works.

Other than that the same performance problems reported by Windows users also apply here. But that is the game's fault.

kisak-valve commented 1 year ago

Hello @wwmm, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the black screen stall, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

wwmm commented 1 year ago

Just like it happened with Wild Hearts and probably any other EA game the log is huge and even compressed can not be put here on github. @kisak-valve here is an external link with it https://mega.nz/file/K49VAKYS#n0qZ71MahtG9H3KL3jhIViV6mF5khD1S9MYskFeNAYE.

wwmm commented 1 year ago

I think that what I'm seeing is a problem in the RX 7900 XT driver

[  144.136413] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=647, emitted seq=648
[  144.136591] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process JediSurvivor.ex pid 5658 thread JediSurvivor.ex pid 5917
[  144.136719] amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
[  145.153243] [drm:sdma_v6_0_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out
[  145.153409] amdgpu 0000:03:00.0: amdgpu: IP block:sdma_v6_0 is hung!
[  145.154480] amdgpu 0000:03:00.0: amdgpu: IP block:sdma_v6_0 is hung!
[  145.154480] amdgpu 0000:03:00.0: amdgpu: soft reset failed, will fallback to full reset!
wwmm commented 1 year ago

drm:amdgpu_job_timedout

Or could it be that the game is doing something weird that is taking so long to finish that the driver is restarting the gpu as a last resort?

YamiYukiSenpai commented 1 year ago

I think that what I'm seeing is a problem in the RX 7900 XT driver

[  144.136413] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=647, emitted seq=648
[  144.136591] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process JediSurvivor.ex pid 5658 thread JediSurvivor.ex pid 5917
[  144.136719] amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
[  145.153243] [drm:sdma_v6_0_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out
[  145.153409] amdgpu 0000:03:00.0: amdgpu: IP block:sdma_v6_0 is hung!
[  145.154480] amdgpu 0000:03:00.0: amdgpu: IP block:sdma_v6_0 is hung!
[  145.154480] amdgpu 0000:03:00.0: amdgpu: soft reset failed, will fallback to full reset!

Did your desktop crash and brought you back to login screen?

wwmm commented 1 year ago

Did your desktop crash and brought you back to login screen?

No. As surprising as it may seem the full gpu reset is working flawlessly and I was not forced to logout. The desktop just freezes for a few seconds and after that I can open gnome process manager to kill the game and try again. It usually works in the third try.

kisak-valve commented 1 year ago

Start Wars Jedi Survivor Controller Not Detected by Game.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6745. @sp1ne7 posted on 2023-05-05T23:15:34:

Compatibility Report

System Information

I confirm:

I apologize but I was unable to generate the log file using the PROTON_LOG=1 %command% launch options. It did not go where it was supposed to and I can not find it.

Symptoms

Any one else having this issue? I submitted a ticket to Steam but could not get help unfortunately. Here is the breakdown of what's happening.

Expect that I have tried all these steps I am about to list on both Bluetooth and a wired USB connection.

-I have tried all 3 settings. Disable Steam Input, Enable Steam Input, and Use Default Settings. Did not work. -I have tried doing everything through Big Picture Mode. Did not work. -I have tried it with making sure only Playstation Controller Support is selected. Did not work. -I also tried all these steps with different DS4 controllers. Did not work. -Basically every method you listed just now I have tried already long before I submitted this ticket. Rebooting my computer over and over again. I have been fighting with this issue for like 3 days in a row. -I have tested my controller on other games using Steam Proton and works just fine. Eldin Ring in this example. -I have been browsing the internet looking for solutions as well and every thing suggested failed for me. -Steam has no issues detecting and recognising my controller whatsoever. -Also tried using DS4DRV (Linux version of DS4 Windows)

There is only one online suggestion I have not been able to try because I can't get it to launch because its part of the game installation and that is EA Launcher. I am under the impression that there is controller settings in there, but because I can't get into it I can't check the settings. I tried to get into it to check the settings using the following terminal command.

STEAM_COMPAT_CLIENT_INSTALL_PATH=/usr/games/steam STEAM_COMPAT_DATA_PATH=/mnt/games/SteamLibrary/steamapps/compatdata/1774580 /home/user/.steam/debian-installation/steamapps/common/Proton\ -\ Experimental/proton run /mnt/games/SteamLibrary/steamapps/compatdata/1774580/pfx/drive_c/Program\ Files/Electronic\ Arts/EA\ Desktop/EA\ Desktop\EALauncher.exe

But this did not work to let me launch the EA App that the game is installed in so I could check those settings. So if there is settings messing with the game not detecting the controller in there I can't even check them because I can't get into it.

When the game launches and I get to the main menu the only controls the game can detect is my keyboard and mouse. I can still use the trackpad on my controller as a mouse in game like I can before launching the game but no other buttons work.

Reproduction

See the symptoms sections for how to reproduce the issue.

wwmm commented 1 year ago

Any one else having this issue?

No. I have one of those generic xbox controllers and at least on wire it is working. I did not try its bluetooth connection with this game yet. But it works on others.

I am under the impression that there is controller settings in there, but because I can't get into it I can't check the settings.

I do not remember having seen controller settings there.

@sp1ne7 Looking at your specs I see we have very different kernel versions. Maybe the old kernel is the problem.

Try to take a look at the output of sudo journalctl -b | grep -i steam after starting the game with the controller plugged. Maybe it will show something about it.

sp1ne7 commented 1 year ago

Here you go. How is my kernel version older if my Ubuntu is up to date? I just updated like half hour ago.

outputcontroller.txt

wwmm commented 1 year ago

How is my kernel version older if my Ubuntu is up to date? I just updated like half hour ago.

The current stable kernel version is 6.3.1. As I use Arch Linux I do not know if there is a PPA providing it for a LTS Ubuntu release. In any case the problem may or may not be the kernel version. So at this moment I would not try to take drastic approaches to upgrade the kernel.

Unfortunately I did not see anything in the journaltcl output that could help to fix your problem. But I see that steam used the PROTON_LOG variable you set. Are you sure no proton log file was created in your user home folder?

sp1ne7 commented 1 year ago

It generated one this time. But its like 1.3GB large it won't let me upload it.

sp1ne7 commented 1 year ago

protonlog.txt

sp1ne7 commented 1 year ago

I copied like the first 10000 lines or so of it at least. I scrolled through a huge portion of it and it looks like it just repeats a of the same things after a certain point so maybe this will be okay.

I also still had it on Proton 8 ge from when I was testing. I put it back to experimental

sp1ne7 commented 1 year ago

Hi there. Don't spend too much time troubleshooting this. I may be wrong about my controller being the issue after all. Jedi Survivor was an exclusive for PS5, XBOX and PC only. Therefore my Dualshock 4 PS4 controller may not be natively supported, hence why it may also not be working on Linux.

I'm picking up a DS5 controller today and testing it when I get home, so I'll let you know if it works sometime today and then you can close out this issue.

sp1ne7 commented 1 year ago

Hi there,

I have confirmed that my Dualshock 4 controller was the issue. My Dualshock 5 controller I just purchased is working just fine, but you have to disabled steam input.

Forgive me for not considering that my controller could have been the issue. This is not a compatibility issue with proton, but was an issue between the dualshock 4 controller and this game.

You can close this issue, but please keep it documented so it can help others solve this issue. Thank you.

urbenlegend commented 1 year ago

I can't launch Jedi Survivor today. It was working fine a few days ago. Is EA APP broken again? It doesn't even seem to launch. Here's my Proton log: steam-1774580.log

wwmm commented 1 year ago

I can't launch Jedi Survivor today. It was working fine a few days ago. Is EA APP broken again? It doesn't even seem to launch. Here's my Proton log:

Try to delete the proton prefix folder. I had to do this after the game update that was released this week. Just deleting the shader cache was not enough for it to stop crashing.

urbenlegend commented 1 year ago

Thanks! Yeah I just tried that, it hung at 100% progress completion during the EA app install, but I clicked Close and Cancel Install, and it proceeded through and launched the game! Works every time I launch it now. Weird how the Proton prefix just broke like that though.

wwmm commented 1 year ago

Weird how the Proton prefix just broke like that though.

Considering that many windows users are complaining about crashes caused by the latest game update I think that Proton is not the one to blame. By deleting the prefix we probably removed some kind of game configuration or cache that is not compatible with the latest update.

YamiYukiSenpai commented 1 year ago

Sometimes, it just doesn't launch, though it might be just the EA app itself steam-1774580.log

https://github.com/ValveSoftware/Proton/issues/6396

jalabb commented 1 year ago

@YamiYukiSenpai It wouldn't launch for me after the latest updates (Proton Experimental and SteamOS Beta), I deleted the proton files and that fixed it

Sturmlocke86 commented 1 year ago

I can't launch Jedi Survivor today. It was working fine a few days ago. Is EA APP broken again? It doesn't even seem to launch. Here's my Proton log:

Try to delete the proton prefix folder. I had to do this after the game update that was released this week. Just deleting the shader cache was not enough for it to stop crashing.

This +1

Came across a similar issue: I'm on Proton experimental here, using it for Battlefront 1 + 2 and Battlefield 1 and 5. All games stopped launching a few days ago, silent crash of the EA app it seems. I followed the suggestions here and deleted the prefix folder for each game, and after relaunching each game Steam reinstalled the EA app and now everything works again as intended. All games launch and play fine online now.

Thanks!

ErikReider commented 1 year ago

Proton Experimental bleeding-edge seems to break the game while the regular Proton Experimental works as expected. The game freezes while compiling shaders and sometimes during the intro video (probably compiling during the intro video)

agurenko commented 1 year ago

Yesterday's Patch 6 broke the game again, cannot launch it with any Proton, including the Proton-GE. EA app is not even trying to start, going directly from Starting -> Stopped. Don't see any obvious issue in the console output

ErikReider commented 1 year ago

Yesterday's Patch 6 broke the game again, cannot launch it with any Proton, including the Proton-GE. EA app is not even trying to start, going directly from Starting -> Stopped. Don't see any obvious issue in the console output

Try clearing the proton prefix. Experimental works for me :)

agurenko commented 1 year ago

Yesterday's Patch 6 broke the game again, cannot launch it with any Proton, including the Proton-GE. EA app is not even trying to start, going directly from Starting -> Stopped. Don't see any obvious issue in the console output

Try clearing the proton prefix. Experimental works for me :)

Hm, maybe I've removed the wrong one yesterday? Anyway it helped, thanks, it's the EA app that's acting up again...

agurenko commented 1 year ago

Since, we're talking, people with AMD GPU, do you also experience following issue, like I do: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8934#note_1891809 ? I found a video online with another 7900 XTX which does show same issues and some recordings of nVidia 4090 on linux without said issues. I'm wondering if it's all AMD GPUs or only 7000-series.

ErikReider commented 1 year ago

Since, we're talking, people with AMD GPU, do you also experience following issue, like I do: gitlab.freedesktop.org/mesa/mesa/-/issues/8934#note_1891809 ? I found a video online with another 7900 XTX which does show same issues and some recordings of nVidia 4090 on linux without said issues. I'm wondering if it's all AMD GPUs or only 7000-series.

Looked like that on my 6800XT at launch but running the latest mesa-git seems to fix it for me

agurenko commented 1 year ago

Since, we're talking, people with AMD GPU, do you also experience following issue, like I do: gitlab.freedesktop.org/mesa/mesa/-/issues/8934#note_1891809 ? I found a video online with another 7900 XTX which does show same issues and some recordings of nVidia 4090 on linux without said issues. I'm wondering if it's all AMD GPUs or only 7000-series.

Looked like that on my 6800XT at launch but running the latest mesa-git seems to fix it for me

Yeah, I've just tried latest mesa-git and it seems to be much better at least in a opening scene, will retest tonight, thanks for the input @ErikReider

kmoschcau commented 7 months ago

I just want to leave this here because it might be something proton can do something about, but mainly because it can help others troubleshoot: When I FPS limit the game with mangohud, it significantly increases load times. It takes literal minutes to load a level when capped at 40 FPS. However if I remove the FPS limit on the load screen, it takes only seconds. Hope the word gets around, because I have not found anyone else reporting this so far.

Hellzed commented 7 months ago

The game was running just fine on my RTX 4070 with the "high" graphics preset and DLSS, but I just reached the Forest Array on Koboh, and performance is now under 10fps, making it unplayable. I've tried lowering the details ("medium" then "low"), it barely helps, making me thing something else is at play. I know this game has terrible performance in general, but this seems really bad and running way worse on Proton than on Windows. Is there any known workaround?

kmoschcau commented 7 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/6729#issuecomment-1860022229

I had the same thing and I highly suspect it's those particles flying around there. Their performance seems to be CPU-bound. I went through it by lowering my resolution and turning everything to low settings for that part. Also it seemed like the AMD upscaler did a better job in that part than the NVidia one.

Hellzed commented 7 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/6729#issuecomment-1862563331

I ended up doing just that too, 1080p instead of 1440p, "low" global preset, and I got through the Forest Array with proper performance. A CPU-bound issue would make sense (still, my CPU is an i9 so I would expect it to just "brute force" it, except if it's a threading issue).

Have you tried the following Steam launch command? PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 %command% -USEALLAVAILABLECORES I've seen -USEALLAVAILABLECORES mentioned before on ProtonDB for Unreal Engline 4 games, it might also have helped in my case but I didn't properly compare.

Performance seems indeed better with FSR2 than DLSS, however DLSS looks generally better, with less artifacts around moving objects.

kmoschcau commented 7 months ago

@Hellzed I have not tried USEALLAVAILABLECORES, no. But I can when I'm there next time. However CPU load already seems to be evenly distributed. PROTON_HIDE_NVIDIA_GPU is redundant and PROTON_ENABLE_NVAPI is already in my /etc/environment.

The reason why I suspect it's a CPU issue is that when you look at the patterns of the particles, it seems to use some random number generator for the particle positions that's not well suited for the task. It leads to some artifacts (straight lines of particles along "block borders"), which I've seen mentioned in GDC talks for why you should not use language built-in RNGs for particles like this. Might just be that whatever the game calls as an RNG function maps to something inexpensive on Windows, but some more expensive function on Linux, which was not designed for this task.

juanejot commented 5 months ago

Interesting behavior: Jedi: Survivor won’t finish starting up if Proton 8.0-5 is set as the default version of Proton for all games, but the game will start & run OK if Experimental remains the default (using 8.0-5 for J:S only). The game runs fine under Experimental (the latest build from 1/11/24, I believe). OS: Arch Linux running Gnome 45.3 in Wayland (so Steam games in Xwayland), vanilla kernel 6.7, Mesa 23.3.3, MangoHud 0.7.0, Gamemode 1.7 (NOT latest 1.8.1, which seems to have no effect & tests crash; separate issue). Steam client: system package (not flatpak; none of above packages are), latest updates. Yes, running multilib so I have the necessary 32-bit packages. Hardware: 9700K, RX 6600 XT, 32GB 3600MHz DDR4 RAM running XMP

sdornan commented 5 months ago

Game seems to crash for me after a few minutes with Proton Experimental on my Steam Deck OLED. Happened before the latest Experimental update too, so I don't think it's tied to that. Used to run without crashing, performance issues aside.

lordcirth commented 4 months ago

Just launched for the first time today; I've tried Proton Experimental as well as GE 8-16. Running with -d3d11 because I got a dx12 error the first try.

On start I get this confusing error message: SurvivorError About my AMD driver being wrong even though it's nvidia.

Then the game launches to a black screen (with my desktop cursor), stays there for a while, then crashes with:

LowLevelFatalError [File:Unknown] [Line: 1024] 
Rendering thread exception:
LowLevelFatalError [File:Unknown] [Line: 258] 
Direct3DDevice->CreateShaderResourceView failed 
 at D:/depot/r8branches/r8release/Engine/Source/Runtime/Windows/D3D11RHI/Private/D3D11UAV.cpp:249 
 with error E_INVALIDARG

0x00000001421e78f7 JediSurvivor.exe!UnknownFunction []
0x00000001421d9901 JediSurvivor.exe!UnknownFunction []
0x0000000143845021 JediSurvivor.exe!UnknownFunction []
0x00000001438456be JediSurvivor.exe!UnknownFunction []
0x0000000143843db3 JediSurvivor.exe!UnknownFunction []
0x0000000141c143fd JediSurvivor.exe!UnknownFunction []
0x0000000141c14483 JediSurvivor.exe!UnknownFunction []
0x0000000142dc7f42 JediSurvivor.exe!UnknownFunction []
0x0000000142dc8bd3 JediSurvivor.exe!UnknownFunction []
0x0000000141d65557 JediSurvivor.exe!UnknownFunction []
0x0000000141d605a1 JediSurvivor.exe!UnknownFunction []
0x00006fffffed473d kernel32.dll!UnknownFunction []

NixOS 23.11, updated, RTX3060

nvidia-smi 
Fri Mar 15 18:30:20 2024       
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.29.02              Driver Version: 545.29.02    CUDA Version: 12.3     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce RTX 3060        Off | 00000000:01:00.0  On |                  N/A |
|  0%   44C    P8              19W / 170W |   1924MiB / 12288MiB |     20%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+
lordcirth commented 3 months ago

With these launch options from ProtonDB, it works well enough so far: VKD3D_CONFIG=dxr11 PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 %command% -USEALLAVAILABLECORES

77boaz commented 3 months ago

Has anyone all of a sudden.. maybe in the past couple of weeks run into a problem where the game won't even launch from the EA APP? I get the message about unable to launch from our end. I didn't play the game much just made sure it launched and worked which it did and it ran nicely a couple months back. Now all of a sudden it won't launch from the EA APP.. GRR. I tried removing the pfx as well as the whole game.. Tried multiple proton versions and no dice. Any thoughts/suggestions. I'm on Endeavouros (arch)

Update on this comment. I re-installed and chose the proton version beta 9. I don't know if this was the issue.. part of the issue or what.. or if it was "truly a problem on their end" EA.. SIGH

ammgws commented 2 months ago

@77boaz Does it still work for you? Bought it this week and have had no luck so far with any proton version. Game did open one or two times (via the EA app launched by Steam) but controller was not working so I exited, and haven't been able to get back in since :/

77boaz commented 2 months ago

@ammgws It's actually interesting you ask this because I just fired it up yesterday and now it won't launch! It looks like EA changed their app yet again.. it looks very different from before.. it's super annoying...

ammgws commented 2 months ago

Strangely I tried installing on my Steam Deck and it opened and played first time :/ Nuked the game dir on PC and tried redownloading but still the same launch error message from the EA app

agurenko commented 2 months ago

I've tried yesterday on my freshly re-installed Desktop and it worked out of the box without issues

77boaz commented 2 months ago

So it's interesting.. I have not yet tried again, but I was able to get it to launch back again when it did not launch by blowing everything away, and when I mean everything I mean.. the prefix.. PFX and the common folder(s).. Reinstalling it. I guess I'm wondering at what level we would have to delete the whole thing. Obviously blowing away the prefix (pfx) is not that big of a deal, but it will/would stink if we have to blow away the entire game and then re-download and re-install for it to keep working lol. Especially since it's one of the biggest; if not the biggest game I currently have size wise. :)

agurenko commented 2 months ago

So it's interesting.. I have not yet tried again, but I was able to get it to launch back again when it did not launch by blowing everything away, and when I mean everything I mean.. the prefix.. PFX and the common folder(s).. Reinstalling it. I guess I'm wondering at what level we would have to delete the whole thing. Obviously blowing away the prefix (pfx) is not that big of a deal, but it will/would stink if we have to blow away the entire game and then re-download and re-install for it to keep working lol. Especially since it's one of the biggest; if not the biggest game I currently have size wise. :)

You can always backup game files and restore them, this will "Install game" from local files, not the internet, so you can backup (Game -> Properties -> Local Files -> Backup game files) -> delete -> cleanup pfx -> Restore and that would be a clean install.

77boaz commented 2 months ago

So it's interesting.. I have not yet tried again, but I was able to get it to launch back again when it did not launch by blowing everything away, and when I mean everything I mean.. the prefix.. PFX and the common folder(s).. Reinstalling it. I guess I'm wondering at what level we would have to delete the whole thing. Obviously blowing away the prefix (pfx) is not that big of a deal, but it will/would stink if we have to blow away the entire game and then re-download and re-install for it to keep working lol. Especially since it's one of the biggest; if not the biggest game I currently have size wise. :)

You can always backup game files and restore them, this will "Install game" from local files, not the internet, so you can backup (Game -> Properties -> Local Files -> Backup game files) -> delete -> cleanup pfx -> Restore and that would be a clean install.

Oh sweet DUH.. I have done that in the past but only on Windows.. I guess I wasn't sure how much of an 'actual' complete install it was. I don't know if there are any inner workings online vs. offline which could be any different. I will try that thanks!

urbenlegend commented 2 months ago

Yeah I am getting a failure to launch as of 5/7/2024 as well: image

EDIT: Completely uninstalling and reinstalling did not fix the issue for me.

urbenlegend commented 2 months ago

Okay, seems like no matter what I do with Proton Experimental it will show the "Error on our end" failure. But if I switch to Proton 9.0-1 and clear my prefix, I can get the game to launch once. Subsequent launches just crash and the Steam play button turns green again.

77boaz commented 2 months ago

I tried re-installing and blowing everything away last night and I still get the same error you're getting above.. "Problem on our end" I tried the most recent proton and some older ones.. even the latest Proton GE and no dice. I got this message before.. Maybe it truly is a problem on their end.. Before I remember it just seemed to suddenly one day start working. Fortunately I've shelved the game to play later as this is definitely annoying... :)

ammgws commented 2 months ago

I also get this with Star Wars Battlefront 2. I wonder if it's broken for all EA games...?