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

[Altena]

I just did this nine times(but with leeches as a SCH). Each time the bar fully filled and it looked like it casted, but the chatlog says it was cancelled. At least it's consistent. lol

Since you're so close to completing, try hitting Fey Glow on your support fairy and do the same thing. See if you can actually get a few off.

[Namko]

snip.

Took all gear off. Always between 70 and 30 interrupt. Never ever saw spell complete on 50 odd tries.

I really really hope it gets fixed, I can feel your frustration.

[Gravehill]

Here's another test for you -

Run in a straight line (do not stop) and cast Esuna.

What point in the cast bar does it finally interrupt for you?

For me it will sometimes interrupt at around 00.25, other times the bar will completely fill, animation will go off, but in the chatlog it will say "You cancel Esuna".

I think Esuna is a really easy way to test latency on casts because of this, as it's about a 1 second cast time, which makes it very easy to see how long it actually takes for the server to tell your client that you interrupted the spell... For me it is basically between 700-900ms... Pretty crazy huh?

Ive done this with summoning a mount - I can mount up while running and the cast bar gets pretty much 100% full before it even interrupts. I get 20 ping to the NA server.

[Altena]

Ive done this with summoning a mount - I can mount up while running and the cast bar gets pretty much 100% full before it even interrupts. I get 20 ping to the NA server.

Didn't think of mounts, but yep that's basically the same as Esuna/Leeches. Cast time seems the same / similar.

So it seems you are experiencing the same problem as others here. 50/50 on spell complete is 50% too many completes. 300ms position check is at least 250ms too long if they are going to server authenticate everything. Always been 70 and 30 interrupt means you are playing at 700ms - 300ms latency for that, which is solidly in the "terrible" category.

These are the issues we are referring to and talking about, issues that every single player is experiencing no matter what their connection or PC.

Well yes I don't think Namko was really disputing the fact that there is some degree of latency there.

The one thing I will agree with some of the people in this thread is that internet / computer does have SOME effect on the latency, but overall it's a compounding issue.

Poor ping (due to even geographical distance) as an example means that once your client sends the data, it still takes 250ms (well ping dependent) to send to the server, when paired with a poor check interval (currently seems to be about 300ms), this is compounded to 500ms or so, then remembering it takes another 250ms (ping dependent) for the server to send it back to the client and say "that action is invalid, you need to cancel that". So this is probably the sort of place we are seeing this 700-900ms latency... The rubber banding effect of client > server > client..

When someone lives right next to the servers in montreal and gets 5ms, they only have to deal with the check interval, which is why the issue is still present but not as obvious.

Well that's my understanding of the issue..

[StarBright]

It's 50/50 on spell complete. But we know about the 300ms position check.

Always between 70 and 30 interrupt.

So it seems you are experiencing the same problem as others here. 50/50 on spell complete is 50% too many completes. 300ms position check is at least 250ms too long if they are going to server authenticate everything. Always been 70 and 30 interrupt means you are playing at 700ms - 300ms latency for that, which is solidly in the "terrible" category.

These are the issues we are referring to and talking about, issues that every single player is experiencing no matter what their connection or PC.

[Xystic]

My brothers and I (A family of gamers) got together one weekend for a 4 man dungeon. I was unable to dodge any aoe with my older laptop. Sitting side by side, we noticed that my cast bar would show up slightly after theirs and would finish casting after theirs were already casted. After 45 minutes of deaths, I switched to a newer up to date computer and the problem with the aoe-lag was solved. We also tested this on an older gaming pc we built 5 years ago in WoW's day and it was also having the same problem with all settings set to minimum.

Whether or not we are all affected to some degree I don't know,the 100-300ms. The only way to actually test this is to have multiple same top notch computers test for the delay I guess and then for lesser computers and so forth. Testing it for yourself will just give you results based on your system I feel. Sitting side by side with my brothers clearly shows an older pc performing poorly, especially my laptop for aoe.

[Norna]

(Snip for word limit...)

It's not computer specs with me:
Windows 7 Ultimate 64 bit
Intel(R) Core(TM) i7-2600K CPU (a high-end CPU)
16GB RAM
NVIDIA GeForce GTX 690(VRAM 4014 MB) (A powerful gaming card)
Samsung SSD 840 Pro (was considered the fastest and most reliable SSD through most of 2012/2013 by most reviewers)

On top of having a Tier 1 ISP. On top of having a screen with the lowest delay possible (and still I capped at 60fps just in case). On top of having arguably (between three high-end) the best air cooler possible. On top of their benchmark telling me that I should be able to run laps around their game thrice over when I tested it (and became bored during testing and watched a 1080p movie during the test and even with those resources busy, I was told that my computer is more than enough for this game).

May I repeat that this is the only game in which I am having these issues.

[Reeth]

I've successfully been able to dodge the weights 100% of the time, but that's only by anticipating when its going to happen and start moving before he casts it. If I don't do that, then it's usually iffy if I'm out of it, even if I'm visibly out of the circle before the animation goes off. I have found that jumping after I'm out of it will force the server to recognize where I am, which can also help in dodging it, but they do need to fix this issue.

[Bearssi]

People have used computer specs as an excuse for this and have not realized to calculate how much it really values in what you see on screen and reaction times.
I am not expert in calculus and these are just what ever comes to mind.
If a player has 10 frames per second which is a frame every 0.1 seconds if the frame occurs in steady intervals. This means the 0.3 seconds (rumored position check) + latency + invisible frame can actually cause you to see the cast bar and danger areas 0.5 seconds later than it occurs server side. So computer specs do contribute to this by smaller factor and only when your fps is really low.

[PerrythePlatypus]

People have used computer specs as an excuse for this and have not realized to calculate how much it really values in what you see on screen and reaction times.
I am not expert in calculus and these are just what ever comes to mind.
If a player has 10 frames per second which is a frame every 0.1 seconds if the frame occurs in steady intervals. This means the 0.3 seconds (rumored position check) + latency + invisible frame can actually cause you to see the cast bar and danger areas 0.5 seconds later than it occurs server side.

My fps is a non issue, as it's at 60 in a 4 man dungeon or a 8 man raid and I experience the flawed position check , latency or w/e you want to call it.
I'm pretty darn sure most people don't game at 10fps, so you can throw this theory in the trash. And the issue doesn't scale, or fluctuate based on fps.
Fps has nothing to do with it.

There is nothing rumored about the position check. It is fact stated by Yoshida. I have seen several posts in the last few days reference this as speculative or other synonyms. It.Is.Fact.

Lower end specs certainly can cause this issue to be more predominant. I have an i7 4770k, 8gigs of ram, GTX 760 OC and even I get this issue. This was built into the game by choice, and it was a bad choice. As many have said all you have to do to see the issue is Cast a spell and begin moving. The spell does not immediately cancel. Other ways, run up to an object and interact with it. Stone vigil is good for this. If you do not come to a complete stop and pause a moment you will start to use the object than get interrupted. Regarless though, I could quad sli titans and OC my cpu to 4.7 ghz and this issue would still occur because it is caused by their servers and not our machines.

^^

well my free trial is up in a few days and guess what SE. i won't be subbing, because of this problem. good luck with pvp lol!

This.

The funny thing is the white knights in regards to red circles, their big solution is "move before you see it".
Clunkiest MMO I've ever played.
This isn't to say I don't care...I do, or I wouldn't have leveled to 50 or bothered posting on forum, but I'm done because SE clearly does not care.