FOR THE LOVE OF GOD PLEASE FIX THIS MASSIVE LAG PROBLEM!

[EternityFate]

I Never had so many problems in a MMO as FFRR in my life.
First .... the BETA was a total failure .....( i not even played -.-) they offered all players 7 days free and I really appreciate it.After the game release i got(and others players) countless problems of latency, full world (after day I finally got to go) error 90k, authentication error, server crash, disconect in middle of AK (I can prove it was not my internet because I was playing atlantica online at the same time and the servers did not fall) ... I'm paying for something I can not really enjoy because of bad experience with the FFRR.I love FFRR but for who is working and studying all day and when he wants to get home and play at least 1 hour is impossible...this is really ANNOYING.Let's see if they will solve it or if their will continue ignore the fans.

[Ewgraf]

If the support team responds to or requests extra information for a reported issue, it will be moved to Being Addressed/Currently Reviewing. The report will be moved to Resolved Issues if it is not replied to over an extended period.

I seem to recall the giant 140 page thread requesting information. There's been plenty of replies, so it can't be moved to the resolved issues for lack of information. But they won't move it into the currently reviewing forums, because they can't acknowledge it.

It's rough for them. This is already their second try, there is no choice but to commit seppuku if they admit more mistakes. Fixing it most likely will increase the already way over budget cost even further. Since the customers with issues already paid, losing them is acceptable. Markets outside Japan isn't that important anyway. Maybe Phil Fish and Keiji Inafune is right.

[EternityFate]

I seem to recall the giant 140 page thread requesting information. There's been plenty of replies, so it can't be moved to the resolved issues for lack of information. But they won't move it into the currently reviewing forums, because they can't acknowledge it.

It's rough for them. This is already their second try, there is no choice but to commit seppuku if they admit more mistakes. Fixing it most likely will increase the already way over budget cost even further. Since the customers with issues already paid, losing them is acceptable. Markets outside Japan isn't that important anyway. Maybe Phil Fish and Keiji Inafune is right.

totaly agree

[Vagdal]

I find it totally amusing how some people try to defend SE no matter what. In case you didnt notice i suggest going to main page and checking out the news section.
Recovery from this recovery from that/emergency maintenance each 2 days but everything is fine no problems whatsover.
I got 120 ms on servers with clear route with barely any packetloss or ping spikes and yet im having delay. I wonder what sort of magic is at works here...

[Spencer]

The same thing happen to most of my friends and me. I have 69 ms ping to server without ping spikes, while I am constantly lagging 2 to 10 sec at times.

64 bytes from 124.150.157.35: icmp_seq=16061 ttl=241 time=69.586 ms
64 bytes from 124.150.157.35: icmp_seq=16062 ttl=241 time=69.567 ms
64 bytes from 124.150.157.35: icmp_seq=16063 ttl=241 time=69.333 ms
64 bytes from 124.150.157.35: icmp_seq=16064 ttl=241 time=69.515 ms
64 bytes from 124.150.157.35: icmp_seq=16065 ttl=241 time=69.270 ms
64 bytes from 124.150.157.35: icmp_seq=16066 ttl=241 time=69.213 ms
64 bytes from 124.150.157.35: icmp_seq=16067 ttl=241 time=69.316 ms
64 bytes from 124.150.157.35: icmp_seq=16068 ttl=241 time=68.923 ms
64 bytes from 124.150.157.35: icmp_seq=16069 ttl=241 time=69.050 ms
64 bytes from 124.150.157.35: icmp_seq=16070 ttl=241 time=69.900 ms
64 bytes from 124.150.157.35: icmp_seq=16071 ttl=241 time=69.694 ms
64 bytes from 124.150.157.35: icmp_seq=16072 ttl=241 time=69.498 ms
64 bytes from 124.150.157.35: icmp_seq=16073 ttl=241 time=68.723 ms
^C
--- 124.150.157.35 ping statistics ---
16074 packets transmitted, 16074 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 68.250/69.255/93.282/0.759 ms

[Raist]

The same thing happen to most of my friends and me. I have 69 ms ping to server without ping spikes, while I am constantly lagging 2 to 10 sec at times.

64 bytes from 124.150.157.35: icmp_seq=16061 ttl=241 time=69.586 ms
64 bytes from 124.150.157.35: icmp_seq=16062 ttl=241 time=69.567 ms
64 bytes from 124.150.157.35: icmp_seq=16063 ttl=241 time=69.333 ms
64 bytes from 124.150.157.35: icmp_seq=16064 ttl=241 time=69.515 ms
64 bytes from 124.150.157.35: icmp_seq=16065 ttl=241 time=69.270 ms
64 bytes from 124.150.157.35: icmp_seq=16066 ttl=241 time=69.213 ms
64 bytes from 124.150.157.35: icmp_seq=16067 ttl=241 time=69.316 ms
64 bytes from 124.150.157.35: icmp_seq=16068 ttl=241 time=68.923 ms
64 bytes from 124.150.157.35: icmp_seq=16069 ttl=241 time=69.050 ms
64 bytes from 124.150.157.35: icmp_seq=16070 ttl=241 time=69.900 ms
64 bytes from 124.150.157.35: icmp_seq=16071 ttl=241 time=69.694 ms
64 bytes from 124.150.157.35: icmp_seq=16072 ttl=241 time=69.498 ms
64 bytes from 124.150.157.35: icmp_seq=16073 ttl=241 time=68.723 ms
^C
--- 124.150.157.35 ping statistics ---
16074 packets transmitted, 16074 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 68.250/69.255/93.282/0.759 ms

Are you on Japan or NA/EU server? If it's NA/EU--wrong IP. That is a JP server. The ones in Canada start with 199.

[Spencer]

I am on Aegis JP server.

[Yoggi]

The network setup of FFXIV is a joke and the lack of feedback from SE regarding this issue is insulting to their paying customers.

[kelsethel]

don't you guys get it without the lag this game would be too easy the lag is there death mechanic for all instances HAHAHA.

last month i'am paying for this game they are so far away from a polished game

people who are saying wait I ask "how long" and from what im reading in some of the posts it almost sounds like the lag might be a coding issue if that's the case you guys are gonna be waiting a really long time for a lag fix.

[Wolfgoddesscheza]

If they wanna make this game great hire back the old team who did ffxi