Doesn't work on heavies? I decided to try playing today, hoping that the network issues I was encountering yesterday weren't too bad today...
And then, first game, with my K2, newly refitted with dual-gauss (after three months of not bothering with that loadout) and a downsized XL255, walking at 70km/h... teleports everywhere. Rubberbanding ridiculously. Turn ten degrees, get rotated back eight. Press R to retarget, get an update three seconds later. Press fire key, turn to the left, see the gauss fire to my right four seconds later. Fire lasers, see them blink on and off. ...I thought I wasn't using pulse lasers?
...
Well, nevermind that. I'll try the Raven.
...And that 145km/h Raven doesn't have rubberbanding! Lagshield magic!...
1
So Apparently The Lagshield...
Started by Dukarriope, Jan 15 2013 02:06 AM
5 replies to this topic
#1
Posted 15 January 2013 - 02:06 AM
#2
Posted 15 January 2013 - 02:31 AM
rubberbanding on yourself isn't down to what mech you drive - the rubberbanding and lag shield issues are what you see on other people, faster mechs get more lagshield because they rubberband and skip ahead more than slower mechs
if you are getting rubberbanding on yourself then it's a dodgy connection or 4FPS bug or such and not directly related to the lagshield issue
if you are getting rubberbanding on yourself then it's a dodgy connection or 4FPS bug or such and not directly related to the lagshield issue
#3
Posted 15 January 2013 - 02:45 AM
The thing that's funny here is that my slower mech had self-rubberbanding. The game immediately after, my fast light mech had none of it.
#4
Posted 15 January 2013 - 02:46 AM
i saw bigger mechs lagshileding but only temporary..so i put it on some hiccup in the internet connection/server connection
#5
Posted 15 January 2013 - 03:02 AM
Dukarriope, on 15 January 2013 - 02:45 AM, said:
The thing that's funny here is that my slower mech had self-rubberbanding. The game immediately after, my fast light mech had none of it.
What do you mean by self-rubberbanding? Did you always get set back to a previous location you had 10s ago?
Sometimes this happens to me as well when my ping goes up through the roof (450 - 700+) and settles again (down to 150 - 170) during the match.
Due to latency, sometimes packets get dropped or invalidated because you are out of sync with the server. Then the server will give you outdated positional information for your position and because the server is authoritative over the client data, your mech gets set back to a previous position.
#6
Posted 15 January 2013 - 04:07 AM
i have to lead the shot by a whole mech shooting at a cataphract. it has occurred more on lights but since the last patch iv been encountering it on all classes.
this doesnt happen every match.
this doesnt happen every match.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users