Patch Notes Update Gamma update 2.05 incoming

[DaveeBoy]

upgraded to 54009 and now my game is fixed

 

[Hexcaliber]

Do they normally respond to pings? They may have just turned that off to prevent DDOS...

I tried a tracert and the requests are stopping before they get to the game server, but still part of the Amazon web services network. I have pinged the servers in the past without issue.

 

[xxluda]

After last update I was not able to connect to game ( Gamma 2.0.5.r54009/r0 unconnected).

After modifying upnpenabled to upnpenabled="0" and VerboseLogging="1", game is online again.

 

[Apec Valorian]

Scum gathering at Lugh?

Sorry, wrong thread.

 

[Carrumba]

Now in on private group... will see if matchmaker error occurs

 

[Toumal]

I tried a tracert and the requests are stopping before they get to the game server, but still part of the Amazon web services network. I have pinged the servers in the past without issue.

That's not saying much. You can disable ICMP on their servers as part of the config.


BTW I'm also just getting the "no adjucation server" error.

Adjucation... heh... rarely heard that used in connection with networking...

 

[Nazutin]

after upgrading 54009 ... can't connect anymore
before that everything was fine and working.

 

[Coyote]

I'm in now.

 

[vjek]

Best Change Ever!

We're not - that was the bug that was fixed. I've corrected the change log.

Michael

BEST.
CHANGE.
EVER!

Thank you for fixing the galaxy map filters resetting!

 

[Hexcaliber]

Game eventually connected about the same time a successive ping received a response, it may simply be a case of too much traffic.

 

[Erik Marcaigh]

I'm playing Open Play. My rep is the same. I'm taking and completing missions. Trading.
Things are fine for me.

G2.05, the Second Iteration

 

[Shane Gleeson]

Can only connect 1 in maybe 10 attempts. Not going to risk my current status in game until this is sorted. A shame because I was about to go on a massive journey to reach the station I named.

Unfortunately I can imagine this is small fry compared to what will happen at launch but that's the price to pay for always online.

 

[Carrumba]

Now in on private group... will see if matchmaker error occurs

Managed to frop into an USS with no matchmaker crash...private group

 

[veilchen2k]

Spinning ship for a minute or so and then got 'could not connect to the adjudication server'. Retrying...

Edit: Second attempt at joining Open Play got me the same result, but I went straight into Solo

Also here. Retrying ...

I am in now.

I could successfully start the game 5 times.

 

[3LDRITCH]

just got the matchmaking error boot while in solo play. worked fine for about 10 minutes tho

 

[thebullfrog]

The original 2.05 update I could play for a while before getting dumped by the "failed to connect to matchmaking server" error, and got the spinny ship of death once.. I tried that .EXE that Colin put up, and was able to play perfectly fine for a while. I left and came back to the 54009 update and now I can't stay connected for more than about 1-2 minutes. Someone still missed a ';' somewhere.

 

[CMDR Moortz]

In, got into combat with an NPC cobra, and dropped matchmaking server.

Got back in and spinning OSOD

 

[TuesdayFrog]

Still having to discon issues. Got in and launched only to stop at 00:00 on hyper space. Had to quit out to desktop.

 

[Colin Davis]

Hi all,

We are aware of the server issues being experienced right now. Hopefully they will settle down soon.

Thank you to those who helped narrow down and test out the earlier game load issues.

Thanks,
Col

 

[trekman]

Hi all,

We have a potential fix for this "spinning sidewinder" issue.
If you could confirm for me that this new executable fixes the problem for you that would be great!

Download from;

http://hosting.zaonce.net/elite/gamma205/EliteDangerous32.exe

and replace your EliteDangerous32.exe wherever the game is installed for you and try again.

Thanks,
Col

Everything is fine. Back in now. Thank you.