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

Originally Posted by Mishari

I know, it sucks.
The client is not optimized and SE has to do something about it.
But still, it helps.

Edit: Where did Yoshi say something like that? Thats ridicolous.

It was in a live letter, one of the more recent (most recent?).

http://www.dualshockers.com/2013/10/...cer-letter-ix/

Fourth paragraph:

"In order to beat Titan in hard mode, Yoshida-san advised to keep the camera farther from the character, as it makes it easier to avoid the primal special attacks. At the moment many find it too hard because they keep the camera too close"

Originally Posted by tymora

In those games...players bitch about "rubber-banding". It is not as perfect as you think it is.

I play "those" games so I'm aware of the issues. As long as we haven't found a way around light speed and as long as people with crappy internet exist, there will always be problems. There is no "perfect" solution, but using a predictive approach with rollback is pretty much the standard because it alleviates many of the network problems that people complain about. It's unbelievable that SE didn't adopt this.

Originally Posted by Sunarie

It was in a live letter, one of the more recent (most recent?).

http://www.dualshockers.com/2013/10/...cer-letter-ix/

Fourth paragraph:

"In order to beat Titan in hard mode, Yoshida-san advised to keep the camera farther from the character, as it makes it easier to avoid the primal special attacks. At the moment many find it too hard because they keep the camera too close"

LOL what a ridicolous answer.. Yoshi-san did try the game sometime not in "offlline/dev mode" ? Expecially from the EU? Meh.

They have to implement something like HSR (host state rewind) where the server recieves position data from the client with a timestamp.
When the server says there is an AoE attack it sends the info out to the client.
Now the client can evade as soon as he sees the red zone, and if he makes it out this information is sent back to the server together with the time where the player actually is at this moment.
The server compares the timestamps and now knows that the client was out of the damage zone before the attack.
Or something like that...

They had a similar problem in Mechwarrior Online a few months ago, where you would have to aim very far ahead to hit fast moving mechs. After they implemented such a HSR function and some tweaking the visible and the real position match almost perfect.

https://developer.valvesoftware.com/...d_Optimization

The fundamental problem is that SE chose to put in battle-mechanics which are fine for off-line FPS 'twitch' games into an MMO with all the issues the OP goes into.

GW2's 'dodge' mechanic works because it requires a single button-press to indicate you moved, so only a single client/server interaction is needed to register whether you were quick enough or not.

It's not ideal and frankly I think SE has gone way overboard of the 'get out of the red' to the point where many I know hate playing melee classes, but if SE insist on doing it they need to adopt a GW2-like mechanic that is largely (if not entirely) protected from latency/server-lag problems.

I have currently quit this game because of this issue and gone back to playing wow for now lol.

I won't be coming back until this issue is solved as it is game breaking and infuriating, I suggest you all do the same, vote with your wallet etc.

This problem is unacceptable for a pay to play game. We should also have actual EU servers not montreal ones.