Horrible Server Lag Needs To Be Fixed ASAP

[Ranghar]

Hold down auto-run and start channeling a spell or summoning a mount. You will see anywhere from .4-1.0 seconds before it interrupts. The server doesn't even seem to know you are moving for that period of time which explains getting hit with AoE after you move out of AoE.

When I ping the actual server IP address of 199.91.189.21 I get a 70-80ms ping consistently, so it isn't my connection to the server.

Regardless, it feels as if I am constantly playing with a 400-1000 ping inside the game.

When we did hardmode titan, we had to instruct the raid to move BEFORE the bombs would explode or BEFORE the ground AoE popped to avoid it. This is a huge glaring issue and I would love to hear an official response on what if anything is going to be done about it.

EDIT: here is a good video to sum it up
http://www.youtube.com/watch?v=3leMnErroL0

EDIT: This one as well
http://www.youtube.com/watch?v=G5g4TM1fkCg

[Zyeriis]

Hold down auto-run and start channeling a spell or summoning a mount. You will see anywhere from .4-1.0 seconds before it interrupts. The server doesn't even seem to know you are moving for that period of time which explains getting hit with AoE after you move out of AoE.

When I ping the actual server IP address of 199.91.189.21 I get a 70-80ms ping consistently, so it isn't my connection to the server.

Regardless, it feels as if I am constantly playing with a 400-1000 ping inside the game.

When we did hardmode titan, we had to instruct the raid to move BEFORE the bombs would explode or BEFORE the ground AoE popped to avoid it. This is a huge glaring issue and I would love to hear an official response on what if anything is going to be done about it.

I haven't experienced a single instance of this. I'm not saying there isn't an issue but, if it was the server, then wouldn't everyone be having this problem?

[complexxL9]

I haven't experienced a single instance of this. I'm not saying there isn't an issue but, if it was the server, then wouldn't everyone be having this problem?

Everyone is experiencing it, not everyone is aware of it / has problem with it / can tell a difference.

[Unruhe]

I haven't experienced a single instance of this. I'm not saying there isn't an issue but, if it was the server, then wouldn't everyone be having this problem?

As I've mentioned in a similar thread, it could just come down to playstyle. Judging by your avatar, I'd assume you primarily play a tank at 50. While this issue can crop up at lower levels, it's typically the tighter tuning (read: faster enemy cast times) at high level that make the problem most apparent. From the bit that I've messed with Gladiator, I know that you don't have any hard-cast spells as part of your main rotation, so the issue with moving casts or false interrupts wouldn't affect you.

This just leaves the AOE, which is a bit easier for Melee/Archers to avoid simply because of the 'instant' nature of those classes. If your latency to the server is low, and you always move the instant you see a red indicator, you will be very likely to avoid getting hit. Casters have a rougher time of it because it can be tempting to complete a cast ("My cast will finish in less than 1 second, that still gives me .5 seconds to move") but the location polling artificially lowers the amount of time a player has, which can cause a player to get calculated as a false hit if they only barely make it out of the red in time. Casters also have the "I moved but my cast kept going" problem compounding this -- because of the way the polling works, it's possible to complete a cast while moving if you move late in the cast. This can make you face the target or "stutter step" when the spell animation completes, which can cost valuable fractions of a second when trying to avoid a fast AOE.

[Musai]

*snip length* "stutter step" when the spell animation completes, which can cost valuable fractions of a second when trying to avoid a fast AOE.

This explains why I've seen my character "slide" in a different direction than I had been moving in while moving and casting an Insant DoT or after running out of the red and "sliding" into another direction than I had intended. I have also seen the cancel effect on my spells. And when I did Ifrit, I was totally frustrated. I would see the cracks turn red under my feet. I'd stop casting and strafe or run. I could see myself well outside of the explosion zone. Then I would watch my HP drop by half. That does not help a healer keep healing the group when you have to worry about healing yourself due to these delay response issues. And that was last week before the current issues continued to worsen. I won't even get into how bad the past few days have been. I just get sick of it and log out.

[Ruprect]

I haven't experienced a single instance of this. snip

Lies!!!

It does not matter what your latency to the server is you automatically have a .3 second lag. The server only checks your location 3 times a second. Fanboi's will be fanobois's. This has been accepted by SE as an issue and they are supposedly working on it. Everyday there are at least a few new threads on this subject.

http://forum.square-enix.com/ffxiv/t...ng#post1274569
http://forum.square-enix.com/ffxiv/t...ects-everybody
http://forum.square-enix.com/ffxiv/t...ng#post1287053

Apparently you are the magical computer that has found a way to bypass a gamebreaking server lag issue.

So tired of fanoi's saying there is no issue, when it has been admitted an issue by SE and added to the accepted bugs forum. This is a gamebreaking issue for most. It is especially obvious if you are a healer. You are unable to start casting a heal and then interupt it as it still goes off even with a second left on the cast bar. Heals also do not hit the target immediately, it usually takes a biut for it to show up. It is possible to get used to this and accommodate it but we should not have to.

[Riko_113]

Lies!!!

I don't believe he is lying, just unaware. As someone mentioned earlier, he's a tank(non-caster) which means everything he does is instant. This latency affects everyone for sure, but as a WHM I agree this issue is DEVASTATING for caster. Everything we do has a timer and bright flashy animations and it doesn't help that we're so squishy. I've eventually adapted to predict red zones and movement, and of course can use sprint on a whim as a caster w/o risk but I agree this shouldn't even be an issue!

At someone said earlier, having them at least lower the tick rate in instances to match other MMOs would have a huge impact on our ability to survive as a whole. Even if I have managed to avoid stuff, it hurts my soul having to heal so many others that don't.

[Tupsi]

Hold down auto-run and start channeling a spell or summoning a mount. You will see anywhere from .4-1.0 seconds before it interrupts. The server doesn't even seem to know you are moving for that period of time

The server knows you're moving, it just won't interrupt the spell casting/item use right away - has nothing to do with lag.

[SKYeXile]

The server knows you're moving, it just won't interrupt the spell casting/item use right away - has nothing to do with lag.

actually no, it doesn't know you're moving because it has a tickrate of 3, so anybody even with a ping of zero will experience upto 333ms of lag when doing anything, eg moving out of red shit, interrupting, casting. etc

[Unruhe]

The server knows you're moving, it just won't interrupt the spell casting/item use right away - has nothing to do with lag.

This is empirically false. Per Yoshi, the server only polls player locations every .3 seconds, or 300ms. This doesn't sound like a *huge* deal, but when added to actual latency, it can make a big difference in how XIV feels.

And it can feel pretty awful. I can run out of a red circle and still get hit by the attack when it goes off. As a BLM, I can start moving once I'm almost through a cast and complete the cast. I can run to a position, plant my feet, and start casting a spell only to have it "interrupt" early in the cast because the server thought I was still moving because the last time it polled me, I was in a different location.

The game server doesn't trust the client, at all, and handles nearly all combat-related calculations. This makes certain unwanted behavior like botting and hacking a little trickier, but it also completely screws legitimate players on tightly tuned fights.

Boss mob initiates AOE on server. After your latency, your computer/screen receives the red circle. {XXX} You start to move. {XXX} {YYY} You move out of the red circle. {YYY} The AOE cast completes, and damage is tallied and applied on the server and then sent to all computers in the encounter.

If you are lucky, then your 300ms polling intervals occurred at points YYY in the above scenario, and you take no damage. If you are unlucky, your 300ms polling intervals occurred at points XXX, which means your most recent poll had you in the red circle, so even though you moved out of it "in time" you'll still eat the damage for the attack, possibly dying and wiping your group in the process.

Great game design, that.