10 replies to this topic

[HighSpeedSentry]

Please someone confirm this for me. ALL of my mechs seem to take fewer shots to damage/destroy after the patch on the 23rd. This leads me to believe the netcode was not touched to improve lagshielding but rather the armor itself was made less effective making lights easier to kill.

[JSparrowist]

Nope.avi

The games engine was tweaked and reduced the "lag shield" effect in the process. Armor values weren't touched.

[Livewyr]

Umm.. actually damage is just actually happening now...

[Apoc1138]

and so the the QQ begins...

[GoManGo]

I think all the mechs are soft. There like paper dolls you would think a 25-100 ton mech covered in steel armor, ETC would be tough take 20-40 shots to kill. But no some lame brain designer said ow no lets make them die in 1-3 shots like little pansy mechs. The other thing I had to understand was I was not fighting my same class type of mechs which sucks aaasss. I mean if im in a trial mech I just want to fight other trial mechs .If im in a custom mech but not on comms or in a group I just want to fight other FFA players not grouped up.And last if im in a group comms or not I just want to play others in groups on comms or not .My gosh is this such a hard thing to set up for matchmaking?I think they could do a much better job of making this a better mech simulation just with these few changes.

[Comassion]

VvSPECTERvV, on 25 January 2013 - 08:31 AM, said:

Please someone confirm this for me. ALL of my mechs seem to take fewer shots to damage/destroy after the patch on the 23rd. This leads me to believe the netcode was not touched to improve lagshielding but rather the armor itself was made less effective making lights easier to kill.

So do some serious testing. Stand still and let a friend shoot you repeatedly with a weapon with a known damage value (The medium laser, for instance, does 5 damage), then compare the damage done to the armor points you have in the mechlab + internal structure points of the 'mech (not listed in lab, probably can find it on the forums somewhere). Armor points listed in the 'mechlab have not changed.

Then after you've done some beta testing and found out that you're dying too few shots and have the evidence to show it, please come back and show us your results.


The Lagshield doesn't just affect lights - it affected people's ability to target specific sections of your 'mech even if you were a slow mover. It may indeed be the netcode, so go get some results in instead of reporting how it 'feels'.

Edited by Comassion, 25 January 2013 - 08:40 AM.

[TexAce]

VvSPECTERvV, on 25 January 2013 - 08:31 AM, said:

Please someone confirm this for me. ALL of my mechs seem to take fewer shots to damage/destroy after the patch on the 23rd. This leads me to believe the netcode was not touched to improve lagshielding but rather the armor itself was made less effective making lights easier to kill.

Nope, people just are able to hit more often now, since they fixed the netcode a bit. Yes, a bit. It will get even better, and then everybody will do damage while aiming AT a mech, not in front of it.

Nobody says that they will keep it that way, if everybody dies much faster, they could also buff the armor of all mechs to make them durable.

Edited by TexAss, 25 January 2013 - 08:42 AM.

[DrVulcan]

TexAss, on 25 January 2013 - 08:41 AM, said:

Nope, people just are able to hit more often now, since they fixed the netcode a bit. Yes, a bit. It will get even better, and then everybody will do damage while aiming AT a mech, not in front of it.

Nobody says that they will keep it that way, if everybody dies much faster, they could also buff the armor of all mechs to make them durable.

qft

[RabbidFerret]

Now you actually have to rely on skill and not your lag shield. Tragedy.

Edited by RabbidFerret, 25 January 2013 - 09:59 AM.

[Joseph Mallan]

Apoc1138, on 25 January 2013 - 08:34 AM, said:

and so the the QQ begins...

yeah it'll take a few days to get used to the amount of damage I can sustain before going pop!

[Max Immelmann]

ooops, wrong thread