ok, in my case this is low-end notebook with intel hd4000 integrated GPU that does not meet minimal requirements for Horizons. it takes ~10-15min to launch the game where most of this time is taken to process planetary compute shaders - this is what "Prepare planet generation system" step you see, which is specific to Horizons (regular non-Horizons ED does not have it and starts just fine).
Until recently the game could start just fine albeit taking very long but now it game client takes more time and also crashes during this step. Perhaps the root cause is increased game start time that exceeds some network timeout (i.e. game is expected to connect to server within specific period of time since start) or perhaps this is due to losing/corrupting some client state due to crash.
The workaround for my case was is to replace default compute shaders (TerrainComputeShaders.csa) with nvidia version which is smaller and seem less compute intensive. It's a sledgehammer approach but for my notebook specs I just want to be able to start/play game regardless of graphics. With this change game reliably starts and could be played however the issue still happens if computer put to sleep for some time(~hour) with game running.
Would really appreciate if we're given the root cause analysis/explanation for this from support just to understand what the issue is.
Thank you very much for this, I think It might be useful for many!
I also have to say that I fixed my issue somehow.
I just tried downloading steam on another pc I got here. So: same wireless connection, same OS (Win10), same platform (Steam).
As I got main manu "social" was grey, but suddenly after few seconds everything connected properly.
I had a look at "connection" ad there were anything different from my "mac-version" setup.
So I thought it worked as some cmdr wrote here, just because this PC is newer with better specs.
However I played my last card: logged out and tried again with my Mac (via bootcamp etc)
and it worked!
Maybe just luck, maybe my session needed a sort or "resurrection process" like it was stuck nowhere... don't know.
My two cents is try with another pc (if you have one).
Hope it might help.
o7