Was the 0.3 second delay fixed?

**MageBlack** · 12-19-2013 08:14 AM

I never had this problem before nor now so I can't really judge. I've always been able to get out and if i didn't i knew it was my fault. Can anyone (Sunri?) who had this problem before the patch comment here and let me know if it has been fixed?

Haven't heard a peep about it since the patch dropped so I figured it was a good sign, unless everyone was too busy fuming over the "Free Company Housing is too expensive" bandwagon. These things seem to come in waves, usually roar along for a while then disappear without a trace, rarely a "Hey! You fixed this! Thanks!".

The Thread topic was one that came and went as it seemed to be a persistent issue for some people (but not for others) so it would come and go. I do hope this has been fixed enough for people to be able to enjoy the game regardless of their hardware or connection.

**Reynhart** · 12-19-2013 08:19 AM

It's difficult to prove it, but i feel that dodging Titan's AoE is a lot easier now.
So I'll say yes, they changed something.

**Naunet** · 12-19-2013 08:22 AM

Supposedly they increased the rate at which the client checks with the server to 0.1. I wouldn't call it "fixed", as it's still rather backwards and can totally result in getting hit in AoE you're not standing in (something I ran into repeatedly yesterday when I don't normally), but it's... improved?

**Sunarie** · 12-19-2013 08:39 AM

I can't say. I've been having problems downloading the patch because my router is blocking the ports that need to be open, and the password to login to the router isn't working, not even after a factory reset of the modem/router hybrid, so have to call a tech to the house to see what's up. A friend is currently torrenting the game to me so I can even play it.

I saw one report of it still happening since the patch. I would expect it to be improved but not fixed. What they did was increase the amount the client sends information to the server.. so an improvement should be visible. However people with packet loss or latency hiccups will still likely get hit sometimes. A complete fix would require them to re-work the programming, which would take a very long time and a lot of money. Unlikely to happen.

The lull in uproar wasn't cause it stopped happening, just btw, it was because Yoshida actually addressed it in the Live Letter, which is all the majority of us wanted.

I would expect myself not to run into it anymore, just as a note, because it never really hit me bad to begin with. Usually I'm out of things before the 90% bar.

TL;DR Most people should see a noticeable improvement in their ability to dodge, but it will still be possible to get hit by AOEs you're out of.

**Dhex** · 12-19-2013 08:42 AM

I don't know I had no problems before but trying to play PvP is like having a visual seizure.

**BillyBones** · 12-19-2013 08:50 AM

Yes, it was fixed. I did titan today and it went really well. I was able to dodge everything.

**Aurelious** · 12-19-2013 09:52 AM

Fought Titan before and after. I didn't really detect an issue, but I didn't have much of one before the patch, so I'm not the best to ask.

However, I can say that temporarily invincibility on raise makes timing raises much, much more forgiving.

**SpookyGhost** · 12-19-2013 09:54 AM

It's fixed in certain instances, I think. Sometimes I still see it happening, like when DPS get targeted by last boss of Copperbell HM. Wouldn't say it's fixed but it seems to have improved in some places.

**indira** · 12-19-2013 09:59 AM

my connection got fixed, went from good to excellent

**Ladon** · 12-19-2013 10:00 AM

Originally Posted by SpookyGhost

It's fixed in certain instances, I think. Sometimes I still see it happening, like when DPS get targeted by last boss of Copperbell HM. Wouldn't say it's fixed but it seems to have improved in some places.

Patch notes state that the position update frequency interval was only reduced for the trials (primal fights) and PVP and that they would be monitoring its effect on server performance before expanding it to other instance types.

Thread: Was the 0.3 second delay fixed?

Thread Tools

Search Thread

Display

Was the 0.3 second delay fixed?