AOE issues preventing me from beating titan.

[Ramiren]

Well, I can safely say any dungeon content above lv40 is unplayable, with the possible exception of garuda.

10 days since launch and we still don't have a patch for a bug that was found in Beta Phase 3, this combined with the log in and customer service issues is absolutely disgraceful.

[Ramiren]

Oh and just for the record, the final boss, don't even try.

I've spent tens of thousands of gil on repairs, dying my way through all these bosses, only for square to make the last one unbeatable.

Fix your fucking game please.

[XenabelleS]

Let us hope this is one of the undocumented things getting fixed in today's patch!

[matu]

I have this issue too, i did titan for the first time today and I keep dying on the frontal AoE he does that throws you off the platform, even though every time i moved off it... It was a painful experience, why don't they just increase the time before the dmg goes off by like 1-1.5 sec or start showing the red zone 1 sec before?

[matu]

I have the same issue, i was tanking the Dragon from Brayflox's Longstop and the healer was getting pissy with me for being in the 'Fire breath' attack but my client showed me well out of the way.
I currently play from Australia on the Exodus server

My ping to the server (184.107.107.176) is 282ms so im assuming there is a 2.8 sec delay from client to server...?

Makes it hard being a tank!

It is 0.2 sec, ms being milliseconds (1/1000 of a second), so 1000ms = 1 second.

[Azazello]

One of the issues here is that the hit determination is made before the relevant damage animation takes place, and the damage coming off your HP bar is actually synced with the latter rather than the former. It was a conscious design choice on SE's part, but yes, you can sometimes run a long way out of an AOE zone and then see yourself taking damage. It's not your computer or connection, it's the way the game is. It's not that you're actually getting hit outside of the AOE zone, it's that you were inside the AOE zone when the game determined you were hit... as much as 2 seconds before you actually see it register.

That issue is actually a peripheral issue to something more serious, which is cast bar, AOE circle, ability animation, and hit determination syncing, where you can be out of the AOE circle/cone/whatever before the ability triggers but still get hit anyway. This was something that was brought up in beta, got a response from Yoshi-P, and unfortunately was not fully resolved for all AOE abilities. SE is aware of the issue and they already addressed it to their satisfaction. It's highly unlikely at this point that they will ever revisit it.

My advice, unfortunately, is to let it go. Despite the fact that you know it's happening and can even prove it with video evidence, the thousands of people who will blame you for imagining it or that having a shitty computer and connection will sap whatever enjoyment you are getting out of the game. SE is satisfied, the customers they care about are satisfied, that's pretty much the end of the story. If it truly is preventing you from completing content, and that makes you not want to keep playing, then it's time to look for another game. Others no doubt will join you as the same issues contribute to their eventual disillusionment as well.

[Kusumura]

One of the issues here is that the hit determination is made before the relevant damage animation takes place, and the damage coming off your HP bar is actually synced with the latter rather than the former. It was a conscious design choice on SE's part, but yes, you can sometimes run a long way out of an AOE zone and then see yourself taking damage. It's not your computer or connection, it's the way the game is. It's not that you're actually getting hit outside of the AOE zone, it's that you were inside the AOE zone when the game determined you were hit... as much as 2 seconds before you actually see it register.

That issue is actually a peripheral issue to something more serious, which is cast bar, AOE circle, ability animation, and hit determination syncing, where you can be out of the AOE circle/cone/whatever before the ability triggers but still get hit anyway. This was something that was brought up in beta, got a response from Yoshi-P, and unfortunately was not fully resolved for all AOE abilities. SE is aware of the issue and they already addressed it to their satisfaction. It's highly unlikely at this point that they will ever revisit it.

My advice, unfortunately, is to let it go. Despite the fact that you know it's happening and can even prove it with video evidence, the thousands of people who will blame you for imagining it or that having a shitty computer and connection will sap whatever enjoyment you are getting out of the game. SE is satisfied, the customers they care about are satisfied, that's pretty much the end of the story. If it truly is preventing you from completing content, and that makes you not want to keep playing, then it's time to look for another game. Others no doubt will join you as the same issues contribute to their eventual disillusionment as well.

They will revisit it at some point when enough people have taken notice (The game's just out of Beta, and there's a good majority that can't even play yet, let's not forget!) and demand it to be not fixed, because it's not an unintended problem, but changed/re-balanced.

[Solragor]

No, this has absolutely nothing to do with the point in time where it is determined if you were hit or not, when i can sometimes have JUST left the red zone a minuscule moment before the cast bar finishes and other times when I'm already standing half a mile away from the boss before he cast is even remotely finished and still take damage.
This has nothing to do with lag either, there's an acceptable ping from my location to the server, there's nothing running which could slow down my connection, there's no possible peer2peer throttling involved when I can download stuff on utorrent with 2mb/s and upwards.

This is entirely an issue on the servers, it may be poor coding, it may be the sheer overload the servers are experiencing I don't know and actually to be honest I don't really care.
I can accept it, if I take the damage because I fucked up, but most of the time I don't and I still get screwed over. And that is -not- acceptable at all.

[svann]

few questions first,
1. does duty finder put na and eu players together (if no then disregard the rest)
2. when doing DF the relevant latency is to the DF server, not your own server right?
3. DF servers are in na, correct?

If thats all true then I dont think it would help eu players very much to have an eu located server. They'd still be communicating cross atlantic for all dungeons.

edit: 1 more question semi-OT: is there an in game latency meter?
edit2: ok, patch notes answer Q1. NA and EU players DO get put together in DF. Im fairly certain the answers to Q2 and 3 have to be yes as well, so having eu based servers wouldnt help eu dungeon latency.

[Ramiren]

One of the issues here is that the hit determination is made before the relevant damage animation takes place, and the damage coming off your HP bar is actually synced with the latter rather than the former. It was a conscious design choice on SE's part, but yes, you can sometimes run a long way out of an AOE zone and then see yourself taking damage. It's not your computer or connection, it's the way the game is. It's not that you're actually getting hit outside of the AOE zone, it's that you were inside the AOE zone when the game determined you were hit... as much as 2 seconds before you actually see it register.

That issue is actually a peripheral issue to something more serious, which is cast bar, AOE circle, ability animation, and hit determination syncing, where you can be out of the AOE circle/cone/whatever before the ability triggers but still get hit anyway. This was something that was brought up in beta, got a response from Yoshi-P, and unfortunately was not fully resolved for all AOE abilities. SE is aware of the issue and they already addressed it to their satisfaction. It's highly unlikely at this point that they will ever revisit it.

My advice, unfortunately, is to let it go. Despite the fact that you know it's happening and can even prove it with video evidence, the thousands of people who will blame you for imagining it or that having a shitty computer and connection will sap whatever enjoyment you are getting out of the game. SE is satisfied, the customers they care about are satisfied, that's pretty much the end of the story. If it truly is preventing you from completing content, and that makes you not want to keep playing, then it's time to look for another game. Others no doubt will join you as the same issues contribute to their eventual disillusionment as well.

Thanks for the detailed response, after struggling to log on through error 1017, then being booted off with error 90000 and unable to log back in due to error 3012, I've got a while to respond.

Firstly if square enix consider this fixed, that is the pinnacle of lazy quality assurance, and bodes terribly for the future of this game. Secondly even if it's nothing more than a sync problem as you suggest, the intended fix only takes in to consideration classes who can see the enemy cast bar in the first place. This completely neglects healers, who absolutely rely on the AOE markers to avoid damage, as targeting the mob to see the cast bar between every single heal is impossible, and even were it possible, would we really be able to finish healing, target the monster, look at the cast bar and move before the hit? I think not.

I really don't understand why square enix has to reinvent the wheel on this, I mean it's quite simple

Enemy casts spell
AOE hit box appears
I move out of the way
Attack animation triggers
I don't get hit

But no, lets switch it up:

Monster launches attack
Hit box appears
you move out of the way
Attack Still hits you
Attack animation shows.

As for quitting the game, I'm going to see how my free trial pans out, and then decide. As I'm sure your aware the further and further I get in to end game content, the less and less willing people will be to accept a healer that always dies to AOE attacks. I've taken a ton of verbal abuse so far because of this, so I really can't see me sticking around for more. And to think, prior to release I was actually defending Square-Enix under the illusion that this was a simple fix and they'd have the game working for launch.