Sins of a Solar Empire: Rebellion (204880)

[cdglitch]

Runs almost perfectly on Arch minus one minor quirk:

• Loss of focus causes the game to hang. Definitely the case during the splash screen. Not tested during gameplay.

Steam sysinfo

[rombert]

Counterpoint - the launcher window does not work for me - it just shows whatever was drawn on the steam window and does not accept input.

Monitor: W541 laptop display ( 15.6 in, 1920x1080 )
Display driver: i915 ( I guess)

Also

$ rpm -q llvm Mesa
llvm-6.0.1-1.1.x86_64
Mesa-18.1.5-204.2.x86_64

[thunder1410]

launcher did work once for me, got into game and started a match.
Now when I start the launcher it just copies the background where it opens.
I can move it around and click on links, but I have a hard time finding the play button.
system information

[MayeulC]

I had an issue with the flatpaked version, but it has since been fixed by the Steam flatpak mainainer.
It turned out to be a game problem, where long paths would prevent the launcher from working correctly. Reported here.

Below is the obsolete original report.

Doesn't work great for me, at least on the only computer I can try for now.

Arch Linux, i5-7440HQ, three monitors (same on one). Mesa 18.1.5 as provided by the flatpak runtime I am running steam from. Kernel 4.18.3.

• When I tried it on Proton launch day, and Sins would crash after clicking "play" on the launcher
• After today's last update, the game instantly starts complaining about not being able to find gamedata.dat, which is there. I even checked the game integrity.

Manually going there and running the proton command (with the right env) doesn't help.
I should note that after the last update, steam actually installed the prerequisites before launching.

Update: It works perfectly if I replace StardockLauncher.exe with Sins of a Solar Empire Rebellion.exe (renaming the latter as the former). Still unsure why the launcher complains about gamedata.dat.
I can also alt-tab out and back in, although I have to wait a few seconds with a black screen before the game appears again.

[rombert]

After the update I get the same experience as @thunder1410 - game seems to work fine, but the launcher screen copies whatever was rendered on the screen. In Gnome, if I press the start key to show all windows, the correct graphics are shown, but as soon as the window gets focus it reverts to the old graphics.

Input is accepted though so I can eventually manage to click on the play button and start the game.

[snarvaezsoft]

It is working on Debian 10
I Use Mate Desktop.

My Specs:
Distro Debian 10
Driver: NVIDIA Corporation GeForce GTX 1070 Ti/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 390.77

Installed everything from Debian repository or default, I have not added any extra config or parameter.

Here is the link to my Steam system info:
https://gist.github.com/snarvaezsoft/dd0a970ce0b9ba8ed19a6c91022d2a50

[NoXPhasma]

The game works out of the box for me, also does the launcher. Performance is similar to Windows and I couldn't see any difference. Online play works as well.

Proton: 3.16-4
Sysinfo: https://gist.github.com/NoXPhasma/9ed85e6b0602b656c812acd013ee121f

So the launcher refuses to appear for me out-of-the-box. It shows correctly in the activity window but clicking on it just produces nothing using game's default Proton and Proton 16.5.

https://gist.github.com/byte1024/e11ee2703ad2bc8037747ff5ccd93408

[kisak-valve]

Hello @byte1024, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

For reference, can bypass the launcher by using launch option
/nolauncher
since it wasn't said here. The game itself starts fine.
.
.

Hello @byte1024, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

Yeah, I was looking into that already lol 👍 (busy with stuff)

steam-204880.log

Noticing some odd things here:

78213.135:0008:002b:warn:module:load_builtin_dll cannot open .so lib for builtin L"Steam2.dll": /home/linux64/.local/share/Steam/steamapps/common/Proton 3.16 Beta/dist/lib/wine/steam2.dll.so: cannot open shared object file: No such file or directory
78213.135:0008:002b:warn:module:load_dll Failed to load module L"Steam2.dll"; status=c0000135

78213.135:0008:002d:warn:debugstr:OutputDebugStringA "Performed current game fixup as unable to find location any other way!"
78213.135:0008:002d:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43c6bd ip=7b43c6bd tid=002d
78213.135:0008:002d:trace:seh:raise_exception  info[0]=00000047
78213.135:0008:002d:trace:seh:raise_exception  info[1]=00441c68
78213.135:0008:002d:trace:seh:raise_exception  eax=7b42952d ebx=7b638ff4 ecx=00000000 edx=01b2eb34 esi=01b2ebd8 edi=01b2eb38
78213.135:0008:002d:trace:seh:raise_exception  ebp=01b2eb88 esp=01b2eb14 cs=31300023 ds=1b3002b es=1b2002b fs=f7c50063 gs=1b3006b flags=00000216

78213.560:0008:003a:warn:debugstr:OutputDebugStringA "Window on screen fully"
78213.560:0008:003a:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b43c6bd ip=7b43c6bd tid=003a
...
blah blah

Did a re-install to make sure nothing happened there. Still no dice.

I see there's more problems listed in the log though some could be of no consequence perhaps.

78213.299:0008:002e:fixme:bcrypt:key_asymmetric_verify GnuTLS does not support algorithm 11 with hash len 48
78213.299:0008:002e:fixme:crypt:CNG_VerifySignature Failed to verify signature: c0000002

78213.144:0008:002e:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.

Fixed/check on Fedora by $ su $ntlm_auth -V and follow install prompts (part of samba-winbind-clients). Possibly of no real consequence.

[MayeulC]

All right, the flatpak issue seems due to the fact that the launcher doesn't support arbitrarily long path names (the limit seems to be ~127 chars): flathub/com.valvesoftware.Steam#253

Now, the launcher has a strange behaviour on KDE plasma/Wayland, which can probably be linked to the invisible launcher issue.
Most issues seems to be from people using Gnome Shell (Gnome 3, I suppose). However, at least one person (@thunder1410) seems to have this issue under X.org as well (Gnome 3 now defaults to Wayland).

When launching under plasma/X.org, I have no issues. However, under Wayland, the window decorations (the blur/shadow that normally appears on the side of the windows) overlays the whole window, and stays above the other windows, stealing clicks.

Screenshots:

• of the "window" below:
  
• of the window and its overlay
  

Note: telling spectacle (the screenshot tool) to only capture the active window produces an image that only contains the blur.