Waited for launcher and patch to be done, yay. Patched, logged into a toon, did my fleet management for it, switched to next toon. Same one more time. Onto my third...Lagged out and unable to get into game. Thought you JUST fixed this?
And of course, I am not on my main yet to get the ship yet.
Like pretty much everyone else, I'm getting massive lag. Not sure if this is due to the amount of people who just hopped on, or if the patch broke something. Either way, it's making the game pretty much unplayable.
The forums seem to be getting hit badly too, so it's probably demand. Still, in defence of the game, it's not unplayable. So far movement in sector space has been pretty smooth.
I get the feeling that we are facing a bit of a compounded issue from earlier in the week.
I seem to remember a patch being loaded on sunday or monday, and since the next few days the majority of the game was offline due to the network failure I'd be willing to suspect that we are seeing traffic from both sides of the fence overwhelming the patch server for the 3rd anniversary.
Basically the same here, started the launcher this morning, launcher ran a patch then loaded the starting screen, I select my character then it switches to loading map and that is it, at esactly 40.17 % the loading stops and I get " connection to server lost, going on for an hour. I so hate it when the do patches that screw the game up insted of improving existing bugs. Shame on you!!!
While i see that the servers are 'up' and most if not all the threads pertaining to 'launcher/patching' issue have been closed, I am most defiantly still experiencing the same issue i was before, I can't possibly be alone.
As far as i can tell nothing has changed.
The launcher opens and I login, the 'status' bar says "patching" and if i am willing to give it 4-5 minutes it does eventually load the game and go to the "Cryptic" splash-screen. Eventually this closes and i'm given a message saying, "Fatal Error: Unable to initialize on-demand patching and connect to Patch Server: The connection was idle for too long.
The same error i have received through this entire situation.