It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
After upgrading to version 1.1h2, I get black screen after loading the save or just starting a new game. Tried to run in the window, use steam runtime, but nothing helps. Rollback to the previous (1.0.3.3) version, and it works fine.
Any solutions?
64-bit Linux, NVidia GTX 650 with proprietary driver 390.48.
Post edited June 22, 2018 by EugVVl
No posts in this topic were marked as the solution yet. If you can help, add your reply
Same here, black screen of emptiness. https://pastebin.com/eARpk5uV

// Also with GTX650 and 64-bit Debian 9. Those upgrade plans never made it…
I thought I had the same problem, but it seems to have gone away. I suspect it just takes very, very long to read its startup data from disk now, and now that it's loaded/cached in memory, the game appears to start in a reasonable time. Either that or it's some intermittent error.
avatar
EugVVl: After upgrading to version 1.1h2, I get black screen after loading the save or just starting a new game. Tried to run in the window, use steam runtime, but nothing helps. Rollback to the previous (1.0.3.3) version, and it works fine.
Any solutions?
64-bit Linux, NVidia GTX 650 with proprietary driver 390.48.
Can I ask which distro you are using and does the music play during the black screen of doom? If so, it may be loading extremely slowly. Officially, Unity (the game engine) requires the following :

Distribution: Ubuntu 12.04+ or current SteamOS
GPU/driver: OpenGL 3.2 core profile or later (opengl)
libvulkan 0.21 or later, with correspondingly supported gpu/drvier (vulkan)

But that said it * should * work on other distros without issue.
avatar
JuggernautGames: Can I ask which distro you are using and does the music play during the black screen of doom? If so, it may be loading extremely slowly.
I don't hear music at all, even in the main menu. And I don't see loading screen, it only flicker for a moment, and everything goes to darkness except the mouse cursor. I waited more than half an hour and nothing (the game constantly consumed about 100% of processor all this time).
In 1.0.3.3 the music plays normally and loading is almost instant.
avatar
JuggernautGames: But that said it * should * work on other distros without issue.
My distro is unsupported indeed. It was Alt Linux even without a number (or I forgot one). It was installed more than 10 years ago and slowly updated with unstable branch. But I had no problems with any of the games on my list (250+ Linux games) before, neither with Unity nor with others. Only rare and solvable problems with libraries and problems with full screen on a couple of Unity games. And StarCrawlers worked without issues before this version.
avatar
JuggernautGames:
Also on new version I don't see startup screen with developer name before the main menu.
Same problem here, Ubuntu 18.04, StarCrawlers 1.1 (installation file is "starcrawlers_en_1_1h2_21682.sh").

Original error:

Unable to preload the following plugins:
ScreenSelector.so
libCSteamworks.so
libfmod.so
libfmodstudio.so
libsteam_api.so
Logging to /home/xxx/.config/unity3d/Juggernaut Games/StarCrawlers/Player.log
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
[S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so.
I then start Steam and last line or error changes to:

[S_API FAIL] SteamAPI_Init() failed; no appID found.
Either launch the game from Steam, or put the file steam_appid.txt containing the correct appID in your game folder.
I then create the mentioned file (steam app id = 318970) but that doesn't help either.

Isnt is a bit strange that a game received on gog.com requires the Steam runtime? I may be wrong, but it looks to me that someone released the steam version of the game on gog.com
Post edited July 01, 2018 by jm4n
Still the same problem on 1.1.1.
Here's an update.

The problem (at least in my case) was the excessively slow shader compiling:

Shader warmup: 126 shaders 2841 combinations 263.923s <--- !!
This excessively long startup time (as already reported in this thread) made me think the application was stuck (running on a laptop with I7 3,4ghz, 32gb RAM and 940MX).

The Steam client errors are completely irrelevant.

By the way, I just noticed that a new build has been uploaded ("starcrawlers_en_1_1_1_21922.sh" , version StarCrawlers v1.1.1 - Unity 2017.3.0f3 : 23:14 06 July, 2018).

Now that I can play, I hope I won't experience all the crashes reported in this forum too ...
Post edited July 07, 2018 by jm4n
avatar
jm4n: This excessively long startup time (as already reported in this thread) made me think the application was stuck (running on a laptop with I7 3,4ghz, 32gb RAM and 940MX).
Ah, yes, I should've realized that. I'm still used to the bad old days, where shader compile times occurred on every load. I forgot that mesa now caches compile results, so I guess that's why the game now starts in a reasonable time for me. Sure enough, moving ~/.cache/mesa_shaders_cache to the side makes it take way too long to start up again, at least the first time.

edit:
avatar
jm4n: Now that I can play, I hope I won't experience all the crashes reported in this forum too ...
I still experience this issue, for which the workaround only barely works.
Post edited July 07, 2018 by darktjm
I found a solution! The game just did not work in my Russian locale. After I added to the start.sh line
export LANG=C
after run_game () {, the game works fine (there is music in menu, developer logo, loading screens and everything else). The first launch took some time, but now it is almost instant.
avatar
EugVVl: I found a solution! The game just did not work in my Russian locale. After I added to the start.sh line
export LANG=C
after run_game () {, the game works fine (there is music in menu, developer logo, loading screens and everything else). The first launch took some time, but now it is almost instant.
I tried that too and my shading compiling time has decreased from 262s to 172s and finally 7s only!

Not sure which "combination" of actions was effectively the solution: I've deleted che "~/.cache/mesa_shader_cache/" folder, exported LANG=C and installed the latest Starcrawler version.

Thanks for the suggestions!