NOOOOOO it is not, i waited... nothing.It's probably down to congestion guys, I ran into the error message 8 or 9 times trying to log in just now and then eventually the launcher showed data entry boxes for ID and Password then a minute later the Log In button. You just have to keep restarting your clients and be patient, this shit happens and it's nothing to cry about. Good luck.
restated ps4... nothing.
re-installed game... nothing.
deleted update... BINGO, i'm in =D the problem is the update itself not the game or "congestion"
for me the good old "ipconfig /flushdns" did the trick... maybe it works for you too.
Jokes aside all chances their sysadmins running like crazy right now. If that's not something stupid like a wrong line in some launcher config file pointing to dev or QA servers that cannot handle the load. >.<
And suddenly I'm in. Launcher just loaded as always, with no delays whatsoever.
This is if you assume that SE had the foresight to expect issues with the launcher load-ins and put a time-out counter for everything that downloads from the server in, and we've all experienced how much 'foresight' that SE has had with server load issues. My guess is there isn't a time-out counter for any of it, it requests something from the server, expects that it will arrive in a certain amount of time, doesn't get it but continues to try and go ahead and fails out. Yes, programming for networks 101 there... but we have a proven track-record already, don't we?
The sum of all hunt arguments over early pullers: http://goo.gl/IFT9IE
yeah seriously, I forgave them for the 2.0 launch issues but the fact we still continue to have server issues baffles me, I dont think I've ever seen an MMO with so much downtime before because of maintenance.This is if you assume that SE had the foresight to expect issues with the launcher load-ins and put a time-out counter for everything that downloads from the server in, and we've all experienced how much 'foresight' that SE has had with server load issues. My guess is there isn't a time-out counter for any of it, it requests something from the server, expects that it will arrive in a certain amount of time, doesn't get it but continues to try and go ahead and fails out. Yes, programming for networks 101 there... but we have a proven track-record already, don't we?
So is SE going to do or say anything or are they just going to blame it on "congestion"? Would really like to play a game I pay for or at the very least get a non random BS excuse as to what's happening. Would also be nice to even know what error -2146697205 means
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.