garbage waiting times, you suck Enix

[Amileah]

Traceroute is revealing it is an issue at NTT-GIN dropping packets and causing these 90006 etc. errors that are disconnecting people. Can even cause 2002 error.

SNJSCA04 is dropping packets.

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                           172.16.15.254 -    0 |  504 |  504 |    0 |    0 |   13 |    0 |

|           173-23-224-1.client.mchsi.com -    0 |  504 |  504 |    5 |   15 |   33 |   17 |

|                            172.30.7.177 -    0 |  504 |  504 |    5 |   15 |   32 |   18 |

|                             10.16.72.15 -    0 |  504 |  504 |    8 |   17 |   37 |   13 |

|                              10.16.72.1 -    0 |  504 |  504 |   11 |   22 |   53 |   16 |

|            68-66-73-66.client.mchsi.com -    0 |  504 |  504 |   20 |   30 |   48 |   26 |

|              po10.mplmn001er1.mchsi.com -    0 |  504 |  504 |   17 |   28 |   65 |   23 |

|            mini-b2-link.ip.twelve99.net -    0 |  504 |  504 |   20 |   31 |   69 |   26 |

|            chi-b23-link.ip.twelve99.net -    0 |  504 |  504 |   29 |   38 |   74 |   41 |

|    ae-25.r08.chcgil09.us.bb.gin.ntt.net -    0 |  504 |  504 |   29 |   39 |   51 |   35 |

|     ae-4.r23.chcgil09.us.bb.gin.ntt.net -    0 |  504 |  504 |   23 |   38 |   68 |   31 |

|     ae-1.r24.snjsca04.us.bb.gin.ntt.net -    9 |  383 |  352 |    0 |   96 |  154 |   90 |

|     ae-4.r00.scrmca02.us.bb.gin.ntt.net -   10 |  371 |  337 |   84 |   94 |  148 |   95 |

|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net -    9 |  378 |  346 |    0 |   97 |  164 |   94 |

|                           204.2.229.230 -   35 |  214 |  140 |    0 |   95 |  146 |   95 |

|                            204.2.229.11 -   10 |  371 |  337 |    0 |   95 |  152 |   95 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[Sacrilegion]

Right. We will stop bringing them up when they ACTUALLY fix the problems. This is how stuff gets fixed. Being silent means it is okay for them to be lazy about #1 thing that NEEDS to work. Servers not working = No Final Fantasy 14. Not a single player game people just because you can play it like one (exceptions of course). Free to play MMOs have figured this out, SE has no fucking excuse for servers to be in this state. SE needs to fork over the money for better and/or more servers or they can expect cyberpunk 2077 level lawsuits because there is way too many people who can't use the product (Consumer violations in numerous countries).

[Noxii]

-- As for the audio crackling issue? That's not a FFXIV issue. I have one headset that uses different drivers than my wireless headset. The other headset doesn't crackle at all: But since the last audio driver update, my wireless one crackles in XIV quite frequently.

That's a me issue, not a FFXIV issue. I'll be updating my drivers again today and hoping it fixes it. Either way, my other headset is fine.

Try another headset, or uninstalling your audio driver completely and then downloading the updated driver.

Idk me and my friend have the EXACT same headset and im fine he is having terrible audio stuttering issues tried updating drivers etc

[ParagonKammy]

I hope they fix it soon because now the new expansion has no sense. You have to be so lucky or be 24/7 to play a little now...

[Orriss]

So are those of us with normal working hours just SOL for the moment?

It seems the only way to get in right now on high pop servers is either early morning or late at night. Any other time is a 5k plus queue which always gives error 2002 after an indeterminate amount of time...

[Sacrilegion]

Seriously, they need to stop doing maintenance until they know it will fix the problem. Yoshida, please sit down with your dev team and look through the coding as a team. Plan your move out because doing stuff like this in panic is only going to make it worse. You're better off reverting the patches back to initial.

[imeanlikesrsly]

I am really shocked by the incompetence of the dev team. How on earth it is possible that they cannot fix login errors in almost a week now? Even maintenance that was supposed to finally resolve it was an absolute failure. I am starting to think that they don't really have a clue. Yes waiting 4 hours in queue is annoying but getting kicked due to an error after 3 hours just to wait for another 5 ....that is just unacceptable and lasts way too long now. We clearly bought a dysfunctional product. And 7 days that you can spend in this hell for free as compensation is nicely said - a joke.

[agbear9]

I am really shocked by the incompetence of the dev team. How on earth it is possible that they cannot fix login errors in almost a week now? Even maintenance that was supposed to finally resolve it was an absolute failure. I am starting to think that they don\\'t really have a clue. Yes waiting 4 hours in queue is annoying but getting kicked due to an error after 3 hours just to wait for another 5 ....that is just unacceptable and lasts way too long now. We clearly bought a dysfunctional product. And 7 days that you can spend in this hell for free as compensation is nicely said - a joke.

They are working on it.

[MeldinX2]

I do think the 2002 error has gotten better. It might still happen sometimes but before it happened 2-4 times each que and now it did not happen at all for me. The issue is that now the queue seems to take even longer than before. It moves at a snails pace, and while the 2002 error was annoyng it did help to shave off some unlucky players that were in the queue making it go by faster if you were lucky and quick enough to keep your place in queue. It sucks for people like me that work full time and only have a few hours to game when i get home in the evening. If i have 3-4 hours to play and the queue takes 4-5 hours to complete then that just means that i can't log on. Making it impossible for me to play it at all on the weekdays. And things like this makes it hard to justify paying a monthly sub when the only time i can play is abit on the weekends if i'm lucky.

[Nepthys]

Well yesterday it worked better than after the "maintenance", yesterday at the same hour I was 2700 in queue and had 0 errors of 2002, smooth waiting the line and got access. Today after that maintenance on the same hour I was 3700 and in that time 2x 2002 error, first at 1600ish and next one right after 1st one close 1440...too bad I went to the kichen to pick up my tea, relog pushed me back to 5700 queue line.... the "maintenance" destroyed the yesterdays stability in the queue lines.