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

[StarBright]

One of the major problems is that people like Namko (who I don't doubt means well and is honestly trying to help) simply do not understand the issue and incorrectly think they aren't affected by it. *Every* player, on *Every* NA/EU server, on *Every* ISP with *Every* possible PC setup is affected by this issue.

Here's the simple test: start casting a spell/ability, then move your character before its done casting, with 10-30 (100-300ms) left on the cast bar. Do this several times in a row. The spells will nearly always complete. If anyone can upload a video showing them successfully canceling spell/ability casts near the end, several times in a row, I'll be happy to buy you a 3-month sub. This goes for Namko, or any other player who doesn't understand this issue and mistakenly thinks it is about ping speed, packet loss, or anything else but SE's terrible, terrible servers.

[Norna]

I don't have packet loss. Done Leatrix Latency Fix. Done Port Forwarding. Have pinged all the game servers always been under 150. I move out of the red the moment it appears (or I'm already strafing away), I get hit 50-90% of the time. It doesn't matter if I use WTFast or try every other "fix".

Looking at guide videos of future Hard Mode fights, I have realized that I will never be able to do that content at this rate. Story Mode Titan might Landslide me stuck in the story as well.

I had less lag during Early Access, and now after a bunch of "fixes" I'm still in the red from the other side of the battlefield, apparently.

And before you question my ISP, it's Telia. They're Tier 1 on the internet backbone/network gig. If Tier 1 customers notice a unusually high lag (possibly game-breaking), things are bad server-side.

[Namko]

Here's the simple test: start casting a spell/ability, then move your character before its done casting, with 10-30 (100-300ms) left on the cast bar. Do this several times in a row. The spells will nearly always complete. If anyone can upload a video showing them successfully canceling spell/ability casts near the end, several times in a row, I'll be happy to buy you a 3-month sub. This goes for Namko, or any other player who doesn't understand this issue and mistakenly thinks it is about ping speed, packet loss, or anything else but SE's terrible, terrible servers.

- Interupted (greyed out)



It's 50/50 on spell complete. But we know about the 300ms position check. I moved when the cast bar was at the right border of R1 boundry. I can't tell if I was a bit late to move (under 300ms) when spell completed.

Would be nice to get an official response, some people are clearly not able to play as intended. ;_;

Edit - Between 31-40 left on cast bar it will always interrupt.

You can donate the 3 month sub to a charity of your choice ^^

[Altena]

Snip

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?

Want to hear the crazier thing? Very rarely (but it happens) the Esuna is not interrupted, even when continuously running in a straight line on auto-run..
This means that a full 950ms spell actually fit in between position updates.

While my ping is about double NA players (about 250ms), this does not explain why I can nearly, and sometimes actually complete a 950ms cast time spell while continuously running. My internet is highly stable, I do not visibly see any lag spikes, and my frames in a busy area range from 45-60 on max settings.

[Elim]

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?

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

[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.