Jump to content

Lag Shield After Patch


37 replies to this topic

Poll: Lag Shield (132 member(s) have cast votes)

Has the lag shield changed after the 1/8 patch?

  1. It has gotten worse. (37 votes [28.03%])

    Percentage of vote: 28.03%

  2. It has gotten better. (16 votes [12.12%])

    Percentage of vote: 12.12%

  3. It is the about same. (79 votes [59.85%])

    Percentage of vote: 59.85%

Vote Guests cannot vote

#1 Mongoose Trueborn

    Member

  • PipPipPipPipPipPipPip
  • Veteran Founder
  • Veteran Founder
  • 742 posts

Posted 09 January 2013 - 02:01 PM

Had another poll that was moved and later deleted for some unexplained reason. I simply would like to know if others are having the same issue as me.

The patch notes talk about lag shield improvements but it seems to be much worse for me after the patch and my ping is very good at 30-40.

What are you all seeing after this patch?

#2 Roadkill

    Member

  • PipPipPipPipPipPipPipPipPip
  • 3,610 posts

Posted 09 January 2013 - 02:03 PM

Lag shield is the same for me or possibly a little bit worse. Rubberbanding seems to be better, though.

#3 Arjohan

    Member

  • PipPipPip
  • Cadet
  • Cadet
  • 94 posts

Posted 09 January 2013 - 02:15 PM

For me worse, here an example of what's going on with me:
One Atlas (with a 300 engine, STD or XL it doesn't matter) is in my left, he is moving to my right and he is right ahead of me. Before the patch, if I fired a laser or anything in it it would register the hit. Now, if I do the same, sometimes it says that I hit (cross hair go red) but the damage doesn't register right and sometimes I need to shoot a little more ahead of him.

It's the same for any class, but even worse. I noticed this when I was fighting a Jenner, I had a K2 with 2x ML, 2x MPL and 2xMG with STD 315. I was shooting as the same way as I did before the patch and the crosshair went red, but the little icon of the mech didn't changed much. Even fully hitting it, it didn't registered right. After I died for this Jenner, a Commando with 3x SSRM2, 1x TAG and ECM defeated him easily. I don't remember the ping of the Commando one but the Jenner was 54.

Before this last patch, I had no issues about it, just the normal lagshield.

I have 10Mbps internet and I'm in Brazil, South America. Is anyone suffering from the same thing?!

EDIT: Additional information: I had around ~150ms and still have ~150ms, but I notice that it's different, lack of synch. Other thing that started to happen is the 'mech teleporting as depending how fast/how low the ping is. I REALLY hate my country.

Edited by Ryon Kerensky, 09 January 2013 - 02:43 PM.


#4 Aurien Titus

    Member

  • PipPipPipPipPipPip
  • Bridesmaid
  • Bridesmaid
  • 315 posts

Posted 09 January 2013 - 02:17 PM

View PostMongoose Trueborn, on 09 January 2013 - 02:01 PM, said:

The patch notes talk about lag shield improvements


No it doesn't

Edited by Aurien Titus, 09 January 2013 - 02:18 PM.


#5 jakucha

    Member

  • PipPipPipPipPipPipPipPipPip
  • Knight Errant
  • 2,413 posts

Posted 09 January 2013 - 02:18 PM

I'm doing damage to lights. Whether or not it's full damage I can't tell.

#6 Norris J Packard

    Member

  • PipPipPipPipPipPipPipPip
  • 1,972 posts

Posted 09 January 2013 - 02:18 PM

They made no alterations to the netcode this patch.

What you're noticing is something called the placebo effect.

#7 jubbly

    Member

  • PipPipPipPipPip
  • 130 posts
  • LocationMaui, Hawaii

Posted 09 January 2013 - 02:24 PM

View PostMongoose Trueborn, on 09 January 2013 - 02:01 PM, said:


The patch notes talk about lag shield improvements but it seems to be much worse for me after the patch and my ping is very good at 30-40.



do you have a link for that? I don't see anything about netcode improvments in the notes. They put in a fix for some rubberbanding issues. Is that what you are talking about?

#8 siLve00

    Member

  • PipPipPipPipPipPipPip
  • 667 posts

Posted 09 January 2013 - 02:25 PM

lagshield is for me the same..

But i dont see rubberbanding... A guy with a ping of 350 ( you can guess the mech he was using trololo ) and no rubberbanding at all.

so still alot to do ^^



View Postjubbly, on 09 January 2013 - 02:24 PM, said:


do you have a link for that? I don't see anything about netcode improvments in the notes. They put in a fix for some rubberbanding issues. Is that what you are talking about?


it was in the patchnotes for 20 minutes... then they deleted it because they didnt take it into the patch.
Some1 from the crew did state they did something with the moving ( rubberbanding at high pings )

Edited by siLve00, 09 January 2013 - 02:27 PM.


#9 Nauht

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 2,143 posts

Posted 09 January 2013 - 02:28 PM

There was nothing done to the netcode this patch. Read the patch notes properly next time.

#10 bug3at3r

    Member

  • PipPipPipPipPipPip
  • 275 posts

Posted 09 January 2013 - 02:35 PM

At first I thought it was better because I was successfully nailing lights with AC's/PPC's....then a fast CN9D showed up and crapped on my parade.

No difference from what I can tell, all depends on the persons ping, like it did before.

Edited by bug3at3r, 09 January 2013 - 02:35 PM.


#11 Xyroc

    Member

  • PipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 855 posts
  • LocationFighting the Clan Invasion

Posted 09 January 2013 - 02:37 PM

First thing I do is look at the person im shooting and check their ping if its up 200+ I dont expect to hit them much if in a light unless I got some lock on weps

#12 DeadlyNerd

    Member

  • PipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 1,452 posts

Posted 09 January 2013 - 02:37 PM

Well at least now a point blank shot of SRMs into a standing assault will register, as opposed to some situations before the patch.
The usual lagshield is still there.

#13 Ghogiel

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • CS 2021 Gold Champ
  • CS 2021 Gold Champ
  • 6,852 posts

Posted 09 January 2013 - 02:48 PM

View PostAurien Titus, on 09 January 2013 - 02:17 PM, said:


No it doesn't

I am pretty sure they edited the patch notes...

It did say something to the effect of> lag shield is an acknowledged problem yaddayadda, we are continuing work on it. Improvements > now lag shield issues should only be affected by your own ping rather than both yours and the other player. ( not sure what they meant by that though)

#14 Aurien Titus

    Member

  • PipPipPipPipPipPip
  • Bridesmaid
  • Bridesmaid
  • 315 posts

Posted 09 January 2013 - 02:52 PM

View PostGhogiel, on 09 January 2013 - 02:48 PM, said:

I am pretty sure they edited the patch notes...

It did say something to the effect of> lag shield is an acknowledged problem yaddayadda, we are continuing work on it. Improvements > now lag shield issues should only be affected by your own ping rather than both yours and the other player. ( not sure what they meant by that though)


Because it listed things that they're still working on and weren't in the patch. So no lag shield changes this patch.

#15 Dirkdaring

    Member

  • PipPipPipPipPipPipPip
  • Survivor
  • 685 posts
  • LocationTwycross

Posted 09 January 2013 - 02:53 PM

Played for a few hours last night, didn't see anything different. Had no problem hitting lights with 2x Gauss.

#16 Mongoose Trueborn

    Member

  • PipPipPipPipPipPipPip
  • Veteran Founder
  • Veteran Founder
  • 742 posts

Posted 09 January 2013 - 04:55 PM

View PostAurien Titus, on 09 January 2013 - 02:17 PM, said:


No it doesn't



I clearly saw, and was not the only one, something in the patch notes in regards to fixing lag shield. It said something about no longer taking into account both parties latency and that only your ping would affect how much lag shield there was.

Now the patch notes are much shorter and that information is nowhere to be found. Does anyone else know what I'm talking about?

View PostsiLve00, on 09 January 2013 - 02:25 PM, said:


it was in the patchnotes for 20 minutes... then they deleted it because they didnt take it into the patch.
Some1 from the crew did state they did something with the moving ( rubberbanding at high pings )



That clears it up. Thanks

#17 Rifter

    Member

  • PipPipPipPipPipPipPipPipPip
  • 2,230 posts

Posted 09 January 2013 - 05:19 PM

It 100% DID say something about fixing the lagshield which has since been edited out of the patchnotes. I saw it with my own eyes, it was in for 20-30 min till edited out.

I agree with OP lagshield seems worse, it seems like movement and rubber banding seems better less clipping around when changing direction in a fast mech but the lagshield as far as registering hits seems as bad or worse than ever.

Edited by Rifter, 09 January 2013 - 05:19 PM.


#18 Aurien Titus

    Member

  • PipPipPipPipPipPip
  • Bridesmaid
  • Bridesmaid
  • 315 posts

Posted 09 January 2013 - 06:49 PM

View PostRifter, on 09 January 2013 - 05:19 PM, said:

It 100% DID say something about fixing the lagshield which has since been edited out of the patchnotes. I saw it with my own eyes, it was in for 20-30 min till edited out.

And then PGI said oops, that stuff didn't come in this patch, we're still working on it internally and changed the patch notes. Is this really a ******* hard concept for people to grasp? <snip>

Edited by Prosperity Park, 09 January 2013 - 09:21 PM.
edited per CoC...


#19 Stone Wall

    Member

  • PipPipPipPipPipPipPipPip
  • Veteran Founder
  • Veteran Founder
  • 1,863 posts
  • LocationSouth Carolina, USA

Posted 09 January 2013 - 07:00 PM

I have no problem hitting Lights, so I voted No Change.

#20 Das Wudone

    Member

  • PipPipPipPipPipPip
  • 204 posts

Posted 09 January 2013 - 07:18 PM

i think u should add an additional choice there for "sometimes really good, sometimes very bad". there are matches where i can easily hit fast moving stuff cos they dont warp around but there are also matches where it just goes warpy and i cant do anything to them.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users