In Regards to Stormblood Launch

[Hayate_Himura]

The recent congestion of the servers with issue to the main story quest "Best Served in Cold Steel" and its inability to be instanced made me consider waiting even though it is a serious issue. I began to enjoy other content of the expansion, limited as it may be, to include the Samurai class. To level I decided to do Palace of the Dead and for awhile it was fine. Recently however many players are getting 90002 and 90006 errors as soon as queuing then being locked out of the game for 30+ minutes at a time.

I realize that the expansion may be more crowded than expected however the sales of the game and the amount of pre-orders given gave the company plenty of time to allocate the resources necessary to conduct a smooth transition into the next expansion of their game considering there was a 5 month period between pre-order availability and launch of said content.

Hopefully the team is working overtime to get this issue fixed considering the only notice given over the last 24 hours is "We are sorry so sorry" then a follow up of "We are sorry so sorry"

[Kumiko_sazuki]

It's especially ridiculous given out POTD group was a FIXED party and still kicked us all out. I understand as well that the game is congested but you shouldn't have much of an excuse since it has been over 24 hours since the release and you're a multi billion dollar company. You have the money and server-power to handle this foreseen situation. Maybe you should have also thought about this congestion when adding an instance MSQ so early on into the game. Shame shame.

[WhiteFalk]

It's especially ridiculous given out POTD group was a FIXED party and still kicked us all out. I understand as well that the game is congested but you shouldn't have much of an excuse since it has been over 24 hours since the release and you're a multi billion dollar company. You have the money and server-power to handle this foreseen situation. Maybe you should have also thought about this congestion when adding an instance MSQ so early on into the game. Shame shame.

That's strange... I went in PotD with a fixed party of 4 members and didn't have a single problem with 90006 or 90002. I get it 50% of the time when I queue in a matched party.

Whatever the case though, it seems that with PotD a fixed party gives you less issues since you immediately book an instance and go in as a party. Matched is where it seems 1 or 2 people from the party sometimes gets locked out. I've had it fairly often where the 4th member DC'd as soon as we get in as a matched party.

[zXr]

That's strange... I went in PotD with a fixed party of 4 members and didn't have a single problem with 90006 or 90002. I get it 50% of the time when I queue in a matched party.

Whatever the case though, it seems that with PotD a fixed party gives you less issues since you immediately book an instance and go in as a party. Matched is where it seems 1 or 2 people from the party sometimes gets locked out. I've had it fairly often where the 4th member DC'd as soon as we get in as a matched party.

Certain methods are working better than others, the matched party relies heavily on the instance server to synch properly with multiple world servers, a fixed party it only needs to synch with a single world server, basically running fixed over matched reduces the number of variables that contribute to failure, lowering the over all chance, but the chance is still there.

If you are a PC windows user and monitor the client latency through resmon.exe, you will see two instances listed, each with their own latency, one represent your connection to the world, the other represents the connection to the data center portion, if you log out and change characters and take notice there will be a third temporary instance with no name label, that's the log-in server. Monitoring these numbers myself the world latency was stable between 90 and 120, the data center one was NOT stable, with fluctuations between 120 and 400. Once the data= center connection got over 200, I noticed players 'teleporting' after 300 there was risk to myself for a DC if I did not stop all action, movement, attacks, chat, EVERYTHING, Once it broke 400 it was a guaranteed DC.

This realization based off the information I collected supports my desynch theory. On top of that, since the NADC upgrade, I have noticed increased desynch when trying to heal tanks in dungeons and raids not on my world server (I would have them selected cast a heal and it would cast on myself instead and then have to try and quickly toss out an additional heal -- even tried disabling auto self-cast, then the heal would go off, mana spent, but nobody would receive the heal) I tried bring this to SqEx's attention but never got a response from them and just had troll responses when using the forums. Current situations that be begin to explain why after the NADC upgrade these things occured...I though perhaps it was underlying goundwork for cross-world friends list acting up, but It may jus be faulty DC hardware or software.