Yoshi P's Statement on Network Delay/Packet Loss

[RobynDaBank]

http://na.finalfantasyxiv.com/lodest...a451d5a8daa66f

They released this statement a bit ago. I skimmed it, and seems that it's finally under their radar - although they do mention it's because Japanese players are having this issue at the moment...
They do include the fact that they'll look into things for other parts of the world too.

I do see that they want us to give them information (again) about things like where we live, ISP, timeframes when the delays may spike, etc.

Honestly from what I'm getting this isn't anything regarding issues like animation locks and ping reliance. Which is a bummer when they mention packet-spoofing as against rules and avoided addressing it in the third-party tools notice too. Oh well, maybe I'm wrong?

Thoughts?

[Nekkowe]

It's kind of disheartening - I'm worried that the tunnel vision on packet loss will drown out the animation lock issue, which is both more immediately important to overseas players and a lot easier to address. I remember this exchange (https://forum.square-enix.com/ffxiv/...=1#post5926244) all too well. It was pretty frustrating.

[Deedlit]

"Since 6.1"
Pure comedy.
"There's no issue on our dev server."
Hmm.
And nothing on animation lock.

Absolutely out of touch.

[Larirawiel]

"Since 6.1"
Pure comedy.
"There's no issue on our dev server."
Hmm.
And nothing on animation lock.

Absolutely out of touch.

Cheers

[Deceptus]

"Since 6.1"
Pure comedy.
"There's no issue on our dev server."
Hmm.
And nothing on animation lock.

Absolutely out of touch.

Reminder, they said the exact same thing about the log in authentication error when Endwalker dropped. Until players starting looking deep into it and provided enough foolproof data (that Yoshi-P should have already had).

Then he said "oops, it was an old code bug we missed, sorry"

[Ronduwil]

Reminder, they said the exact same thing about the log in authentication error when Endwalker dropped. Until players starting looking deep into it and provided enough foolproof data (that Yoshi-P should have already had).

Then he said "oops, it was an old code bug we missed, sorry"

What makes you think he should already have had that? Lab simulations only go so far. That's why on issues like this they ask for players to help out with feedback. They're not trying to downplay our concerns; it's quite the opposite. He's asking us to provide them with the tools they need to get to the bottom of this issue. When he mentions that they can't reproduce the problem in their lab, he's not implying that we're lying; he's explaining why they need our help to resolve this. If everyone who has these issues submits their traceroute, they can look for patterns to help determine where the bottlenecks are, helping to pinpoint the source of the slowdowns. Issues with latency are generally caused by failures in third party ISPs and/or gateways. I would be shocked if SE ultimately found that these issues are in any way under their control. I'm just happy that they're investigating the issue, and the next time I experience lag issues like the ones I had over this past weekend, I'll be sure to submit the information they've requested.

[Johners]

"Since 6.1"
Pure comedy.
"There's no issue on our dev server."
Hmm.
And nothing on animation lock.

Absolutely out of touch.

Animation lock is a game design choice. Packet loss is a technical issue that's negatively impacting the game design choice. Even without animation locking, the packet loss would still be an issue for players experiencing it.

[KuroMaboroshi]

Animation lock is a game design choice. Packet loss is a technical issue that's negatively impacting the game design choice. Even without animation locking, the packet loss would still be an issue for players experiencing it.

Animation lock being a thing in general is a game design choice, but that's not what people mean when they complain about it in the context of the netcode.

The problem lies in the way animation lock is being applied at the moment, which is definitely not a game design choice, but a technical issue. People living further away from the server and therefore with higher ping have to wait longer between inputs than people living closer to the server, as the game basically applies the animation lock twice, once after a button press, and once more after the server's repsonse to said button press (this second instance overrides the first).

Unless Square actually intends for people who live further away from the servers to not be able to do the same things in-game as people living closer to the server, this is definitely not game design, but a known problem with the netcode that has persisted for years.

[Sacred_Nym]

It is, but it's also being artificially bloated by ping, which is what's causing the weaving issues.

[grinkdaboy]

"We are currently investigating the matter; however, we have not detected any issues on the development server."

no shit, really?