Sorry SE, but endgame won't work if you don't fix something.

My two gil.

I've thus far done one run of HM Titan with some FCmates, so I wanna preface this message with that. That said, that first run had five seperate attempts.

One of my FC has utterly given up on the Titan step of the Relic as a result of not only being utterly clear of Weight, but for the reaction of other players in the group blaming him for being unattentive. Having been blasted off the side by Landslide while well clear, I know for a fact we were experiencing latency.

It would appear, until there is actual verbal agreement from this dev team to the contrary, that you, the devs of this game, are willing to let the community eat itself alive between those who have experienced and have video proof of latency and those who are willing to shrug it off as "bad players are bad" while not doing a thing to attempt to fix or even acknowledge the issue.

Prove us wrong. Or we will walk.

Fix it SE!

What do we want?

NON CANADIAN BASED EUROPE SERVERS!

When do we want it?

Sometime in the near future would be acceptable!

Seriously though Canada is a part of North America, come on SE.

Here's a new contribution to this topic: Not only do we discuss lag and how you get hit by mechanics that you clearly dodged... But we discuss the fact that once you dodge the "indicator" you can run through the mechanic itself and take no damage/effects.

The feel this gives off is that we are dodging red circles and cones, there's no need to dodge the actual explosions and lazers, they are harmless!

http://forum.square-enix.com/ffxiv/t...net-code/page1

Signed, liked, fix it SE.

Bump.

SE I'm not allowed to dodge Titans plumes so why should you be allowed to dodge the question?

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

The problem actually consists of 2 major parts.

First part is really connectivity. EU servers based in Canada are making EU players suffer from high network latency which can't be fixed by any means besides creating a dedicated EU datacenter. This is really expensive and requires both new hardware AND new office with new people. Would be a hard decision but I would go for it as SE cause because of it they are effectively losing EU subscribers.

The second and not the least part is the game design. The thing that really cosfuses people is the "animation lag", which is not the lag but a designed delay. I'll explain.

The boss has a cast (with a castbar) which is marked on the ground with a red area. At the end of the cast the attack should happen. What we are seeing is the red zone disappears and the boss actually starts his attack animation (which can be as long as 1.5 secs) and in the end of animation the attack happens dealing damage anf other bads like pushback in Titan's case. The thing is that the list of people effected by the attack is calculated right in the end of cast so people really have the animation delay to roam freely and get the attack when they are pretty far from the red zone.

The later should be definitely fixed by making the animation sync with cast bar and the effect be applied right when it should. So many skills are really effected by this "feature" that I can't even imagine PvP.

One more feature of FFXIV servers is that they do not really process data in a real time. They are doing internal cycles that process data which causes many consequences like ability delays and unpredictable DoT damage which do not tick fixed amount of times but do tick based on how many server cycles to actually fit in DoT's duration and it really differs from time to time.

While I like the FFXIV game very much I must admit that technically it is a disaster. I am patiently waiting for SE to even mention fixes for these misdesigns but do not currently see any. Probably I should get back to RIFT raiding and stop any efforts here.

Quote:

---

Originally Posted by XainTheGreat

Lalalalalalalala...

I live in the datacenter and I'm not having problems :D

---

Ok! Your post was obviously very constructive. You don't have problems so therefore everyone else in this thread must be lying!!! Fanboy rage lalala.

Btw I'm not paying/playing anymore. Salutation!

Quote:

---

Originally Posted by XainTheGreat

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

---

Hey LOL thanks for the laugh dude but how does your trace PROOVE ANYTHING at all???

Learn how to watch a video fanboi if it wasn't square who paid for the awful net code who was it? If it wasn't SE who decided to lump all the servers together who was it? This FAULT has been in the game since 1.0 beta 1.0 release 2.0 beta and now 2.0 release it's still there and this game will always be a flaming pile of shit until it is fixed. Now i suggest you go white knight some other topic where you wont look like such a twa...........