Jump to content

[Bug] Cataphract Armour Damage Both Sides/


9 replies to this topic

#1 Zagum

    Member

  • PipPip
  • Elite Founder
  • Elite Founder
  • 48 posts

Posted 15 December 2012 - 02:55 PM

In all my Cataphracts (3d, 4x and muro) I am taking damage to my CT while my back is facing the enemy. I am taking damage to my BT and CT at the same time. This needs to be looked into. Also, my CT is taking damage while I am turned 90 degrees to the enemy with no damage to my arms. Something is not right.

#2 Straylight

    Member

  • PipPipPipPipPipPipPip
  • Knight Errant
  • 535 posts
  • LocationHarlech, Outreach

Posted 15 December 2012 - 09:47 PM

Direction is not the same thing as hit box. I can't speak to the Cataphract, but I know that tagging a Centurion between the legs from behind does damage to its (front) CT, and that all of the Hunchback's hunch is considered (front) RT.

In the Mechbay, rotate the 'mech around while you have a component selected in the Loadout screen. The highlighted sections don't correspond perfectly to hitboxes, but they give you a general idea.

#3 Willie Sauerland

    Member

  • PipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 1,209 posts
  • LocationKansas City, Missouri, USA

Posted 15 December 2012 - 10:25 PM

Might have something to do with this:

http://mwomercs.com/...ost__p__1602892

#4 Straylight

    Member

  • PipPipPipPipPipPipPip
  • Knight Errant
  • 535 posts
  • LocationHarlech, Outreach

Posted 15 December 2012 - 11:31 PM

View PostWillie Sauerland, on 15 December 2012 - 10:25 PM, said:

Might have something to do with this:

http://mwomercs.com/...ost__p__1602892

No, it mightn't have. That was a purely visual bug, as that post notes.

#5 Corvus Antaka

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Knight Errant
  • Knight Errant
  • 8,310 posts
  • Twitch: Link
  • LocationInner Sphere

Posted 16 December 2012 - 11:51 AM

Every mech can be hit in the CT simply by targeting the crotch between the legs. This is the same flaw mech4 had, and as the game evoles crotch shots will only be a bigger problem. The only fix is to move the crotch to do leg damage instead of CT damage.

#6 Straylight

    Member

  • PipPipPipPipPipPipPip
  • Knight Errant
  • 535 posts
  • LocationHarlech, Outreach

Posted 16 December 2012 - 01:05 PM

View PostColonel Pada Vinson, on 16 December 2012 - 11:51 AM, said:

Every mech can be hit in the CT simply by targeting the crotch between the legs. This is the same flaw mech4 had, and as the game evoles crotch shots will only be a bigger problem. The only fix is to move the crotch to do leg damage instead of CT damage.

Why is that an issue, though? Unless your armor distributions are very strange, the CT is your most well-protected location. I'd RATHER take hits there than to my CT® which has, at best, about a quarter the protection.

#7 Gargel

    Member

  • PipPip
  • 26 posts

Posted 17 December 2012 - 02:09 AM

Guys, I think you are misinterpreting the OPs questions. It's twofold:

1. He noticed when taking damage to rear center torso, he also takes damage to front center torso.

However, as you pointed out, its probably that a damage-over-time weapon like a laser, hit the "tail"/crotch and the rear center torso, which would make both areas light up on the paper doll.

2. He also noticed that when turning 90 degrees to incoming fire, his center torso took damage while no arm damage was registered. This is HIGHLY unlikely since the center torso is barely visible from the side of a cataphract. (Apart from a small piece sticking out of the left-right-torsos)

I can only speak for myself when I say I have noticed this too. However, if there was a quick turn to spread damage out, the latency could affect where you think you should have been hit. But if its not latency related, then it's something worth looking in to.

Edited by Gargel, 17 December 2012 - 02:11 AM.


#8 Straylight

    Member

  • PipPipPipPipPipPipPip
  • Knight Errant
  • 535 posts
  • LocationHarlech, Outreach

Posted 17 December 2012 - 03:12 AM

View PostGargel, on 17 December 2012 - 02:09 AM, said:

2. He also noticed that when turning 90 degrees to incoming fire, his center torso took damage while no arm damage was registered. This is HIGHLY unlikely since the center torso is barely visible from the side of a cataphract. (Apart from a small piece sticking out of the left-right-torsos)

I can only speak for myself when I say I have noticed this too. However, if there was a quick turn to spread damage out, the latency could affect where you think you should have been hit. But if its not latency related, then it's something worth looking in to.
As you say, there's every chance that he wasn't precisely perpendicular to whatever was shooting at him and that something raked his CT as he was moving, or there was a second shooter he wasn't aware of. Occam's razor, aye?

#9 Corvus Antaka

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Knight Errant
  • Knight Errant
  • 8,310 posts
  • Twitch: Link
  • LocationInner Sphere

Posted 17 December 2012 - 12:00 PM

View PostStraylight, on 16 December 2012 - 01:05 PM, said:

Why is that an issue, though? Unless your armor distributions are very strange, the CT is your most well-protected location. I'd RATHER take hits there than to my CT® which has, at best, about a quarter the protection.


because you can stand behind a mech, shoot him in the crotch, and hit the front center torso. This also causes the damage issues others are noting.

#10 Straylight

    Member

  • PipPipPipPipPipPipPip
  • Knight Errant
  • 535 posts
  • LocationHarlech, Outreach

Posted 17 December 2012 - 08:37 PM

View PostColonel Pada Vinson, on 17 December 2012 - 12:00 PM, said:

because you can stand behind a mech, shoot him in the crotch, and hit the front center torso. This also causes the damage issues others are noting.
So aim at his back, if you want to shoot him in the back?

So long as the hitbox behavior is consistent, the only "issue" is players failing to understand how the system works.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users