31 replies to this topic

[Metalice99]

Seriously, I'm surprised this isn't on the known issues list. Its stupidly noticeable, every single match. Take some damage to front armour, decide to **** by using rear armour/arms as protection, but damage just completely ignores rear armour, even though fire obviously cannot hit anywhere near the front torso.
I can deal with crappy netcode. I can deal with ECM working as intended. However I cant deal with a blatantly obvious bug that removes any skill in maneuvering out of a tight situation.

Rant over.

Otherwise, I'm loving the other changes in the patch. It seems every patch lately, on the whole, is a step forward. QQ, invincilights. QQ, sync dropping pug stompers. Tourney organisers; I'm sure the devs won't leave you in the dark for long...

Metalice99, on 25 February 2013 - 12:09 PM, said:

Take some damage to front armour, decide to **** by using rear armour/arms as protection

Read "Decide to artfully withdraw from hostile situation"

[Deathlike]

There are some issues with damage transfer...

During the tourney, my cic took a direct hit on the front, only to immediately die from taking damage on the "back CT armor" instead.

With that said, the code for lag/hit detection and transfer works better for hitscan weapons (lasers), than it does for projectiles and weapons like that (PPCs).

[ohtochooseaname]

I've been in a Raven, and taken a double gauss to the face with full armor. It went straight to the back and turned my ct orange without damaging my front armor.

[sycocys]

My guess is they want you to load up your back armor and run into every battle face first guns blazing.

I'm also under the impression they somehow believe netcode rewind will fix this.

[arnham]

just had this happen to me in river city, in tunnel. Was piloting my Wang, followed team into tunnel, gausskitty inside. Gausskitty shoots me in what appears to be CT - see the gauss plow straight into my face, i'm facing directly at him (nailed him in the cockpit with my AC20, <3 catapults) Take all damage on rear armor, coring me there instantly and destroying one of my medium lasers. Asked team if anyone saw a teammate shoot me in the back just in case, but no - i was kinda up on the right higher part of tunnel, and nobody was directly behind me at all.

I've seen this a few other times too. At least for me it seems to usually be gauss doing it, though occasionally autocannons as well.

Don't think i've seen lasers do that ever that I can recall. It's hard to tell with SRMs, but I think I've seen 1 or 2 out of a 6 pack register on front armor when i'm shooting someone in the back (in a 1v1 situation, no way someone else shot him at the same time - undamaged mech, sneak up and unload directly on rear armor from 30m - back will turn orange/red/cored but front armor will often go yellow from a hit or 2 too. This is definitely not an ammo explosion or anything as my SRM mechs run with 2-3 SRM6s at most, vs some mechs this won't core their rear armor, so rear armor goes orange/red, front goes yellow.

Edited by arnham, 25 February 2013 - 06:32 PM.

[Deathlike]

I've seen damage to the back register as damage to the head. At times, this bug boggles my mind.

[Frank the Tank]

sycocys, on 25 February 2013 - 02:31 PM, said:

My guess is they want you to load up your back armor and run into every battle face first guns blazing.

I'm also under the impression they somehow believe netcode rewind will fix this.

This is likely an issue that was hidden by the blatant net code problems. Now that the net code is more stable we are noticing another problem that was likely always there.

I've seen this bug too. Seems to be more apparent with ACs, but I suspect all projectile ACs, PPCs, and missiles are effected.

[Cest7]

Shot a raven in the face with an ERPPC... back RT armour dissapeared and RT went yellow

[GrimmwolfGB]

I guess this might be a bug were you lag a bit in front of the projectile and suddenly your back is closest to the bullet. (Like when you suicide because you lag into your own SRM...)

[Metalice99]

Servers are down for maintainance, hopefully they will have addressed this issue. Hopefully.

[sycocys]

Bryan stated net rewind won't be in until the 5th at the soonest. I honestly don't think it's going to change much of anything myself other than adding mysterious headshots to higher ping players.

[jay35]

Net rewind? You mean where it rewinds the game and determines what you saw happen, didn't actually happen? because that annoying, frustrating mechanic is already in the game. It happens most frequently when you're colliding with another mech. You can actually get into a near unbreakable loop with an enemy mech if you're between said mech and another obstacle like a wall or a building, where you keep warping back and forth 1-2 seconds in time. It's extremely annoying and probably could cause epilleptic siezures if you're using heat vision at the time. It already does this and even gets so bad as to set things back 5-10 seconds in time once in a while which completely changes what happened to you. Sometimes you'll even be dead when the net code catches up!

[Cest7]

I've noticed front to back but not so much back to front.

[Ronin13m]

Yeah saw this last night after the patch. Got hit full on in the face and the damage transfered to the back. Also saw a flight of LRMS hit a jumping sider full on front chest but his back armor took the damage instead.

[Vedic]

I'm glad I'm not the only one feeling this. The last few nights I've been having huge problems with my Cataphract 4X feeling like it's made of paper. The worst offenders to me seem to be LRMs, followed by autocannons (maybe). A few LRM volleys kills me in seconds, and it makes zero sense. These aren't small LRM swarms, but I'm moving and taking them across the whole mech - I shouldn't have more than light orange armor in a single section by the time I die. I wonder if LRMs are noticeable for me since they do a LOT of damage over a wide area, except now that's all being routed straight into my torso.

I'm running an XL in this build, and that seems to be where it shows the most because your ST in a 'phract has 30hp once they get through the rear armor with this bug. In one match I lasted maybe 10 seconds against a pair of Centurions, at full health.

[GetinmyBellah]

I've always had issues with streaks affecting the rear or front CT depending on which way I'm facing the opponent. I'll be sure to keep my eyes open for more because this is complete BS ~

[JuiceKeeper]

i noticed this yesterday. I was stripped off armor on CT with completly red internals and jenner was chasing me and shooting with lasers to back (no damaged armor there) and damage was transfering straight on frontal torso on internal parts.

[Monky]

It seems to happen a lot on the trebuchet 5J at least. laser to the mid-level front torso? back armor. Damage to the back of the head? looks like you just took one to the CT!

[sycocys]

jay35, on 26 February 2013 - 03:57 PM, said:

Net rewind? You mean where it rewinds the game and determines what you saw happen, didn't actually happen? because that annoying, frustrating mechanic is already in the game. It happens most frequently when you're colliding with another mech. You can actually get into a near unbreakable loop with an enemy mech if you're between said mech and another obstacle like a wall or a building, where you keep warping back and forth 1-2 seconds in time. It's extremely annoying and probably could cause epilleptic siezures if you're using heat vision at the time. It already does this and even gets so bad as to set things back 5-10 seconds in time once in a while which completely changes what happened to you. Sometimes you'll even be dead when the net code catches up!

From their explanation the net-rewind code will do something along the lines of keeping a server side log per match of mech locations that the weapons code can poll to determine exactly where a mech was at the time it received a fire command.

My guess is that this will hurt high ping players more than help them. And it will incredibly help low ping players because they will better be able to predict shot locations on faster/high ping targets. Will as I said probably lead to mystery head shots from the perspective of higher ping players.

[Hobietime]

It seems to happen the worst with 'phract CTs. I only target side torsos on that mech since it seems that you tend to damage the other side of the mech at the most inopertune moments.

Looks like that armour is...


(•_•)
( •_•)>⌐■-■
(⌐■_■)
...'phracted up.

YEEAAAAAAAH!

Edited by Hobietime, 28 February 2013 - 09:16 AM.