Jedi Survivor refusing to start

Help
1

Hi all I’m pretty new to NixOS although so far I love it, when trying to launch Jedi Survivor through Steam, the game looks to be running but never actually starts. I’ve tried changing the proton version but the same thing happens.

These are the only messages that appear if I run from CLI -

fsync: up and running.
Setting breakpad minidump AppID = 1774580
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561197990283238 [API loaded no]
Game Recording - would start recording game 1182480, but recording for this game is disabled
Adding process 69290 for gameID 1182480
Fossilize INFO: Overriding serialization path: "/STEAM/SteamLibrary/steamapps/shadercache/1774580/fozpipelinesv6/steamapprun_pipeline_cache".
info:  Game: EABackgroundService.exe
info:  DXVK: v2.6-68-g2e20d7302682ea6
info:  Build: x86_64 gcc 10.3.0
info:  Vulkan: Found vkGetInstanceProcAddr in winevulkan.dll @ 0x6fffebcbdd90
info:  Built-in extension providers:
info:    Platform WSI
info:    OpenVR
info:    OpenXR
warn:  OpenXR: Unable to get required Vulkan instance extensions size
info:  Enabled instance extensions:
info:    VK_EXT_surface_maintenance1
info:    VK_KHR_get_surface_capabilities2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
warn:  Skipping CPU adapter: llvmpipe (LLVM 18.1.8, 256 bits)
warn:  OpenXR: Unable to get required Vulkan Device extensions size
info:  AMD Radeon RX 6650 XT (RADV NAVI23):
info:    Driver : radv 24.2.8
info:    Memory Heap[0]: 
info:      Size: 7936 MiB
info:      Flags: 0x1
info:      Memory Type[0]: Property Flags = 0x1
info:      Memory Type[1]: Property Flags = 0x1
info:      Memory Type[7]: Property Flags = 0xc1
info:    Memory Heap[1]: 
info:      Size: 32104 MiB
info:      Flags: 0x0
info:      Memory Type[2]: Property Flags = 0x6
info:      Memory Type[5]: Property Flags = 0xe
info:      Memory Type[6]: Property Flags = 0xe
info:      Memory Type[8]: Property Flags = 0xc6
info:      Memory Type[10]: Property Flags = 0xce
info:    Memory Heap[2]: 
info:      Size: 256 MiB
info:      Flags: 0x1
info:      Memory Type[3]: Property Flags = 0x7
info:      Memory Type[4]: Property Flags = 0x7
info:      Memory Type[9]: Property Flags = 0xc7
Fossilize INFO: Overriding serialization path: "/STEAM/SteamLibrary/steamapps/shadercache/1774580/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: Overriding serialization path: "/STEAM/SteamLibrary/steamapps/shadercache/1774580/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: Overriding serialization path: "/STEAM/SteamLibrary/steamapps/shadercache/1774580/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: Overriding serialization path: "/STEAM/SteamLibrary/steamapps/shadercache/1774580/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: Overriding serialization path: "/STEAM/SteamLibrary/steamapps/shadercache/1774580/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: Overriding serialization path: "/STEAM/SteamLibrary/steamapps/shadercache/1774580/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: Overriding serialization path: "/STEAM/SteamLibrary/steamapps/shadercache/1774580/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: Overriding serialization path: "/STEAM/SteamLibrary/steamapps/shadercache/1774580/fozpipelinesv6/steamapprun_pipeline_cache".
Game Recording - game stopped [gameid=1182480]
Removing process 69290 for gameID 1182480

Does anyone know what is causing this?

2

I’ve worked out it’s something to so with the EA ‘launcher’, by changing the Proton version, I eventually had the EA screen come up, when I clicked on Jedi Survivor, it said ‘app broken’ or something similar. I’ve tried the exact same thing on OpenSUSE Tumbleweed (same drive, partition, etc but replacing / and /home) and it launched with no problems at all.

3

Hi i found a fix!

I set launch options to

for var in $(printenv | cut -d= -f1); do export $var=$(echo ${!var} | rev | cut -c1-1000 | rev); done ; %command%

and used GE-Proton9-27.

I found this here:
https://discourse.nixos.org/t/failing-to-launch-ea-games-on-nixos/61944

which references to here:
https://www.protondb.com/app/1237970#R7KoHBKZsf

Apparently this has something to do with EA not liking long Env Variables and this command cuts the variables to a maximum of a thousand chars.

I also ran protontricks but that didn’t do anything i think.