OTHER THINGS are now breaking!

[Kaedan]

It's not just the instance issues anymore! People are apparently getting stuck after fighting with Susano'o, and there's still crashing and disconnects with people doing other old stuff!

So now the excuse "Go do other things!" isn't flying because people are too worried about what to do now!

Is it time for maintenance NOW!?

You're on Balmung... what do you expect?

Other "standard" servers (as opposed to congested) are doing quite well now.

You can't blame SE for choosing to be on the highest population server. Granted, the server problems are problems, but there's not much they can do about it, just like a stadium or auditorium can't do much when an event is overcrowded.

[Dyvid]

You're on Balmung... what do you expect?

Other "standard" servers (as opposed to congested) are doing quite well now.

You can't blame SE for choosing to be on the highest population server. Granted, the server problems are problems, but there's not much they can do about it, just like a stadium or auditorium can't do much when an event is overcrowded.

Too bad it effects the whole Data Center and not just individual worlds...... It's not a Balmung problem, it's an Aether Data Center problems

[Aerowaffle]

You're on Balmung... what do you expect?

Other "standard" servers (as opposed to congested) are doing quite well now.

You can't blame SE for choosing to be on the highest population server. Granted, the server problems are problems, but there's not much they can do about it, just like a stadium or auditorium can't do much when an event is overcrowded.

I can ask you the same question, what do you expect?

People are not going to just roll over and be content with the game when the game is in an unplayable state. Blaming the player for playing on a high-pop server (or on a datacenter that is shared with a high-pop server) is victim blaming. It's entirely SE's fault that there are problems currently. Just as it would be if a stadium or auditorium didn't account and plan for a large amount of people and started having problems because of it.

[Beckett]

Actually new players are getting stuck at the lvl 15 MSQ because it's instanced based. And also lvl 45 job quest people are stuck. So it's no longer an early access thing

I don't understand why these instances are a problem, yet I was able to do my 63 PLD solo instance without any trouble.

[Dyvid]

I don't understand why these instances are a problem, yet I was able to do my 63 PLD solo instance without any trouble.

You got lucky is all. I was forced D/C when doing the RDM solo instance. Had to wait 30 mins to get back in.

[Kerione]

You got lucky is all. I was forced D/C when doing the RDM solo instance. Had to wait 30 mins to get back in.

omg I would kill for a 30 min log in >.> 1hr+ here. >.> Gotta love Balmung.

[Amulrei]

What annoys me is the situation is getting worse, not better. Disconnects from zoning in to areas are increasing, queue times are getting longer (up to near 4k on Tonberry) and there seems to be no actual plan or response from SE other than apathetic shrugging.

I am just at a loss how utterly unprepared SE were here. The early access launch was entirely for preorders so they had a pretty solid idea how many people were going to be trying to play. To make matters worse, we have the standard launch in a few days which is only going to make the situation even chaotic.

[KisaiTenshi]

That makes ... no sense.. what are you talking about?

If something you've queued for in-game has disconnected you, don't play that queue again for 90 minutes to avoid getting disconnected. On Excalibur at 2-5am when it launched, the duty finder was broken-beyond-broken and anything you queued for either kicked you out after 20 seconds, or you queued for it and got disconnected and if you requeued for login before the instance timed out, you got disconnected immediately. This was also happening to the job quests.

Hence, if you get disconnected, switch to something else in the game otherwise you may just be repeating the disconnect-and-kicked-to-login sequence again.

If you've already been disconnected and the queue isn't 15 minutes long, you're going to just get disconnected immediately.

The Susano thing appears to be an explicit bug and players that have been disconnected by that likely are screwed until a patch comes out.

[SicariusSeven]

What annoys me is the situation is getting worse, not better. Disconnects from zoning in to areas are increasing, queue times are getting longer (up to near 4k on Tonberry) and there seems to be no actual plan or response from SE other than apathetic shrugging.

I am just at a loss how utterly unprepared SE were here. The early access launch was entirely for preorders so they had a pretty solid idea how many people were going to be trying to play. To make matters worse, we have the standard launch in a few days which is only going to make the situation even chaotic.

I really think at this point, they do not care and are just waiting for launch. Apparently the Japanese servers are doing just fine. No problems like what we have. The only answers we keep getting are to try again later or wait. Between everything else, I just seriously doubt anything is going to be fixed by launch.

[otarolgam]

You're on Balmung... what do you expect?

Other "standard" servers (as opposed to congested) are doing quite well now.

You can't blame SE for choosing to be on the highest population server. Granted, the server problems are problems, but there's not much they can do about it, just like a stadium or auditorium can't do much when an event is overcrowded.

I just transferred to Coeurl and it's having the same problem.

As people have said, it's a Data Center issue.