Can't start the game anymore in linux

[Chalchiutlicue]

Sadly I can't start the game anymore in linux.

I use Arch Linux x64 and the nvidia drivers.
Probably a new system update did this.

Sadly I can't debug this issue, since the terminal only shows

 
$ prime-run ./ParticleFleet.x86_64
Set current directory to /home/user/.local/share/Steam/steamapps/common/Particle Fleet Emergence
Found path: /home/user/.local/share/Steam/steamapps/common/Particle Fleet Emergence/ParticleFleet.x86_64
Mono path[0] = '/home/user/.local/share/Steam/steamapps/common/Particle Fleet Emergence/ParticleFleet_Data/Managed'
Mono path[1] = '/home/user/.local/share/Steam/steamapps/common/Particle Fleet Emergence/ParticleFleet_Data/Mono'
Mono config path = '/home/user/.local/share/Steam/steamapps/common/Particle Fleet Emergence/ParticleFleet_Data/Mono/etc'
displaymanager : xrandr version warning. 1.6
client has 4 screens
displaymanager screen (0)(eDP1): 1600 x 900
displaymanager screen (1)(DP3-1): 1920 x 1080
Using libudev for joystick management


Importing game controller configs

[Chalchiutlicue]

I did go into standby for a few hours and woke up my device.
The game is workin again.
Wtf.

[Chalchiutlicue]

And now it's not working again the next day...

[Chalchiutlicue]

It might be pipewire.
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1258
If the sound is broken, the game might refuse to start.
Probably fixed by

systemctl --user restart pipewire pipewire-media-session.service pipewire-pulse

and restarting steam may fixed it.

[Chalchiutlicue]

And again no start possible.

Sad, that I can't debug the issue in the terminal.

[75Karsten]

as a non-Linux person, what is the reason you "can't debug the issue in the terminal"?

Are there other games that allow you to do this?

[Chalchiutlicue]

Other games allow me to see stacktraces and internal error outputs.

If it's possible, I miss the documentation of the needed parameters.

[75Karsten]

I don't know what Unity provides for, but I guess what you have is what you get. You can try and look in the game's log file:

https://knucklecracker.com/forums/index.php?topic=21330.0

Which I think says it should be here:

~/.config/unity3d/Knuckle Cracker/Particle Fleet/Player.log

[Chalchiutlicue]

Sadly if this bug happens the Player.log doesn't get generated.
All I get is just the log above from starting the game in the terminal.

[piotrj3]

What do you get when you try to run game without prime-run, just nativly?

And does game close itself upon trying to launch it in terminal or still keeps working but without any window?

Did you move recently from X window server to Wayland?

[Chalchiutlicue]

The same problem happens with and without prime-run.

There is no window, just an instant dying process.

And I still use the X Server.

I wonder if it dies because of my multi monitor configuration. (Laptop + external monitor with different resolutions)

[piotrj3]

Hmm... did you test without external monitor?

Anyway, Game is made in Unity engine, and probably same issues that other Unity games have, may apply here.

https://wiki.archlinux.org/title/Steam/Game-specific_troubleshooting#Unity3D

Also I saw somewhere issue and solution was chown -R user:user *path to*/steam-library

[Chalchiutlicue]

I then can't start Creeper World 3 as well, if this problem happens.

Do you know if it is also an Unity game?

PS: I need to wait until this bug happens the next time, then I'll look to force the game starting on my laptop monitor.

[75Karsten]

Creeper World 3, Particle Fleet, and Creeper World 4 are all Unity games. THey are, however, at different levels of the Unity Engine, since each was built at a different time.

[Chalchiutlicue]

Sadly no success with the "UnitySelectMonitor" config. (Btw it was already 0, so I played around with the values)