Red Ring of Death!

[Borfin]

Just... stop calling it lag.

It's not the core issue, the devs themselves have confused the core issue for complaints of lag and this fix does not solve said core issue.

The problem is the positioning check delay and it's a design problem. It's a code problem. It's not a computer, ISP, connection or anything similar problem.

Call it lag and they'll try to fix the wrong thing. Again, they've already confused it once already.

It's not the first time a game has had this problem. We've seen it in other MMOs. Those of us with experience know how to differentiate via spellcasts and other forms of lag testing.

It's not lag.
It's not FPS.
It's not an issue with people moving too slowly.

[Araye]

Just... stop calling it lag.

It's not the core issue, the devs themselves have confused the core issue for complaints of lag and this fix does not solve said core issue.

The problem is the positioning check delay and it's a design problem. It's a code problem. It's not a computer, ISP, connection or anything similar problem.

Call it lag and they'll try to fix the wrong thing. Again, they've already confused it once already.

It's not the first time a game has had this problem. We've seen it in other MMOs. Those of us with experience know how to differentiate via spellcasts and other forms of lag testing.

It's not lag.
It's not FPS.
It's not an issue with people moving too slowly.

That is the best description I've heard so far as it precisely describes all the problems I experience: positioning check delay. PCD

[Trancery]

Just... stop calling it lag.

It's not the core issue, the devs themselves have confused the core issue for complaints of lag and this fix does not solve said core issue.

The problem is the positioning check delay and it's a design problem. It's a code problem. It's not a computer, ISP, connection or anything similar problem.

Call it lag and they'll try to fix the wrong thing. Again, they've already confused it once already.

It's not the first time a game has had this problem. We've seen it in other MMOs. Those of us with experience know how to differentiate via spellcasts and other forms of lag testing.

It's not lag.
It's not FPS.
It's not an issue with people moving too slowly.

This guy is right. Everyone who claims there is no delay issue in the game (ESPECIALLY THE OP) are completely and utterly delusional.

[Parodine]

Am I zoomed out far enough yet?


Oh wow! Dodging landslides IS easy now.

[Tupsi]

It's not lag.
It's not FPS.
It's not an issue with people moving too slowly.

So basically according to you - It's impossible for anyone to dodge anything by design.

[Gamma621]

I currently have the best possible connection in my area.
At high traffic hours, I still get between 30mb and 35mb down, up to about 45mb+ at best.
I don't lag ANYWHERE in this game other than when I try and do Titan HM.
So it's CLEARLY an issue with my ISP and not the Titan HM instance servers that a lot of other people also have problems with.
Logic.

[Sunarie]

So basically according to you - It's impossible for anyone to dodge anything by design.

No, he is like me and able to separate the problem from lag. Lag itself is not what causes people to get hit when they were out of an AOE on time, otherwise the issue would be present in every other MMO (as every MMO has at least a few people connecting to it with latency problems) and it isn't. The actual issue is one in the coding. That issue is aggravated by lag, but not caused by it. There is a difference.

Every single person in the game is effected by the actual issue. The issue being the delay, which Yoshi himself has said everyone will see a .1 second delay on cast bars. So that's what you get at minimum. The difference is the degree to which they are affected. As stated multiple times, if a 500 ms connection is adequate to play every other MMO on the market and be able to dodge AOEs provided I can move out in time, then the industry standard upholds that I should be able to play FFXIV with a 500 ms connection. That isn't the case, or even close to the case. SE is so far off the ball here.