Why the netcode issue exists, and why it cannot be fixed.

[Sunarie]

Bump cause this thread, of any of them.. really needs to stay on the first page. Lots of beneficial discussions that maybe SE could take note of.

[Alcyon_Densetsu]

Bump cause this thread, of any of them.. really needs to stay on the first page. Lots of beneficial discussions that maybe SE could take note of.

Yep!
Especially as we close in on the next LIVE Letter with a pile of questions about the netcode/lag issues.

[Wildsprite]

atleast 1 person mentioned this was client side polling. the issue with that is Yoshi-P confirmed it was server side polling

Yep!
Especially as we close in on the next LIVE Letter with a pile of questions about the netcode/lag issues.

most of which said questions were ignored, they did say something about changing the polling in wolves den, great for PvP. but they really need to fix the polling issues in DF bosses like the primals, 3ms polling in those fights makes them difficult even though they are predictable. you only have to be 1ms off with their predictability to end up with the fight going completely down hill. factor in 3ms server side polling and any possible lag nomatter how small and that predictability goes to hell

[Sunarie]

most of which said questions were ignored, they did say something about changing the polling in wolves den, great for PvP. but they really need to fix the polling issues in DF bosses like the primals, 3ms polling in those fights makes them difficult even though they are predictable. you only have to be 1ms off with their predictability to end up with the fight going completely down hill. factor in 3ms server side polling and any possible lag nomatter how small and that predictability goes to hell

Actually, they addressed the question that many players were being hit by AOEs they were out of directly. Here's a full translation of their response, "Q2: You have said that in FFXIV: ARR, the character's position is checked by the server once every 0.3 seconds. However there are times where the character receives AoE damage even though the character on the screen is outside of the range. Seems like the information on character's position is not up to date. Is there any plan to make an adjustment to this?

A2: If we apply faster response times in all areas, the load on the servers will be too much. Therefore, while it will only be for certain areas (for example high-level content and the Wolves' Den), you will be able to notice the faster response times. Please stay tuned!"

What's that mean? High-level content is basically end-game (I don't really see how it could be interpreted another way), and Wolves' Den is PvP. So they are adjusting it for both. The bigger win though, is that they realize it's a problem and are now trying to work to fix it. Even if they start with something that's small, they still recognize it's there.

Please don't go say they're only working to fix it for PvP though, that's just not true.

[Sybreed]

Actually, they addressed the question that many players were being hit by AOEs they were out of directly. Here's a full translation of their response, "Q2: You have said that in FFXIV: ARR, the character's position is checked by the server once every 0.3 seconds. However there are times where the character receives AoE damage even though the character on the screen is outside of the range. Seems like the information on character's position is not up to date. Is there any plan to make an adjustment to this?

A2: If we apply faster response times in all areas, the load on the servers will be too much. Therefore, while it will only be for certain areas (for example high-level content and the Wolves' Den), you will be able to notice the faster response times. Please stay tuned!"

What's that mean? High-level content is basically end-game (I don't really see how it could be interpreted another way), and Wolves' Den is PvP. So they are adjusting it for both. The bigger win though, is that they realize it's a problem and are now trying to work to fix it. Even if they start with something that's small, they still recognize it's there.

Please don't go say they're only working to fix it for PvP though, that's just not true.

Exactly, problem recognition combined with an immediate remedy to the two most dire areas of the problem = we should be happy and stay positive.

[Wildsprite]

It is not 3ms. It is 300ms...

I stand corrected, you are right it is 300ms

Therefore, while it will only be for certain areas (for example high-level content and the Wolves' Den), you will be able to notice the faster response times. Please stay tuned!"

What's that mean? High-level content is basically end-game (I don't really see how it could be interpreted another way), and Wolves' Den is PvP. So they are adjusting it for both. The bigger win though, is that they realize it's a problem and are now trying to work to fix it. Even if they start with something that's small, they still recognize it's there.

Please don't go say they're only working to fix it for PvP though, that's just not true.

this should be fixed for all instanced battles, not just high level content and PvP. that is the point. fixing content that only high level players will see is bad. especially if you want to get new players into the game

[Katai]

I guess this is good news...

Beta 4: "AoE dodging feels sluggish"

*FIX*

Launch: "AoE dodging still sluggish. Finding it particularly troubling during Primals and Coil"

*2.1 FIX*

Future: "AoE dodging outside of primals and coil still sluggish"

...etc????

Long story short: Servers are expensive and they won't improve them unless they make more money... which they'll only get if they improve the servers.

Final Fantasy XIV: A Catch-22 Reborn

I certainly hope I'm wrong.

[Kith]

I guess this is good news...

Beta 4: "AoE dodging feels sluggish"

*FIX*

Launch: "AoE dodging still sluggish. Finding it particularly troubling during Primals and Coil"

*2.1 FIX*

Future: "AoE dodging outside of primals and coil still sluggish"

...etc????

Long story short: Servers are expensive and they won't improve them unless they make more money... which they'll only get if they improve the servers.

Final Fantasy XIV: A Catch-22 Reborn

I certainly hope I'm wrong.

While its not optimal, honestly if they just "fix" dodging by improving the poll rate in _all_ dungeons, then I can live with that. I'd obviously rather it be fixed in the overworld as well, but inside duty/instances would make it tolerable I think as these are the times when its crucial to dodge stuff.

[Sunarie]

this should be fixed for all instanced battles, not just high level content and PvP. that is the point. fixing content that only high level players will see is bad. especially if you want to get new players into the game

I am not disagreeing with you there, but they have to start somewhere, and bandage the issue somehow with a bit of urgency. Since increasing the rate at which positioning polls are done will create a very large load on the server, they have to be selective as to which areas they decide to apply the bandage. It makes the most sense to have them in the areas that are the most movement intensive, such as Titan. That isn't to say that this will be the very last thing they do to address it (at least I sure hope it's not), or that they shouldn't address it elsewhere. However, expecting them to immediately fix all areas with 2.1 is unreasonable. That's why I believe the mere fact they addressed it and are now making moves to try and improve it is so important.

[Koressa]

So bascially SE could spend the money to fix it now and technically make some of it back or keep it the way it is and have players leave in droves and lose money? I know for a fact when I get to the point where the desyncs with the AoEs are common, I'm done with this game. Things of this nature should not happen at all if SE wants to keep FFXIV open, and everyone knows it.