Austerim wrote:Happens to me on Reaver when I get rooted and Slam someone then they're out of range. The window dragging on this server is really getting out of hand.

I'm not so sure its window dragging at all. I understand that problem and it may be solved on server side.

Blue wrote:

Austerim wrote:Happens to me on Reaver when I get rooted and Slam someone then they're out of range. The window dragging on this server is really getting out of hand.

I'm not so sure its window dragging at all. I understand that problem and it may be solved on server side.

he was trolling. its normal its becuz when the guy move, the range hit is higher u said it urself. after slam the guy is stunned, not moving so range hit is reduced

[quote="TugaPowah"]So,

They discovered the window dragging... Will Uthgard let this happen?

Till we get an official answer I will post here all videos. Starting now:

Xfaniax

you also need ban messenger mobs at dragon,they allways "teleport" from me,when i start fight them

Orihiime wrote:after slam the guy is stunned, not moving so range hit is reduced

Good analyzed. Anyway Uthgards stuns have the problem that you don't see immediate player stop.

Do the liveservers use a better mechanic?

Rector wrote:Do the liveservers use a better mechanic?

From server perspective I could make the player immediately stop. But due to delay in network communication this means that the stunned player has to be set back to an older position which can look odd in his own client.

The problem explained (I use 200ms as ping delay in this example, can be worse or better):

1) Player A hits button for stun effect
2) Command is delivered to server (200ms)
3) Server sends to Player B to immediately stop movement (200ms)
4) Player B sends current position and that he is standing still (200ms)
5) Server sends Player B's position to all who can see Player B (200ms)

So if we assume that Player A and B have 200ms ping delay to Uthgard this results in heavily delayed stop of the movement of player B from player A's view of about 800ms after stun. There is no window dragging involved.

Since player A did not receive the stop from ther server yet, player B will still run forward into last direction until 5).

The old window dragging techique tried to increase the ping delays seen above.

Rector wrote:Do the liveservers use a better mechanic?

I encourage you to run around in RvR for 5 minutes on live with a trial account.
What you would see is that the ghosting there is constant.
NPCs/players from clip ranges away ghosting at speed 6 and even when you're fighting, they rubberband just stopping to face.

Uthgards method for fixing this netcode error is far superior to any ive seen.
Bad computers and connections can be a messy cocktail.

Blue wrote:1) Player A hits button for stun effect
2) Command is delivered to server (200ms)
3) Server sends to Player B to immediately stop movement (200ms)
4) Player B sends current position and that he is standing still (200ms)
5) Server sends Player B's position to all who can see Player B (200ms)

First of all, i wouldn't reset the position of the stunned player. As mentioned, that may feel very unnatural to if you get stunned and ported afterwards.

Just a thought: Does the Server keep the position of player's in memory? If so, send position of Player B two times

1) Player A hits button for stun effect
2) Command is delivered to server (200ms)
3a) Server sends to Player B to immediately stop movement (200ms) and
3b) Server sends Player B's actual position, marked as stopped, to all who can see Player B (200ms)
4) Player B sends current position and that he is standing still (200ms)
5) Server sends Player B's position to all who can see Player B (200ms)

Steps marked as 3a and 3b will run nearly simultaneously (Server doesn't have to wait for laggy response). So Player A get's a 'guessed' position and an updated position at step 5.

Sure this will not completely solve the problem, it's just i minor improvement. There will be still some warping, but it might reduce effect.

Odd thing i could image, if Player A has horrible lags, he might position to standing target and then the target will get repositioned. But honestly, if you encouter bad lags on your own machine, everything is warping and porting around. So nothing new here

Without porting player B (the stunned one) in its own client this will result on another warp for all players seeing player B.

Player B will stop sooner (from others view), yes, but as soon as client of player B sends its position he will warp for all players again. Its not so easy to solve that without reseting player B's position in his client with what the server thinks is the stun position.

Maybe warping player B in its client is not that bad. Better than giving that player extra time to run around and change position when already stunned.

Blue wrote:Player B will stop sooner (from others view), yes, but as soon as client of player B sends its position he will warp for all players again. Its not so easy to solve that without reseting player B's position in his client with what the server thinks is the stun position.

Yes, as mentioned above, just an idea/thought to reduce the warping. But i admit, it's still a mess.

For warping Player B: If it's not that much work to to implement, then just give it a try? Would be interesting how the 'look and feel' is like.