David Braben please open your wallet and set up some proper server

I mean.. isn't it a big shame?

Ok the tadition of not playing on patch day... but this is getting ridiculous now...

FD worked hard for a complete year or more for this incredible patch that everyone has been wating for the last 4 years and now the game is totally unplayable because of a cheap traffic system?

Not even FRONTIER SHOP is working... I wanted to buy a second licence but the LOG-IN and the NEW ACCOUNT pages are totaly facked upp
 
Last edited:

Deleted member 115407

D
Maybe they are getting more traffic than expected, due to the success of the patch?
 
Maybe they are getting more traffic than expected, due to the success of the patch?

With that kind of screw-up, they cull at least some of their customers' desire to continue playing, thus reducing the traffic. A solution. Not an elegant one, but a solution, I'll grant them that . . . ;D

(And, no, I'm not salty. I got to play Total War Rome 2 that way. Otherwise, when ED is working, it keeps sucking up pretty much all my leisure time . . .)
 
Maybe they are getting more traffic than expected, due to the success of the patch?

Oh I do hope this is a joke...

They've hyped the patch for weeks, even before the Beta, offered incentives to old players to come back, and even announced the go-live time and date a week in advance, and yet the number of people trying to play caught them by surprise? Really? They know the size of their player base, and should have been able to anticipate this with reasonable accuracy. Either someone handling the infrastructure was asleep at the meetings or (and I think this is more likely), they've altered something fundamental in the patch that went unnoticed with the lower volume of players in Beta, that has broken the game when a larger player base tries to log in. They should have load tested the Alpha in-house with tens of thousands of dummy logins to protect against this kind of thing.

4 weeks of Beta, most comments ignored (especially around using FSS stationary in supercruise - might as well just beg to be interdicted with no situational awareness). There was some good stuff in there, but they didn't take on board any of the comments from the Beta Testers, or fix half the bugs. They promised the codex would have your historical data in it, then on release day adjusted the patch notes to say "oops, sorry, no it won't. Your codex will start from blank".

Add to that the debacle of more than about 8,000 players trying to log on crashing the servers, and they've hardly covered themselves in glory. If the development team I run had released this software and effectively brought the business down for 2 days, I'd be in front of the board now arguing to try and keep my job.
 
Seems like it's definitely traffic based because I can usually get on once Europe goes to bed. So the obvious solution is for you guys to go drink some Valerian root tea, pop a melatonin tab, and put on some soft music by a warm fireplace. Whatever it takes :D
 
Oh I do hope this is a joke...

They've hyped the patch for weeks, even before the Beta, offered incentives to old players to come back, and even announced the go-live time and date a week in advance, and yet the number of people trying to play caught them by surprise? Really? They know the size of their player base, and should have been able to anticipate this with reasonable accuracy. Either someone handling the infrastructure was asleep at the meetings or (and I think this is more likely), they've altered something fundamental in the patch that went unnoticed with the lower volume of players in Beta, that has broken the game when a larger player base tries to log in. They should have load tested the Alpha in-house with tens of thousands of dummy logins to protect against this kind of thing.

4 weeks of Beta, most comments ignored (especially around using FSS stationary in supercruise - might as well just beg to be interdicted with no situational awareness). There was some good stuff in there, but they didn't take on board any of the comments from the Beta Testers, or fix half the bugs. They promised the codex would have your historical data in it, then on release day adjusted the patch notes to say "oops, sorry, no it won't. Your codex will start from blank".

Add to that the debacle of more than about 8,000 players trying to log on crashing the servers, and they've hardly covered themselves in glory. If the development team I run had released this software and effectively brought the business down for 2 days, I'd be in front of the board now arguing to try and keep my job.

Crikey, well put, much better than my clumsy and troll like comments (repped)
 
The thing that annoys me most is that this isn't a one-off thing. It happens every time. Which, after a few years, should be a reason to look for a solution. And not advertise the patch until you're sure it actually works, because this is doing more harm than good. If I were a codemonkey at FD I'd be unhappy.

Then again, seeing the Angry Nerd Boys rage on all social media (sometimes the same dude on all of them) compensates. ;)
 
Last edited:
Save yer breath lad, there will be people in soon defending FD, they can do no wrong.

They can definitely do wrong .... but I think we're well past the point of threads appearing on the forum, suggesting large scale changes to the way the game is run.
 
perhaps being december was a particularly bad time to rely on amazon for server capacity? what with everyone buy on amazon.com XD

but i cant shake the feeling its more than capacity issues. maybe the GRU got the wrong servers to attack lol
 
It could be anything, not necessarily server bandwidth/connection.

I would also suggest if Frontier were running their own servers that such issues would be worse. AWS have a wide global reach and reliable service generally. The fact this happens on launch day suggests to me bugs in the code not a directly server related issue.
 
I've heard that the RSPCA are asking some very pointed questions about the conditions in which the server hamsters are kept.
 
Back
Top Bottom