143 replies to this topic

[Pwnocchio]

I just started noticing this problem particularly when driving faster mechs in close proximity to other enemy mechs.

Didn't have this problem as of mid November. Have noticed it since.

[xengk]

Been encountering more rubber banding/teleporting recently.
Also the time between pressing "R" and a target is locked has become longer, forcing me to swap out my LRM builds for SRM.

My ping did not change much from previously.

[Caswallon]

Agree with the above. Lock on time even with BAP and appropriate modules is vastly increased. Several times I am sitting there mashing the "R" key with nothing happening. But I can laser the targets just fine with instant updates on their paper doll and or Kills...

[Mad Porthos]

As Pwnocchio, Xengk and Caswallon all mention above- it seems to have really gotten worse since mid November. I typically enjoy a ping between 20 and 59 - rarely ever seeing any rubber banding... however of late these matches come along where though my ping is still in that range, there is almost a complete desynchonisation. As recently as Sunday, thre was a game on caustic that started out smooth, thenbecame increasingly laggy, in the sense that shots fired into a target would seem to FORCE the target (from my POV) to teleport somewhere else than where I fired... causing misses, but with similar results from enemies... thier attempts to do massive alphas would just rubber band me another 200 meters forward, or correct my position from running across THE CALDERA, poof ! to being instantly stuck in pipes and water tank in the factory that I had previously fled 30 seconds earlier.

All this while my ping remains in the 20-60 range. Some others in game at same time were posting crazy high pings in bursts, reading 12 steady for a while, then suddenlt showing something like 1800 or 3000 yet they did not disconnect automatically. As the match progressed, it proved no one could really hit anything at all, with the exception of a few streak kills. Soon one after another we all said sorry,this is too much... cant hit anything, cant be hit even standing still... then disconnected.

That all started with and was the worst the rubberbanding got. Many other matches, its just rubber banding and the inability to target, even with targets under the reticule, hitting 'R' can mean a five count before you get the little beep beep and that person is selected, starting the targeting process of aquiring an Lrm or streak lock, that can then take from five to twenty seconds to lock tone and firing - assuming the game doesn't then decide that you HAVE been holding the 'R' button down and procede to cycle through other targets breaking the lock acquisition.

Now when this occurs, its definitely a game/server issue. Its not ecm nearby blocking the locks on target or aimer by being intermittently in range. I know this too from being the final armed survivor in a game who had to go kill an afk catapult, when this odd lag/rubberbanding hit. The disarmed deaths knell and jager with me were trying to ram the catapult to death and so I came with 2xlrm15 and 4xssrm2. At 200m with artemis, bap... it took 20 seconds to get lock for both streaks and LRM. Firing in this state of lag/rubberbanding was diffult though because at 200 meters, the lock would break immediately on firing and even the position of the catapult target would oddly adjust or rubberband as salvos arced toward him and would miss hitting behind or in front. Several times the paper doll flashedto show damage from ssrm and lrm hits and an area that flashed was undamaged, then later areas that looked orange internallywould flash, and seem unchanged or would update to yellow. obviously glitched or faulty.

I thought in this case, perhaps it is a disconnect and that is why the incorrect damage updating - but at the end as I started just direct fire shooting LRMs at the crosshair reticule location/range the warping and rubberbanding of the target Cat ceased and apparently the afk pilot began to pilot, killing the death knell before my LRM volley took him down.

This experience I am relating made me wonder just what I saw... an instance of desychonization where that catapult was playing the game at incredibly high ping in his own seperate world/desynced version of events , yet wasnt disconnected... or if only just then he came back to his laggy game and began playing.

I would point out, in most cases where I've seen this extreme lag and rubberbanding, no one really had an advantage... people might be killed because the rubberbanded into shots and locations they would not normally have been, but it was not like I have ever seen rhyme or reason to when the lag strikes. certainly not any sign that someone is causing it with a hack, or deliberately timed flood of bandwidth filling packets or other speculation I have heard from the tin foil hat brigade when these games go so outrageously wonky.

Edited by Mad Porthos, 10 December 2013 - 04:40 PM.

[RamsoPanzer]

Yes , for me increased since november

[itshouldbegood]

The latests patches (1 or 2) make MWO unplayeble for me, cos of rubberbanding. The last issues what i want to try to solve this problems:
1. reinstall the game - done w/o result (full remove and full install) 14.12.2013
2. reinstall OS + Game.
If it's not helps - i think i'm going to quit for a few months.

Edited by itshouldbegood, 14 December 2013 - 03:05 PM.

[Sowaka]

This problem has become excessive since mid-November for me, nearly to a point where the game is unplayable. Pretty much every action is delayed, zooming in and out can take 2-3 seconds and the same goes for night-vision and locking onto enemy mechs. Sometimes when I turn I'll warp to a location where I would have been if I hadn't turned at all. Sometimes random damage will appear on my mech without even seeing or hearing anything hit me. I've noticed my ping jumping up to 1000+ plus for a second or two on several occassions, but this was never a problem before and hasn't been a problem with other games so far.

[BobBob777]

Getting very serious rubber banding. Happens regularly every game. Basically makes light mechs unplayable. Never had it until the last patch... I love the new features but the new rubber banding feature is pretty much going to kill the game for me.

[BobBob777]

BobBob777, on 19 December 2013 - 01:16 PM, said:

Getting very serious rubber banding. Happens regularly every game. Basically makes light mechs unplayable. Never had it until the last patch... I love the new features but the new rubber banding feature is pretty much going to kill the game for me.

I forgot to add I've never had a problem before - only since the last patch. FPS usually around 50-60. Occasionally drops to the 40s. Even when banding I've only ever seen it go red once generally still in the 50+ range! I'm still running everything extactly the same PC wise. Have logged a support request.

[maxmarechal]

same here
lost some fps since last patch so adjusted my settings for a 35-50 fps in fight and getting really disturbing rubberbanding and teleport back to previous position or direction...even got clock going to time off and no end of game if i don't quit...
config is same before/after patch
w7 64
core 2 quad 2.5
gtx650
4g ram
adsl is fine
ping normaly 120-130 recently 150

[SixDeltaEcho]

I'm getting this every match, heavy rubber banding when trying to move, I only tried playing my Victor DS and gave up after it was unplayable.

Also my ping has skyrocketd from anywhere between 600-800 for no reason at all when it used to be 200, there is nothing wrong with my connection, not capped, nor problems with the lines, just happened with this patch

[Jonathan Paine]

After the last couple of patches, my ping has increased from mid 80's to mid 130's. On occasion the game slow down for a second or so. Locking on randomly takes longer, zooming in sometimes hangs for half a second. Hit registration is pretty random. Changing QOS settings to give all mwo traffic highest priority made the game more playable, but ping remains bad.

[FallguySoldier]

Honestly, I've only just noticed how frequent the rubber-banding issue is when I recently started playing on my light mechs, i.e. on my Locusts and Jenners. That being said, this is a major issue that definitely needs to be addressed and fixed.

[TriOptimum]

Unplayable lag and rubberbanding on an otherwise stable connection here, no problems with MWO in the past.

Updating router firmware (Netgear 3400), opening ports TCP 45461, TCP 45464, UDP 21000 to 30000, and turning off DoS filtering seem to have fixed this problem for me. Not sure which fixed my issue; I will close the ports and turn DoS filtering back on, and try again next patch. Hopefully the old router settings will work once they fix this issue.

Edited by TriOptimum, 27 December 2013 - 11:00 AM.

[Astrocanis]

In the last week or so, my ping has gone from 58 (reliably) to 170-200 consistently. This is the only game / program I'm experiencing this with. it's making playing very very difficult.

As I said, this has happened in the last week or so.

[AdultPuppetShow]

I never really had a problem with rubberbanding before, but after the January 7th, 2014 patch I can't even play. Targets that I aim at end up being 200 meters away from where I thought they were after I've pulled the trigger, and sometimes I'll take damage or get killed without ever even seeing the enemy mech that shot me until AFTER they're straddling my smoking chassis. Shortly before this patch I was having some of the best fun I've ever had in this game. Its a damn shame that I'm going to have to take another couple month long hiatus because of this.

[chewstacka]

As a european(Stockholm) with decent connection(100/10 ,21 ms ping to www.google.com) 16, playing a light mech with a 150 or higher speed is unplayable due to rubber banding, warping and just halts. Even when the US is sleeping its impossible, with 120 ping..

Funny enough, lower the speed to 100 or so its no problem at all cept the occasional jumpjet-warp that teleports you way up then way down sometimes.

Edited by chewstacka, 11 January 2014 - 04:54 AM.

[Batch1972]

Hi,

Australian. It's 9:26pm Sydney time no idea what it is in Canada.

I've started to experience massive rubber banding. Game is now unplayable. Nothing has changed with my PC / internet. I started playing around 7pm is. I've restarted the client repeatedly but no effect. Just been kicked out of game.

Has anything happened? Is anyone else having this issue?

[Lionsroar]

Since the last 2 patches the rubber banding and teleporting have become constant and have made the game nearly unplayable. Mech's treadmilling, walking in place then leaping forward hundreds of meters, and the long lag to lock up on targets.

No changes were made to my computer, I have used this same computer to play MWO since August and before this might see rubberbanding 1 out of 50 games. Suddenly it is every game. My ping has remained pretty constant 30-50. My damage scores have dropped like a rock, previously I was averaging 300-450 a game with highs in the 700-800 area. Now I'm averaging 100-200 and highs around 350. This is making it unplayable. It is extremely frustrating, and is rapidly driving us away.

I have 2 accounts, one for me and one for my son. I have spent a LOT of money on MWO, 2 overlord packages with reinforcements, tons of MC to buy hero mech's etc. I played this game back when it was tabletop and the early computer versions, and am a loyal fan. However, you are about to lose a loyal fan and good customer who spends a lot of time and money on this game. And to make it even more annoying, while this is happening I am still using the premium time on the 2 accounts.

Please quickly address this issue. Beyond all of the other complaints that the fan base has, UI2, CW, Clan tech, etc, all of that affects the future state of the game and how it develops. This issue however will drive away your current customers and fans.

[Rose Scented Love Puff]

Experiencing some bad rubberbanding in Frozen city day map and Caustic Valley map when piloting my Cicada. Occasionally in Terra Therma too.