Jump to content

Ct Internals Destroyed, Armor Intact?


7 replies to this topic

#1 DodgerH2O

    Member

  • PipPipPipPipPipPip
  • 245 posts

Posted 27 August 2013 - 05:11 PM

I had a match a short time ago where I was killed by some combination of gauss/mpl/ml/srm4 while having armor (yellow in rear, orange in front) and undamaged internals (no prior overheating or overriding). The death screen showed armor in all locations (including the head) but a black CT and cause of death being "Engine Destroyed".

I took a screen shot of it but can't figure out how to upload to forum, not worth making an image host account for one screenshot.

Was this a function of a bug with the new crit system, or (most likely alternative I can think of) a glitch in the paperdoll? Has this happened to other players?

Not quite "Mechs and Loadout" but as I'm not a New Player and there's no real place to ask questions about current weapon mechanics other than this subforum I'm placing it here.

#2 Johnny Reb

    Member

  • PipPipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 3,945 posts
  • LocationColumbus, Ohio. However, I hate the Suckeyes!

Posted 27 August 2013 - 11:52 PM

Overheat damage.

#3 DodgerH2O

    Member

  • PipPipPipPipPipPip
  • 245 posts

Posted 28 August 2013 - 07:18 AM

View PostJohnny Reb, on 27 August 2013 - 11:52 PM, said:

Overheat damage.


I did not overheat anytime prior to this occurring. I guess I should have specified that I did not overheat at the time of death in fact I was not firing any weapons, had not for a while and was in the middle of using jumpjets when I came under fire and blew up almost instantly.

Edited by DodgerH2O, 28 August 2013 - 07:20 AM.


#4 3rdworld

    Member

  • PipPipPipPipPipPipPipPipPip
  • 3,562 posts

Posted 28 August 2013 - 07:19 AM

View PostDodgerH2O, on 28 August 2013 - 07:18 AM, said:


If you'd maybe read the post you'd see that I did not overheat anytime prior to this occurring. I guess I should have specified that I did not overheat at the time of death in fact I was not firing any weapons, had not for a while and was in the middle of using jumpjets when I came under fire and blew up almost instantly.


Any chance you were in the lava?

#5 AlexEss

    Member

  • PipPipPipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • FP Veteran - Beta 1
  • 2,491 posts
  • Locationthe ol north

Posted 28 August 2013 - 12:38 PM

IIRC it is a random bug that happens every now and then. The game just goes a lil spazzy on you. File a ticket as detailed as you can and move on =) If it happen to you more often try to take not on what was happening at the time and make a ticket with that info (or if you have 23 friends try to synch drop and reproduce the bug)

#6 Angel of Annihilation

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • The Infernal
  • The Infernal
  • 8,881 posts

Posted 28 August 2013 - 01:24 PM

Did you have armor both front and back? I know there have been a couple time I was wondering how I had at worst lightly damaged armor and my internals taken out then looked closer and realized I had been cored from behind.

Also, did you have an ammo explosion? This is another thing that will take out internals without taking out the armor since an ammo explosion's damage travels along the internals.

#7 Zerberus

    Member

  • PipPipPipPipPipPipPipPipPip
  • Overlord
  • Overlord
  • 3,488 posts
  • LocationUnder the floorboards looking for the Owner`s Manual

Posted 28 August 2013 - 02:15 PM

It`s happened to me before, maybe 3-4 times in the last >year. I originally assumed they were simply "classic" through armor crits like in TT and didn`t think much of it. But it appears that it is in fact a bug, therefore filing a report with as much uinfo as possible would be teh correct course of action.

#8 KrazedOmega

    Member

  • PipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 499 posts
  • LocationSaskatchewan, Canada

Posted 28 August 2013 - 08:04 PM

I saw a Hunchback 4G the other night that lost its RT but still had armor and also had its right arm. Probably just a bug.





4 user(s) are reading this topic

0 members, 4 guests, 0 anonymous users