Launcher problems under Linux

[kevin-ditscheid]

I had a similar report last week, whether here or in a ZenDesk ticket I don't recall. Like you, I don't know how Steam decides what OS you have.

What distro do you use? The previous case was on one I hadn't come across before.

I use Arch Linux as @Aleios10
It is a totally weird behaviour, mine is fixed now and I guess it stemmed from my fiddling around with the compatibility mode, while trying to work around the bug with 3.10.2.
It is all working now, though, so thank you very much for the input

 

[Modin676]

Seeing the last input, I tried using the compatibility mode, with the same result - starting works, but textures are missing. Then deactivatet the compatibility layer, updated to the linux native version (I noticed that a new launcher was added in the respective folder) and then it worked all of a sudden. I will follow up what happend after I restartet the computer and if it then still works.

OpenSuseTumbleweed with updated system by 16.12.2023 here on Ryzen 1600, RX570 and running KDE and Wayland, Steam by Suse repository.

Thanks for the work of keeping bugs out of the way.

 

[Modin676]

So, little update. When starting new - fresh system restart + steam, native linux version will attempt to start, but nothing happens, with steam giving again the option ti hit play. When setting the compatibility to some proton version (latest GE in the last attempt), the game starts with missing textures as described before. After I close the game and deactivate compatibility, I can update 250MB or so, and then native version starts properly.

In addition, the crash report bug seems to be gone. So only the problem with steam not properly launching stellaris after a newstart of steam/the system remains. Please fix, because otherwise, it runs well and I enjoy being on my Suse Tumbleweed.

Thank you very much.

 

[Montesquieu]

This looks like a fun little steam problem? Either that or there's some metadata issue with the launcher and steam ident?

Make sure forced compat tool is off. Remove the wine prefix from compatdata if exists. Close steam. Reopen. Check if it is trying to download the runtime and stellaris again.

If so, it's steam deciding that the game is better run under WINE. Likely getting a communication error because it's just launched inside the wine prefix.

The way I 'fixed' it is to use 'Steam-Play-None' which you can get via proton-up. There's a github repo for it too. It's just a stub that tells steam to bugger off.

I don't know how steam determines all this, but there might be something Paradox can do here?

Just for reference:

Distro: Arch Linux
Kernel: 6.6.4-zen
Paths: ~/.local/share/Paradox Interactive, ~/.paradoxinteractive
Erroneous wine paths: ~/.wine/drive_c/Program Files/Paradox Interactive, ~/.wine/drive_c/users/user/App Data/Paradox Interactive

I also did not enable steam play initially, it simply decided it's a windows game now.

Thank you, thank you, thank you!

This did solve my problems and was exactly what happened!

 

[Hubbabub]

This looks like a fun little steam problem? Either that or there's some metadata issue with the launcher and steam ident?

Make sure forced compat tool is off. Remove the wine prefix from compatdata if exists. Close steam. Reopen. Check if it is trying to download the runtime and stellaris again.

If so, it's steam deciding that the game is better run under WINE. Likely getting a communication error because it's just launched inside the wine prefix.

The way I 'fixed' it is to use 'Steam-Play-None' which you can get via proton-up. There's a github repo for it too. It's just a stub that tells steam to bugger off.

I don't know how steam determines all this, but there might be something Paradox can do here?

Just for reference:

Distro: Arch Linux
Kernel: 6.6.4-zen
Paths: ~/.local/share/Paradox Interactive, ~/.paradoxinteractive
Erroneous wine paths: ~/.wine/drive_c/Program Files/Paradox Interactive, ~/.wine/drive_c/users/user/App Data/Paradox Interactive

I also did not enable steam play initially, it simply decided it's a windows game now.

Thanks a bunch @Aleios10
The Steam-Play-None fix helped me
Thank you!

//Hubbabub
(Hubbabub65)

 

[Modin676]

Thanks a lot for the feedback. I deleted the folder for wine, but that did not work on my end. Though while roaming around in the compatibility setting, I found a native linux launcher v2 at the bottom under the proton versions. That works fine, so different solution with a satisfying end.