Thread: .3 Second Positional Update Delay (Requesting Dev Response)

Originally Posted by Astarica

The client absolutely does less than any other client ought to in a MMORPG.

Let me put it this way - In other MMOs I wasn't able to tell the server to make me have x client side like you could in ARR, it's a very widely known exploit and why there's been a lot of hacks lately, so yeah ARR's client actually is a lot more "work heavy" than most other MMOs, which seems to be double-edged.

I get what you were saying but there's a lot of purposeful designs they did with it for reasons unknown.

If this is fixed..... Im sure it will solve a lot of problems of Boss fights in dungeons and people dont need to explode in rage.

Probably the most wild example of the server delay (not even latency, just the servers being slow) is that I can run a couple constant pings. One to google.com, which will be pretty constantly at 15ms, and then one to the datacenters at about 100ms. (The hop into Canada goes from 15ms to 85ms, then up from there). So 100ms to the servers. I can be auto running and cast Leeches on myself (1.0 sec cast, or 0.97 with some spell speed). Client side I can actually have the animation go off (no battle message because server side it really never happens of course), but what this tells me is that 100ms is accounted for in latency, and another 800-900ms is lost in the server taking time to process the fact that I'm moving and the spell needs to be interrupted, and send that back to my client.

I wish they would at least say "This is an issue, we're stumped on how to fix it, but we're looking into it."

Generally speaking, the best way to get a dev response is to write a normal thread on a subject of interest to the playerbase (and ideally, have it get likes, probably). The best way NOT to get it is to specifically ask for one. Everyone would live it if their threads got official responses regardless of the subject. Unfortunately, the people that scan the forums have jobs to do and cant spend all day long collecting responses from the japanese devs, traslate them, and post them here in a timely manner.

Second, you posted this on a friday night and the community team usually isn't active on the weekend.

As far as the thread goes, I don't know what to make of the situation. personally, in the most latency sensitive fights like Titan, the instant I step off a weight, I'm out of the radius and don't get hit (the maximum normal delay of .3 seconds, assuming starting to move at the beginning of such a tick). This certainly is a strange issue, and I do know a few people who just can't dodge weight of the land if their life depended on it, and I know they can't simply not be trying. But is this delay really about the updating of the player's position (the .1-.3 sec delay)? or is it really just the player having high latency, possibly doubling or tripling the response time in this situaiton? This seems questionable, anybody in north america really shouldn't ping any worse than 150 or so unless their ISp is terrible; Most of the people I know from europe have a ping in the low-to-mid 100s as well, which is not perfect but generally acceptable for online games; and these people I know are able to fight titan just fine.

Only the fact that despite 140+ pages on the topic with videos etc and not a single response from SE shows how clueless they are in resolving this issue and they'd rather remain silent than admit it.

I've cancelled my sub until they fix this as the game generates more frustration than fun at this point (and we play for fun!). I'll be watching the forums when pvp comes out as the level of frustration will certainly be raised accordingly.

I've been playing another MMO at the moment with the same dodging mechanics as I wanted to be sure it was game- and not connection related and I am always in sync with what I am seeing on my screen. No delay in dodging (I prefer the word "delay" as to me I dont see lag in FF but a delay in everything that's happening). So it's clearly an SE issue.

It's entirely in their hands now.