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

[TheRac25]

the best is when you are killed by a mob that you just killed and you dont have any dots on you
horrible servers all around

[Unruhe]

I actually didn't realize people were having this issue. Myself, my boyfriend, and his brother have always dodged just fine without any issues. I wonder where the lag and latency is coming in from? Nonetheless, in every party I've been in I've tried to help out others by letting them know they can use Sprint during the fight if they are having a lot of trouble dodging in general.

It could be luck, or just prudent reaction times.
The problem with the way the game works right now is that every player essentially has a variable amount of latency because the server only polls character positioning every 300ms. Depending on how close you are to the next poll, you could move and have the server update flawlessly. If you start moving immediately after a poll, it effectively adds 300ms to your reaction speed, which can be a killer.

What SHOULD happen is:
AOE cast initiates
AOE cast completes and server checks position of all players in vicinity
Players in the effect are damaged

What IS happening is:
AOE cast initiates
Server polls character locations
AOE cast completes
Server applies damage to all characters in effect range at the time of the poll, regardless of whether or not they moved

It's also a playstyle thing: If you see red and move INSTANTLY regardless of what you are doing, you will generally avoid getting hit so long as your connection is decent -- there is usually enough time to move to safety if you move as soon as the red appears. Problem is with casters and occasionally DRG with their jump lock, it can be tempting to try to finish a cast or an animation. "Oh, well he's casting a 1.5s spell, and I have less than that on my cast, I can finish my cast and move" would work in any other game, provided you moved out of the AOE in time. The polling artificially lowers the amount of time you have to escape an AOE, so any kind of delay can easily result in the player getting hit.

[Kewitt]

I never had any issue as a WAR.
My hubby BRD got hit 3-4 times.
Healer Got hit.
Other DD got hit.

Sometimes just knock back to the edge if your far enough away from it you don't fall.


4 Duty finders later we got it.
The key for anyone having issue, is don't wait for the AOE attack. Start moving as soon as titan turns away form the tank. Never be on the same side as the tank.
As for the video, That's really bad. Never seen that far away and still get hit with AOE.

[Silverwalk]

...
What SHOULD happen is:
AOE cast initiates
AOE cast completes and server checks position of all players in vicinity
Players in the effect are damaged

What IS happening is:
AOE cast initiates
Server polls character locations
AOE cast completes
Server applies damage to all characters in effect range at the time of the poll, regardless of whether or not they moved

Thank you, your explanation is clearer than my attempt http://forum.square-enix.com/ffxiv/t...=1#post1267314

So in the worst case you have to be out of the red before the cast bar finishes by:
300ms + Your Latency + Server processing time

For example with 200ms latency that's more than 500ms or 1/2 second (we don't know how long the server processing time is).

edit: and what's worse is you get a double whammy with latency because you don't see the cast start until the server message arrives at your computer.

So 100ms of extra latency means you have 200ms less time to get out, nearly 1/4 of a second less!

To the next post: exactly! This is why videos show dead bodies sliding long the ground lol, the server says you're dead but is catching up with your movement data afterwards.

[SKYeXile]

Thank you, your explanation is clearer than my attempt http://forum.square-enix.com/ffxiv/t...=1#post1267314

So in the worst case you have to be out of the red before the cast bar finishes by:
300ms + Your Latency + Server processing time


For example with 200ms latency that's more than 500ms or 1/2 second (we don't know how long the server processing time is).

Well imagine this as a scenario. A 1 second cast attack. on 200ms ping, factor server ticks at every .333 seconds and client sending packets every .333 seconds.

[1]00000 Server tick sends packet data for AOE attack
0.100 AOE shows up on your client (remember 200ms is for a round trip)
0.300 You react and begin moving. (avg 200ms reaction time)
[2]0.333 server tick and your client sends data.
[3]0.666 server tick and your client sends data
0.700 You have cleared the AOE. your client holds onto this to go with the next packet due to be sent at "1".
0.766 server receives your new packet 3 location
[4]1 server tick, aoe explodes, server calculates based off your last known position(packet 3) your client also sends data that you have moved
1.100 you receive packet that you are now dead.
1.100 server receives your updated movement data.
[5]1.333 server process your new movement data, and sends you packet: "LOL, YOU ALREADY DEAD BRO!"

[Kupofried]

The saddest part of this issue, is that if they don't fix it they latter will threat us like cheaters because there will appear people who will exploit this to do many things here's a short list:
1)teleport to the exact position they desire(hello gathering points, hi end boss).
2)killing someone in pvp after being dead(want to see a corpse kill you?).
3)being able to resurrect mine times as you like( just one cast and outside the grace period it already grants you)
4)dupe items.

[Sneakaboo]

I wouldn't hold your breath for any further fixes, although it would be wonderful if they improve it. We have to learn to work around the problem by moving before the cast begins. You can either do this by being constantly on the move or memorizing the attack patterns so that you know a second or so before the cast begins to start moving.

For people with over 200ms latency a good guideline is: if you can see the red circle and you are not already moving, you're dead.

You are pretty much right here.
Especially since the servers don't seem to handle the load and tend to lag as well adding even more delays on top of it.
If anything the last maintenance made it worse for me with the constant lag spikes during peak hours.

But here is the main question, does the majority of the players want to do end game when this is the set standard?

[Yiell]

keep on trying until you succeed. The only thing that you need to fight is yourself.

[DuferBloodmoon]

Why? Because I can't dodge the @#$%ing AoE. After hours of practicing in the duty finder and then going in with my free company I still failed over and over again.

Then I tried to react before the weight actually casted. It worked the first few times but then I just ended up running into other people's weights.


EDIT: Thanks to the person who added this link to the discussion:
http://www.youtube.com/watch?v=G5g4T...ature=youtu.be

It seems like it's almost worse on weights too. I will look for a video to add to show that this problem also happens with weights.

It all seems fine to me, except for the horrendous DELAY from the servers. The video you linked is proof. Most of us are experiencing that and it's not viable for being competitive in any way. Regardless, about the titan fight itself, learn when he uses weight and move BEFORE he even starts casting.

[Sebyos]

I hate to say it, but it's on people's end. I have 13ms, I'm capped my fps at 60 and I don't get hit by anything in Titan Hard Mode unless I screw up real bad or like that funny attempt yesterday when I got freed from a rock in a landslide XD was funny tough: ''I'm freeeeee guys yay ... Ahhhh faaalliiinnnggg