STARS WARS Jedi: Survivor (1774580)

[wwmm]

Compatibility Report

• Name of the game with compatibility issues: STARS WARS Jedi: Survivor
• Steam AppID of the game: 1774580

System Information

• GPU:
• Driver/LLVM version:
• Kernel version:
• Link to full system information report: https://gist.github.com/wwmm/554c17ef4bc38a8ebb9d52068968d9d9#file-pc_system_info-txt
• Proton version: Proton Experimental based on Proton 8 and available on 29/04/2023

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

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]

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]

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]

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]

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]

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]

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]

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

• Name of the game with compatibility issues: Star Wars Jedi Survivor
• Steam AppID of the game: 1774580

System Information

• OS: Linux Ubuntu 22.04.2 LTS (Latest Version as of this Post)
• GPU: Nvidia GeForce 1660 Super
• Driver/LLVM version: Nividia-driver-525 (Proprietary)
• Kernel version: 5.19.0-41-generic
• Link to full system information report as Gist:
• Proton version: Proton Experimental

I confirm:

• [ x] that I haven't found an existing compatibility report for this game.
• [ x] that I have checked whether there are updates for my system available.

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]

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]

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]

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]

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

[sp1ne7]

protonlog.txt

[sp1ne7]

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]

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]

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]

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]

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]

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]

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]

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]

@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]

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]

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]

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]

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]

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]

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]

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]

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]

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.