No plans to fix the atrocious netcode?

[Unruhe]

I pose a question to the people in this thread. Why not post where they said to about said issue instead of the GD as they told you to go there? Means they're more likely to look at the issue if a lot of people post there instead of here.

They told us to post in "Website Feedback" -- What part of any of the posts on this topic (or topics on the same subject) implies that it belongs there? SE just doesn't want people highlighting their inexcusable netcode on subforums that actually get a lot of views.

Edit -- It appears that the original thread was unlocked a few days ago. I don't tend to check locked threads, so hadn't visited it in a while. I went back to get the link to the post where the mod told us to go to "Website Feedback" and found the thread reopened. The link in question was also changed to direct to the "gameplay" subforum.

[Alhanelem]

So, this thread got locked with a semi-canned response telling everyone in it to go post in the website feedback forum instead. I guess that means the piss-poor 300ms client polling that can and does absolutely ruin the game for (some) players isn't a concern for the devs?

so you have access to the netcode codebase to tell us how piss poor it actually is? Wow, what position do you hold at SE?

Idk, I don't find the combat clunky or unresponsive. Maybe I'm just lucky?

Agree Totally with a Aussie 310-370 ping

You're obviously trying to connect to the North American servers. You can't seriously tell me you get those pings to the JP servers, which are not that far away from you? You realize that there are english communities on the JP servers, especially the legacy servers and specific other non-legacy servers?

You should seriously consider transfering to a world on the JP data center. Just because they're in Japan, it doesn't mean they're JP ONRY. They're not.

That's as "no intent to fix it" as it gets.

That doesn't in any way mean "no intent to fix."

[Alcyon_Densetsu]

This 300ms polling is a game-breaking issue for me, and I really hope they do fix it somehow; no client prediction is also very bad considering all the existing titles using it, and therefore theoretical methods available.

My guess is that a much, much lower interval would at least be a solution (30ms max would be acceptable, I guess); client prediction (by interpolation or extrapolation, I don't know) should be considered too. Most AAA MMORPG do this, and it's just expected for an enjoyable and actually challenging PvE/PvP. Right now it's frustrating, and since I don't do "rage" in games, it just makes me laugh at how badly this netcode was designed everytime I get hit by an AoE that I had seen myself escaping on the client.

[Vestall]

This is why I did not resub, it's terrible in almost every dungeon

[Miiu]

I experience the same problem with getting dmg even though I was already outside the marked area before it disappeared but I agree with the people saying that SE will fix it. I remember other mmos where dungeons etc where unplayable because of server crashes/freezes ms spikes for months after launch. So while annoying it is not as gamebreaking as people make it out to be. There are worse examples.

[Namko]

Titan HM is exactly the same as Ifrit 1.0 eruptions. Love the game but this is a huge disappointment. You dodge by prediction, i.e. it's already happened server side. I thought this was one of the main issues that lead to 2.0. Come on SE, give us some update please.

P.S. Does anyone close to the server have it any better? I am UK and ping 85ms to Ragnarok.

Edit: Read this http://forum.square-enix.com/ffxiv/t...-fix-something.

[M4Fade]

Dunno why they don't just come out with this one already xD

LOL. This!

[Dano]

yea the thread locking move was really uncalled for, it just only confirm they don't give a rat's ass about improving game response and fluidity.

[Omagana]

Agreed, something needs to be improved.