Standing out of the red, and still getting hit

[nulian]

Do you live in Europe. The EU tag on the servers is nothing more then timezone thing they are in America. So for European players its almost impossible to evade stuff.
It square enix totally not taking European players serious. latency from EU to US is way to big for games you need to evade stuff.

[BlazeChronic]

This is a case of madcuzubad, unfortunately.

React faster. The damage registers at about 85% cast bar completion; Even if you avoid it last second, and you were in the area at roughly 85% cast, you ARE getting hit. Learn the mechanic, deal with it, and move on. It was much worse in Beta.

You should be grateful that they even added a red AoE marker for you to avoid. There is no 'issue' and nothing is going to be 'addressed'.

Lastly, you are a GLD, you should be shield bashing the majority of those casts, anyways.

[Vektrat]

Hello, I just made a thread that recaps this among other issues (all are because of the same).

http://forum.square-enix.com/ffxiv/t...s-everybody%29

[Kenka]

UK Player here and never had a problem avoiding AOE attacks, except when it's my own fault, so I think this is not the case :s

Another EU here. I can say that latency DOES play a non-negligible factor here. Depending on the time of the day (the quality of my internet connection varies greatly from time to time...) I can dodge AoEs easily or I get hit even when apparently I'm several yalms out of the red circles.

Quick reflexes are a must to avoid AoEs. Sadly, reflexes alone do not guarantee your safety :/

[Lexarious]

It was like this in the beta but a lot worse. People were also saying it was intended but it's pretty obvious that it wasn't and it's been fixed for the most part.

[KogaDrake]

what my experience has been is in open world i never get hit, but in dungeons I do still have issues at some points. My guess is that since it seems to work correct in the open world (low stress on server due to login restrictions due to duty finder server issues) and not well in dungeons (i.e. on the duty finder server) it is due to the heavy load on the DF server, and the problem should lessen with the addition of new DF servers tonight. But we will just have to wait till tomorrow to see.

[Petrified]

Whenever you see that red thing, get out ASAP.

[tuseroni]

yeah it's basically a discrepancy between where the server thinks you are and where your client thinks you are.
you may notice when everything freezes you can still move, this is because movement is done on the client side with updates to your location pushed asynchronously to the server. this has some unfortunate consequences (such as being able to move in front of an enemy who aggros but who's model hasn't loaded yet, or in this case the server thinking you are where you were a second or two ago)
if you want a good gauge of your latency go mining, compare the time between when you hit the button to mine and when he begins to swing(note SE: a ping timer would be nice) in on JP servers but i'm in america so there is a noticeable lag between those events as it has to negotiate with the server on each swing to keep cheating to a minimum.

--edit--
also, the things people above have mentioned (get out as soon as you see red) is a good workaround but that's all it is, a workaround.

[KogaDrake]

Whenever you see that red thing, get out ASAP.

This will work for a while, but much of endgame has no red. the crutch of showing you where the attack hits gets pulled away latter and you need to watch the cast bar, see what is being cast and know if it is a frontal line, frontal cone, or 360deg aoe field and move accordingly.

[TitanSlayer]

I think this issue is because they took out the animations from 1.0 and replaced it with the sliding movement. They need to correct this. Animations and better combat are what this game needs apart from the server issues !