Patch Notes Update Server Update Incoming - 19.06.2015

Status
Thread Closed: Not open for further replies.
DEVELOPMENT SUGGESTION for some end-user experience improvement:

It is clear that the authentication system is separate from the instancing, matchmaking, etc servers. When you do an update, you are only bringing down the back end servers. End users are still getting the log in screen, going through authentication, waiting on all the local client files to load...only at the end when the client tries to create a session with the server does it fail.

When you are taking the servers down you need to set a flag on the authentication servers to pop some simple dialog that the servers are down and stop the process there. This makes the process of eager-beaver gamers checking to see if the servers are back up as simple as clicking the login button and getting instant feedback.
 
Thanks for the fix! :)

Just wanted to get in and had unknown server error, then I took a look in here and now I can connect, that's timing :)
 
Ooh, interesting...

Thanks for the update peeps!

I was affected by the server stability issues, so welcome this with open arms! You too, if you fancy a hug. ;)
 
That happened to me yesterday, was kinda weird (high int. RES). Also, when at a different RES ealier, it was all going ok and then all of a sudden over the space of a minute or so, all other ships just vanished except for a couple of miners.

Ian.

It happens to me ALL the time! :p
 
Which system?
What is your commander name?
What time?

Thanks

Michael
It happens now and then. To lots of CMDRs in lots of systems. I suspect that it is to do with server load. The worst example I had was having to scan 7 times before it actually completed the scan. There are also similar issues with blowing your horn. You frequently get an incorrect scan, even with the Advanced scanner. Blowing the horn again usually works, if you leave it long enough. Again, I suspect server load. I sometimes get,say, just a star and two asteroid belts shown in the system scan, with a gap between the belts that obviously has planets in it - very like the view you get with an incomplete scan from just a basic scanner. I also get it where you blow the horn and are told there are lots of objects (say, 54), but the system map only shows a couple of stars, or similar. Blow the horn again, and it reports the 54 again.

Bottom line is that it looks like server load problems, with the client apparently not knowing that it has only received partial information: not only do you need to worry about the server loads, but you should probably put in more robust comms wih the server, so the client knows when it has only got partial information, and asks again.

TL; DR : scans are inconsistent, do not always work, and often report wrong information.
 
Last edited:
Thanks for the update :)
I just hope this server update does not break something that requires a patch come monday and makes game practically unplayable :(
 
I'm feeling like a beta tester.

Can you please do these balancing changes and fixes in the beta stage?
~
Unfortunately, they can't as some bugs and fixes are necessary immediately. This is an on-going and growing game that relies on the input of its players to improve. You can't say that about many games these days, eh.
Just be glad our studious little FrontierDev gnomes are on the job in some teeny industrial park near Cambridge and not sipping liquor store margaritas back at the Motel Six in LA, having spent all their allowance on tacos and gaudy mexican hats at EEE.
 
That happened to me yesterday, was kinda weird (high int. RES). Also, when at a different RES ealier, it was all going ok and then all of a sudden over the space of a minute or so, all other ships just vanished except for a couple of miners.

Ian.

Perhaps they suddenly realised either that there's no point entering combat without shields, or that there's no point trying to rob miners in a depleted rocky field?
 
Sure they could - would you like to wait until the next Beta?
I think he means the majority of issues that are currently in the game were identified during the 1.3 beta and should have been fixed before it was released, this 'test it for a week then sling it out' approach to updates is ridiculous. I would much rather wait for big updates like 1.3 to be tested properly than be left with the largely broken game we've had for the last two weeks.
 
DEVELOPMENT SUGGESTION for some end-user experience improvement:

It is clear that the authentication system is separate from the instancing, matchmaking, etc servers. When you do an update, you are only bringing down the back end servers. End users are still getting the log in screen, going through authentication, waiting on all the local client files to load...only at the end when the client tries to create a session with the server does it fail.

When you are taking the servers down you need to set a flag on the authentication servers to pop some simple dialog that the servers are down and stop the process there. This makes the process of eager-beaver gamers checking to see if the servers are back up as simple as clicking the login button and getting instant feedback.

I agree! It would be most helpful to get the real server status after logging in on the launcher. On a few occasions it would've saved me getting ready, moving seats to my other screen whilst the shaders are being prepared just to have wasted my time lol Though, I check here more often these day's before I'm about to play and again I've saved myself some hassle :cool:

Keep doing what you're doing FD! I have been a fan since Frontier: Elite 2 on the Amiga and am soo looking forward to what else may come in the future from this game! :D
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom