Please stabilize multiplay

Please FD stabilize the multiplay.
I have already set several bug reports concerning this game breaking issue but still nothings visible happens to solve these.

"Connections loss", "client crashes" happen to me and to everyone I used to play together constantly.

When are these fixed?
 
Last edited:
Also what location,

I get a disconnect error normally once a day, normally on planets. I'm in the UK, so wondering if location has something to do with it.

Simon
 
What router and ISP are you with?
There's currently a bunch of issues with wings that have nothing to do with your ISP. Station interiors desynching, everyone but the wing leader having their game freeze at the same instant, etc.

Also what location,

I get a disconnect error normally once a day, normally on planets. I'm in the UK, so wondering if location has something to do with it.

Simon
I think there's also an issue where the matchmaking servers are crashing occasionally, which is why you get randomly dropped every so often.
 
Lol - stuck going into SC at Asellus Primus in open.

Gonna be my crash for the day I think. I'll have a quick shifty at the net logs.

Simon
 
Also what location,

I get a disconnect error normally once a day, normally on planets. I'm in the UK, so wondering if location has something to do with it.

Simon

Up until recently I would have asked the same question.
.
However I've been using my second Cmdr on my old PC taking timed screenshots whilst I play with my main Cmdr on my new PC, side by side.
The second Cmdr gets disconnected but my main one does not.
This is making me think there is more to this and it might be local to my old PC.
Once I've finished the current run of timed screenshots I'm going to look through my PC logs at the same time as the disconnections to see if there is anything going on.
.
 
Up until recently I would have asked the same question.
.
However I've been using my second Cmdr on my old PC taking timed screenshots whilst I play with my main Cmdr on my new PC, side by side.
The second Cmdr gets disconnected but my main one does not.
This is making me think there is more to this and it might be local to my old PC.
Once I've finished the current run of timed screenshots I'm going to look through my PC logs at the same time as the disconnections to see if there is anything going on.
.

Well I got into an empty instance in Supercruise - took a few minutes though., and indeed 3 the three or four low/normal res sites I went to (hey its an Eagle!).

Looking at the netlogs, a few things reminded me of Beta:

Forced disconnect on timeout.
Failed responses for trying to find a relay to the session (is this matchmaker dying?).

Loos something like this:
{12:15:02} Trying 17 machines to find a relay to 247309712145080 x 3 [1/2]((Relay))Name Unknown
{12:15:06} ILeftSession(3): 0x000005cc51fe2043: 4229601523789 x 1053 Name Unknown
{12:15:10} Trying 16 machines to find a relay to 170188555762837 x 5 [1/2]((?62.76.12.215:54957))Name Unknown
{12:15:10} AttemptReconnectViaRelay - timeout - from Connected
{12:15:14} Machine 170188555762837 x 4 [1/2]((Relay))Name Unknown disconnected: timeout
{12:15:14} allow machine to time out immediately after forced disconnect (ed-31797)
{12:15:32} FlowControl:26

This is repeated - so the game is trying to connect me to an island but not managing.
The flow control actually drops each attempt - all the way down to 10 when the matchmaker decides I will have my own instance (so tha its 16 attempts in background as I wait).

Finally get into instance with the following:
{12:23:42} FlowControl:10
{12:23:59} LeftSession(3): 0x000005cc53466662: 67018151039577 x 167 [0/2]((?5.71.207.45:57562))Name Unknown
{12:23:59} LeftSession(3): 0x000005cc53466663: 67018151039577 x 206 [0/2]((?5.71.207.45:57562))Name Unknown
{12:23:59} Object CobraMkIII_SuperCruise 0x000005cc4e1b4883 State=AwaitingReadyToGoLive[1 authority clashes] has authority conflict, but not ready to take authority: 0; 0; 0; 23; 0; 2; 16; 0; 0; 0;
{12:23:59} Object Vulture_SuperCruise 0x000005cc5312c163 State=AwaitingReadyToGoLive[1 authority clashes] has authority conflict, but not ready to take authority: 0; 0; 0; 22; 0; 2; 14; 0; 0; 0;
{12:23:59} Object Anaconda_SuperCruise 0x000005cc4c8bc519 State=AwaitingReadyToGoLive[1 authority clashes] has authority conflict, but not ready to take authority: 0; 0; 0; 37; 0; 2; 38; 0; 0; 0;
{12:24:00} NeedToSendAck for 279083588819449 x 216 [0/2]((?84.25.26.185:54846))Name Unknown increased to 2.00, schedvalue=10.50
{12:24:00} LocationObjectCreator::AllLocationObjectsLoaded
{12:24:00} LocationObjectCreator::AllLocationObjectsLoaded
{12:24:01} LocationObjectCreator:RegisterScenarioCreator - 233d
{12:24:01} LocationObjectCreator:RegisterScenarioCreator - 233f
{12:24:01} LocationObjectCreator:RegisterScenarioCreator - 233e
{12:24:02} Commander Put Undocked

So it looks to me like an insland was created but no-one can talk to the island owner, and the "hand over of authority" algorithm has failed to find a better match, or more likely their is a spin lock.
The Cobra and the Vulture I believe were departing Beagle 2 at the same time as me, the Anaconda I did not see.

Timeout in the end put me in my own instance.

I'm guessing someone has a dodgy P2P connection on their router and mucked up the island ownership creation by responding to enough to be eligable but not enough to set up the peer 2 peer. Gonna blame the Anaconda, because , well fish!

Simon

Simon
Simon
 
@smiths121
Hmm, it looks like your issue is different to mine.
I'm just sitting on a planet in solo. It did do it for about 12 straight hours without a problem but then I'll get 2 or 3 disconnections in a night.
.
 
Back
Top Bottom