16 replies to this topic

[Maker L106]

Okay so over the past week or so I've played a lot of MWO with my typical running partner. We have used a decent variety of mechs, mostly ones we already had and are familiar with but a few new additions etc: etc: So really SSDD.

The reason I'm bothering to even post about inconsistency is that about a week ago now died in the shadow cat with full frontal armor to what i thought was heavy guass fire. Could have been AC20 / whatever but big fat dakka is big fat dakka, anyway that's not the shock. After looking at my paperdoll readout for my death all my frontal armor, even the cockpit was fine. reason for death. engine destroyed, my rear CT however GONE.

I thought nothing about it initially, "okay paper doll glitched" / lag / whatever.

Complained about it to said friend but nothing more was really considered. Read somewhere on here where that'd happened to someone else and again wrote it off as odd but probably just the lag again.

Today however I ran into two very VERY odd circumstances. The first was on caustic valley vs a centurion in my viper, we began a fight becuase i was stupid and flanked HARD, centurion shuts down, "YES!" i alpha him in the spine with 4 Heavy mediums and MG's. thinking hes going down I immediately turn my attention to the cicada. but he starts back up, okay **** it, i relock him and to my surprise he still has rear armor...

after taking 40, while shutdown, to the buttocks, he had rear armor. not structure, REAR ARMOR, unless this was a colossal troll and all his armor was on his back (which i guess can happen) this struck me as strange.

But again, okay could be lag... it was me after all.

Next game up my bud in the linebacker splats two marauders from behind and wrecks them. walks up to a Catapult and does the same exact thing, squarely behind it, 5 SRM 6's to the back + ERSmalls... the back armor doesn't budge but his front armor goes from barely scratched to yellow / orange.

WTF!? He didn't catch it at the time because it was a rough fight, but clearly watching him as a spectator the paperdoll for the Catapult clearly took frontal damage with its back turned.

Too many times now to be coincidence that this sort of stuff is going on... but I'm not a programmer... I'm an IT guy... packet loss shouldn't cause this. Anyone out there shed some light on what we're seeing. Is it just me or has something been broken in this last patch that no one wants to talk about?

[AncientRaig]

Well, either you were playing on a server very far away from you (live in the US, got an Asian server, for example.), you were having really bad lag, or PGI's infamously iffy hitboxes were acting up again. It's been known to happen.

[Nemesis Duck]

Go into the training ground. Shoot the joints of the stationary mech. Move the reticle ever so slightly and shoot again until you discover the seam that damages some random component nowhere near to where you were shooting.

E.G. Shooting the elbow damages the leg on the opposite side you were shooting.

And that's just half the story...

[panzer1b]

Ive pretty much learned to live with the fact that on rare occasions damage can do some very odd things.

The most recent (and this was blatantly obvious) hitreg issue i came up with was a warhawk that fired a narc at my shadowcat, which didnt register as a hit (there was no allied mechs near me so it couldnt have been shot down by AMS or blocked by someone else's ECM). Thing is, i saw the bloody narc fly right into my cockpit, and the other guy (in warhawk) said he hit shadowcat headon with narc and it didnt do anything. I get the exact same thing with PPCs quite a bit actually, and even occasionally lasers where some or all of the incoming damage phases through my or another's mech. Its not that common, so im like "ok bad luck my round didnt do anything", but it is a problem that was never fully fixed and exists to this day.

That and there seems to be a few times where damage hitting my front bleeds through to teh rear, usually this amount is very low (its not gonna core me out or anything), but it does happen especially on the shadowcat and bushwhacker (those are the 2 mechs i consistently get my rear hit even when im 100% certain there was no mech behind me and no friendlies hit me either). Anyways, its not consistent or common enough to really take away from teh game, but it is something the devs need to be aware of.

[Hell in a Helmet]

See it all the time. Earlier today I came up behind a shutdown ShadowCat on Mining Collective In a Kodiak3. Full blast of 2 UAC10's, 2 UAC 5's, and 4 ERM Lasers in the rear center torso after taking a second to purposely aim there. Barely phased it. They used to say that PGI messed with armor values in the background to make games last longer explained it. Who knows?

Edited by LCPL 4, 28 August 2017 - 02:36 PM.

[Ghogiel]

Mechs that shut down while moving, especially JJing or falling (as PGI admits it's JSR cheats that) almost always desync even if only a little

[Asym]

Wow !

Not alone. I wrote a piece about experiences with light mechs and a lot of people told me to get good and find a new pair of glasses....

Same thing with several light mechs: stationary, time to aim and nothing happens to them....other than scaring the be-Jesus out of the light pilot since he/she didn't know I was there !!! In one case, we simply couldn't kill the light mech at all with two players simply blasting the crap out of him from the quartering rear.

Recently, shooting at assault mechs from quartering angles with Streaks in a circling engagement (4xStreak 4 & 1xStreak 2).... Just couldn't kill him and when I ran into that pilot a game or so later on my side, I asked him what he thought.... "I should have just died with the existing damage and you were hitting me and I just didn't die... Lucky me,"

[Ruar]

Hit reg most likely. MWO has some problems still with hit reg. Many will tell you it's better than previous or they do just fine but they are ignoring the times it is bad.

There is talk of a known issue where damage to the front ends up being applied to the rear. I wouldn't be surprised if it happens in reverse as well.

Mainly it's just a problem of old game code that is very limited making it difficult or impossible to truly fix.

[Jun Watarase]

Damage hitting the opposite is a very common thing due to bad hit reg that has been in the game since day one.

It is particularly obvious when you shoot a mech in the front with something like PPCs/Gauss and you can see their rear armor take damage.

It will probably be fixed around the time PGI gets around to delivering the FP experience founders gave them money for.

[Jobe01]

LCPL 4, on 28 August 2017 - 02:33 PM, said:

See it all the time. Earlier today I came up behind a shutdown ShadowCat on Mining Collective In a Kodiak3. Full blast of 2 UAC10's, 2 UAC 5's, and 4 ERM Lasers in the rear center torso after taking a second to purposely aim there. Barely phased it. They used to say that PGI messed with armor values in the background to make games last longer explained it. Who knows?

I guess that's the latest Kodiak-3 nerf😉

[Tarogato]

Nemesis Duck, on 28 August 2017 - 02:19 PM, said:

Go into the training ground. Shoot the joints of the stationary mech. Move the reticle ever so slightly and shoot again until you discover the seam that damages some random component nowhere near to where you were shooting.

E.G. Shooting the elbow damages the leg on the opposite side you were shooting.

And that's just half the story...

Ummmm, this doesn't happen. Or if it does, nobody's ever seen it before.

Got an example?

[TLBFestus]

What you guys are saying simply can't be true. This is an established eSport after all.......

[qS Sachiel]

Iv been wxperiencing connectivity issues recently so may be my end, however was playing faction play river city skirmish. Last mech was an afk whole game. Last drop was a Jenner iic. We agreed as a group to farm him, and I was closes to drop point. I fire on the mech from the side, deciding to take the left wing (slightly from behind but definitely hitting arm). I heard over ts 'guess we ain't farming' and saw the rear armour being the only item to fail. I confirmed aim on left arm and fired alpha strike. Rear armour cored out, all other locations pristine.

[Asym]

Last night, spectating a MDD being chased by a light with streaks..... Streak after streak hitting the MDD and no damage being reported on the paper-doll display. In this case, a set of streak 4's actually appeared to "go through" the MDD.......so splash effect, no damage.

A match later, spectating again, a Assualt with multiple Gauss rifles had a Gyr cornered against the buildings at 500 meters and a dual gauss attack "went through" the Gyr.......no damage, no splash effect, no paper-doll change, the next set killed it. ????

Talk about screwing up match and personal score outcomes.......

[Rick T Dangerous]

During matches I tend to just wonder about it and then forget about it, but in recent weeks (since latest patch, I believe) it's been quite often that I hit a mech, but no damage registers. Really, obvious hit on CT on <400m, but crosshair doesn't go red and paperman doesn't change color.

[Methanoid]

[Nemesis Duck]

Rick T Dangerous, on 30 August 2017 - 07:21 AM, said:

During matches I tend to just wonder about it and then forget about it, but in recent weeks (since latest patch, I believe) it's been quite often that I hit a mech, but no damage registers. Really, obvious hit on CT on <400m, but crosshair doesn't go red and paperman doesn't change color.

Sometimes there's a delay between the hit and the paperdoll getting updated, or so I've been told.