Effects of ping/latency on animation lock and ability to perform rotations normally.

[Aco505]

Bumping as a reminder that this is still a problem that somehow 3rd party tools have solved. Console players however don't have access to those. I'm hoping that content creators and streamers can directly ask Yoshi-P about this issue during the upcoming media tour.

They already have all the necessary information thanks to Nekkowe but there's been no news whatsoever on it.

[WeebPolice]

Improved netcode would be all the more useful to crush our enemies with, citizen. This has the department's vote of approval.




Favor the road traveled by few.

[AluneTempest]

After seeing Yoship testing Viper during burst window with low GCD doing triple weave and the job itself need to weave between those GCD`s i just necro this thread.

Reaper already have this problem on enshroud, is very cluncky doing 2 GCD`s + OGCD during enshroud with high ping, Viper will be even worse.

Can SE please finally fix that problem and people don't need to rely on 3rd party to be able to play the way it was meant to be played by the devs?

The OP itself explain eveything about the problem and how SE can simply fix it.

[HikariKurosawa]

I like how a lot of this thread is people justifying cheating so they can double-weave when they shouldn't be able to.

To clarify, if a job has 1 second gcd, even with 400ms ping you're not going to have an issue with clipping on a single weave. 400ms is basically unplayable levels of latency.

[Aco505]

Those going to the media tour should, once again, ask Yoshi-P about this to get a clear and direct answer. There's still no news on the feedback Nekkowe sent them.

[Balmung_Griffin]

This thread should be pinned on General Discussion, really, for how long will this go on? This very thread is making 3 years anniversary.
Holy Moly, this year I'm throwing a party with cake, skyrockets and some bottles of Realm Reborn Red at my FC, marking 4 years of this issue without a solution...Geez.

[Wanzzo]

Thumbing again this up... you know... just to make it always visible

The hope for a better future is always the path followed by the ones that walk in the light of the crystals... even when we go dark, sometimes... :3

Someone put the ideia of making a "FFXIV - part II". I loved it!

A new engine, more modern and all these issues fixed (alongside hats for Vieras, a South America DC, more languages ingame, and so on...) It would be absolutely awesome!

[Roda]

I just dare SE to have a fanfest on the east coast and have the devs try to play normally. I wanna see it!

[Swordsman]

A new engine, more modern and all these issues fixed (alongside hats for Vieras, a South America DC, more languages ingame, and so on...) It would be absolutely awesome!

Yep, thumbs up for all of this.

[RascalCase]

In it's current state, there's no reason animation lock is handled by the server at all. Even if they fixed the current system (say by updating the animation lock duration after receiving it from the server rather than resetting the timer), all the server does is acts as a database for the animation lock durations for each skill, which is completely unnecessary. If animation lock was handled completely client side, that would fix the ping issues and any inconsistencies in animation locks caused by delays in server response.

This wouldn't make cheating any easier either. There's already no server validation, seeing as there exists tools that allows for triple weaving. Right now, all the server does is tells the client how long the animation lock should be, it doesn't care how fast the client actually uses abilities. Their current approach somehow combines the downsides of both client side (easy to exploit) and server side (latency) solutions.