21 replies to this topic

[HermesFenix]

Hello,

This is my first post, so I don´t know if there is a better forum to post this or if it has been said earlier.

I played a match some minutes ago piloting an Adder, at the begining of the match with the armor almost new (a quick hit form LL and some SL), I walk in front of a Jaggermech at hardly 50m. Then I die. The report says TC destruction, damaged by AC20, and the picture shows my fornt TC armor new, and no back TC armor. But the guy who killed me was in front of me.

Is there anything weird with the hit locations on the Adder? How can you be hit in your back from the front?

See you in the fields!

[Lostdragon]

MWO has some issues with hit detection and sometimes you see things like this happen. Now, of course, you could also be mistaken and there could have been another guy with an AC20 behind you that you didn't notice, but I've seen plenty of instances where damage gets registered incorrectly or not at all.

[TyphonCh]

Fate 6, on 29 August 2015 - 03:36 PM, said:

If you're with RePlayBoy101 you know you're in Elo Hell

I believe this bug has been around for awhile... Taking substantial damage from dual ac20's (and other ballistics) will sometimes register hits to your rear CT. It's happened to me but I've never died from it. File a bug report. I will the next time it happens... Hopefully it will get fixed

Edited by Team Chevy86, 29 August 2015 - 06:12 PM.

[Vlad Ward]

Adders are very short. Jagermechs have extremely high mounted ballistic weapons. At close range, it's very possible for a Jager to shoot down on you and have the shell hit a part of the "roof" of the Mech that could be considered part of the Rear torso.

[Light-Speed]

One of the most frustrating bugs in the world when you are in a light.

Fortunately it doesn't occur often.

[Mechwarrior Buddah]

sometimes its your mech's profile, sometimes its stuff that hangs off and sometimes its a bug thats been in the game since CB

[SolCrusher]

it happens and on some mechs you can aim at points on the shoulder that are back armor.

[Kiiyor]

I think it has something to do with the hitboxes on top of the mech. On some, there appear to be areas on top you can strike to hit rear armour.

[Narcissistic Martyr]

Part of your top counts as rear armor on the adder, jenner and a bunch of other mechs.

[aniviron]

You also have to keep in mind that because the netcode gives priority to the shooter, if you're twisting around and he shoots you in the back but your computer doesn't play the hit effect until you twist to the front on your screen, it still counts as a back hit.

[Erkki]

It happens time to time with the Griffin too. When you're twisting torso a bit or the incoming fire comes from even a bit higher than its own level or the torso is looking even a bit downwards from horizontal, its possible for the incoming fire to hit the 2 side rear torsi locations. Not a problem if its just lasers as but very annoying if PPC, dual AC/5, AC/10 or AC/20 as the armor is then no more or is breached and one suffers damage to the internals.

[zagibu]

This happens fairly frequently with AC/20 hits. Shoot someone in the back, their front also takes a little damage, and vice versa.

[Sabazial]

Yeah i get this happening to me regularly too, although it happens to me when piloting heavies mainly. It's one of those bugs that's been hanging around forever.

[Cyborne Elemental]

Yep, happens alot it seems.

Its an old bug, something to do with the low tickrate the server runs at, and HSR not compensating for frame by frame object collisions that PPC/SRM/LRM/Gauss/AC's use.

What is happening I think, is that because of the low tickrate, frame by frame positions can be off by quite a bit.

Meaning that according to your client you see a hit, but the choppy tickrate on the server is calculating positions not smoothly.

Server side it tracks objects on a frame by frame basis and there are pauses between position updates, so these projectiles could have quite literally passed through your target between ticks, then HSR rechecks your client hit, the projectile was behind your target and reports that client hit behind because its not taking motion into account for the projectile when calculating the hit.

Not sure if this is 100% true because I don't know the code, but it seems the most logical explanation.

Something like this.

Edited by Mister D, 30 August 2015 - 06:35 AM.

[Vlad Ward]

Mister D, on 30 August 2015 - 05:31 AM, said:

Not sure if this is 100% true because I don't know the code, but it seems the most logical explanation.

More reasonable than the 12m high guns shooting down on a 6m tall mech at extreme close range and hitting the back half of the roof?

People come up with the most complicated explanations for the simplest problems sometimes.

[Hashocky]

I've been killed before because someone shoots out my back torso when I'm looking right at them. Pretty sure its not something hanging off my mech that lets him do that. It always pisses me off.

[KraftySOT]

Actually its not HSR.

I can hit most mechs in the rear, from the front.

It is absolutely the geometery and hitboxes. Griffins, Adders, Zeus, Banshees, King Crabs, Timber Wolfs, Direwolfs, I can hit them all in the back, from directly facing its front.

Aim high, aim for shoulders, protrusions, etc. After you figure it out, its pretty easy to do if the enemy stands still and doesnt twist.

[WrathOfDeadguy]

It's not as strange as the occasional shot that'll ignore your armor completely. I've had parts blown off when there's armor still on the paperdoll (where that was the first component lost- not from damage transfer)... the only explanation I can come up with is that on my end, some of the damage didn't register, but on the shooter's end it all did, so the game was trying to reconcile a component destruction with a component that still had armor on it and decided to split the difference.

Wierdness is bound to happen occasionally in online games.

[zagibu]

PS WrathOfDeadguy, on 30 August 2015 - 08:40 AM, said:

It's not as strange as the occasional shot that'll ignore your armor completely. I've had parts blown off when there's armor still on the paperdoll (where that was the first component lost- not from damage transfer)... the only explanation I can come up with is that on my end, some of the damage didn't register, but on the shooter's end it all did, so the game was trying to reconcile a component destruction with a component that still had armor on it and decided to split the difference.

Wierdness is bound to happen occasionally in online games.

Damage is completely server-authoritative, it's not possible that two players have different outcomes.

[Vxheous]

I think that it is HSR, you usually only see this happen with projectile weapons (AC20, AC5, Gauss). What I think is happening (I could be wrong) is that the shot comes from the front, but the server interprets it hitting you somewhere within your mech due to ping differences, and so you take back damage because the projectile was detected to not have hit you in the front, but "in transit" through your torso.