R.I.P Rubberbanding

[LASTofS]

It should be for both versions since rubberbanding is a pyspades issue.

[matpow2]

Just to clarify, rubberbanding is both a vanilla and pyspades issue. Rubberbanding happens when the client's position is off compared to the simulation on the server, and rubberbanding is an attempt to fix this desynchronization.
For 1.0, I've upped the network update rate a little and made the client progressively interpolate between its own simulation and the received world update if a desynchronization happens. No more sudden warps!

In casual terms, "dat lag be gone".

[bman7]

Just to clarify, rubberbanding is both a vanilla and pyspades issue. Rubberbanding happens when the client's position is off compared to the simulation on the server, and rubberbanding is an attempt to fix this desynchronization.
For 1.0, I've upped the network update rate a little and made the client progressively interpolate between its own simulation and the received world update if a desynchronization happens. No more sudden warps!

In casual terms, "dat lag be gone".

My question is: Why not 0.76?

[Fluttershy]

In casual terms, "dat lag be gone".

In techie terms, "010001100110000101101110011101000110000101110011011101000110100101100011"

[bman7]

In casual terms, "dat lag be gone".

In techie terms, "010001100110000101101110011101000110000101110011011101000110100101100011"

I believe that would be "01100100 01100001 01110100 00100000 01101100 01100001 01100111 00100000 01100010 01100101 00100000 01100111 01101111 01101110 01100101". In hex, "64 61 74 20 6c 61 67 20 62 65 20 67 6f 6e 65", and in base64, "ZGF0IGxhZyBiZSBnb25l".

[Fluttershy]

I was typing my response in techie terms

[Pvtrex]

I was wondering what rubberbanding was when mat tweeted. I always hated rubberbanding.

[HoboHob]

Just to clarify, rubberbanding is both a vanilla and pyspades issue. Rubberbanding happens when the client's position is off compared to the simulation on the server, and rubberbanding is an attempt to fix this desynchronization.
For 1.0, I've upped the network update rate a little and made the client progressively interpolate between its own simulation and the received world update if a desynchronization happens. No more sudden warps!

In casual terms, "dat lag be gone".

My question is: Why not 0.76?

Bcause tey nede teh monayz.

[MrMeow]

This is a sad day, Soon soldiers will get out of shape due to less effort in moving. :P

[LASTofS]

Just to clarify, rubberbanding is both a vanilla and pyspades issue. Rubberbanding happens when the client's position is off compared to the simulation on the server, and rubberbanding is an attempt to fix this desynchronization.
For 1.0, I've upped the network update rate a little and made the client progressively interpolate between its own simulation and the received world update if a desynchronization happens. No more sudden warps!

In casual terms, "dat lag be gone".

You may have been referring to my post, but I forgot the fact that know people still use vanilla. ;)

Just a couple of questions; is this fix going to be for both the paid and free versions of 1.0, and is there a difference between 1.0 and the supposed 0.76?

(I was replying to his question above)

[ei8htx]

You shouldn't have to pay for a bug fix for a game you paid for.

If you didn't pay for the game you shouldn't be complaining at all.

[Bozo]

I would really want to get rid of that.

[nalyd8991]

Aw man, rubberbanding saves my life every time I play hallway.

[nimdahk]

Aw man, rubberbanding saves my life every time I play hallway.

By preventing you from meeting anyone?

[Froelich131]

That's great!
Regarding the .76c and .75c... I didn't notice any difference in lag. Except for the fact that the .76 server was ran off a home connection. (Ben's, to be exact)