Titan is hard because your camera isn't zoomed out, not because of server-side delays

[Allyra]

fwiw talking to a jp friend and I guess they are also getting this issue, and have been complaining about it. So not just an NA/EU thing (which is important to note since there are actual JP data centers).

[ufufu]

Quite frankly I do think a good deal of the issue of dodging Weights in Titan HM is skill. Not saying that there isn't a lag problem – there is – but dodging Weights is entirely possible, even when accounting for the positional delay. Although I still haven't figure out what exactly I should be doing when 8 spawn at once post-heart.

[Sunarie]

fwiw talking to a jp friend and I guess they are also getting this issue, and have been complaining about it. So not just an NA/EU thing (which is important to note since there are actual JP data centers).

Yup! There are reports of threads complaining about the issue in both the Japan and French language sections. So it's definitely not just us

[amnie]

Quite frankly I do think a good deal of the issue of dodging Weights in Titan HM is skill. Not saying that there isn't a lag problem – there is – but dodging Weights is entirely possible, even when accounting for the positional delay. Although I still haven't figure out what exactly I should be doing when 8 spawn at once post-heart.

quite frankly, I don't even KNOW my actual dodging skill because right now I have to find work-arounds for not having my client in-sync with the servers. I don't know why that is the case. I do know though that I'm sick and tired of people telling me I just lack the skill.
and the worst thing? once it's 'fixed' (if that happens) people will expect me to immediately be amazing at dodging, which won't happen.
I'm not dodging currently. I run around praying I won't get hit or use 'work-arounds' (landslide running to titan, remembering patterns and so on)
I WANT to get better at dodging. the game won't even let me practice.

[Ricky]

Quite frankly I do think a good deal of the issue of dodging Weights in Titan HM is skill. Not saying that there isn't a lag problem – there is – but dodging Weights is entirely possible, even when accounting for the positional delay. Although I still haven't figure out what exactly I should be doing when 8 spawn at once post-heart.

skill=memorizing a rotation? Well I suppose memorization is skillful

[ufufu]

quite frankly, I don't even KNOW my actual dodging skill because right now I have to find work-arounds for not having my client in-sync with the servers. I don't know why that is the case. I do know though that I'm sick and tired of people telling me I just lack the skill.
and the worst thing? once it's 'fixed' (if that happens) people will expect me to immediately be amazing at dodging, which won't happen.
I'm not dodging currently. I run around praying I won't get hit or use 'work-arounds' (landslide running to titan, remembering patterns and so on)
I WANT to get better at dodging. the game won't even let me practice.

Sorry, I know that just posting that isn't useful in any way. I have found that while I noticeably experience the server/client location sync issue and have a ping over 100ms – as I'm playing from the NA West coast – I am indeed able to dodge the majority of Titan's attacks, usually even without moving ahead of time. It is very precise and unforgiving, but I am able to do it... most of the time. That's just me though, obviously, and your mileage may vary.

[XainTheGreat]

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Jeff>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=30ms TTL=52
Reply from 184.107.107.176: bytes=32 time=33ms TTL=52
Reply from 184.107.107.176: bytes=32 time=30ms TTL=52
Reply from 184.107.107.176: bytes=32 time=32ms TTL=52

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 33ms, Average = 31ms

C:\Users\Jeff>pathping 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

0 JeffsBeast [192.168.0.3]
1 142.254.152.145
2 gig2-5.lkgnwilkgn.wi.rr.com [24.160.229.158]
3 tge1-7-0-9.milzwift-ccr01.midwest.rr.com [65.29.45.102]
4 ae-6-0.cr0.chi30.tbone.rr.com [66.109.6.206]
5 ae-2-0.a0.buf00.tbone.rr.com [66.109.1.42]
6 if-17-0.tcore1.CT8-Chicago.as6453.net [63.243.129.21]
7 if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
8 if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
9 66.198.96.58
10 te7-4.dr9.mtl.iweb.com [184.107.1.110]
11 72.55.128.44
12 184.107.107.176

Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 JeffsBeast [192.168.0.3]
0/ 100 = 0% |
1 8ms 0/ 100 = 0% 0/ 100 = 0% 142.254.152.145
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% gig2-5.lkgnwilkgn.wi.rr.com [24.16
0.229.158]
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% tge1-7-0-9.milzwift-ccr01.midwest.
rr.com [65.29.45.102]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% ae-6-0.cr0.chi30.tbone.rr.com [66.
109.6.206]
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% ae-2-0.a0.buf00.tbone.rr.com [66.1
09.1.42]
0/ 100 = 0% |
6 15ms 0/ 100 = 0% 0/ 100 = 0% if-17-0.tcore1.CT8-Chicago.as6453.
net [63.243.129.21]
0/ 100 = 0% |
7 14ms 0/ 100 = 0% 0/ 100 = 0% if-22-2.tcore2.CT8-Chicago.as6453.
net [64.86.79.1]
0/ 100 = 0% |
8 32ms 0/ 100 = 0% 0/ 100 = 0% if-3-2.tcore1.W6C-Montreal.as6453.
net [66.198.96.45]
0/ 100 = 0% |
9 33ms 99/ 100 = 99% 99/ 100 = 99% 66.198.96.58
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% te7-4.dr9.mtl.iweb.com [184.107.1.
110]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% 72.55.128.44
0/ 100 = 0% |
12 30ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176

Trace complete.

this right here is proof that it is not SE's fault, and im sick and tired of hearing people complain about the .3 positional update. Its clear that it is directly related to the clients ISP/location where they live. Ive said it a hundred times, i dont have problems dodging anything EVER, and its not SE's fault for any of the problems people claim to be having. It also seems like a lot of the people who claim to have these problems are located in the same states, which again, proves its not SE's fault

[Mishari]

this right here is proof that it is not SE's fault, and im sick and tired of hearing people complain about the .3 positional update. Its clear that it is directly related to the clients ISP/location where they live. Ive said it a hundred times, i dont have problems dodging anything EVER, and its not SE's fault for any of the problems people claim to be having. It also seems like a lot of the people who claim to have these problems are located in the same states, which again, proves its not SE's fault

tHiS! ^ ^ ^

[IvoryFox]

SE Defense squad snip

Hey, champ. Square Enix has accepted this PUD (update delay) as a bug on their end, see here: http://forum.square-enix.com/ffxiv/t...s-everybody%29

You can stick your head in the sand all you want because you don't have a problem, but the problem is fairly well-documented in multiple threads and multiple videos. Guess what? It's happening in Japan too, despite having their own data centers.

[Mishari]

It's a problem. Not the problem.
Mostly ISP's handling FFXIV as P2P client and some might expirience graphic lag.
On top of that there is the positional delay thing. But that is not that big of a deal as some may think.
I myself can dodge stuff easily without a problem. Do i have supernatural reflexes? Hell no, I'm an old man lol.