So I noticed this when tweaking my Battlemaster and haven't had the time to test it for more variants yet, but when I was running with low (well under 50%) leg armor my torsos would get absolutely shredded as if I had a similar amount of armor on them - 30 as opposed to the 96 that was on the front CT.
Recently switched up the build I was using an now have nearly max leg armor to use up extra weight and after this the torsos seem to take a vast amount more damage before critting out.
So this gives me the notion that they are doing some % based caclulations on your armor at some point in the process that determines the in-match value based upon how much overall armor you have. Running armor light even if its just in the legs just may reduce the rest of your armor ratings in the match calculations.
Just a curious result, and I'll do some more testing on it to see if something fishy is going on there because I do recall some of my assaults seeming rather unarmored compared to what they actually were in the mechlab. Maybe some other guys have have been seeing something similar though, and this might be the cause of your troubles.
0
Weird Armor Calculations
Started by sycocys, Apr 13 2015 07:28 AM
5 replies to this topic
#1
Posted 13 April 2015 - 07:28 AM
#2
Posted 13 April 2015 - 07:30 AM
It's probably due to the placebo effect and/or dumb luck. This would be extremely weird if it was true, and I don't think that even Paul Inouye could think of something this convoluted.
#3
Posted 13 April 2015 - 07:40 AM
It might be just dumb luck - but I switched up the build after getting solo'd by a single mech in less time than it took to cycle my MPL. Laser only straight ct damage from 100% with 96 front armor in less than 3 seconds, as far as I know there's no mech that has 100+ laser dps burst in that short of time.
Lots of runs after cranking up my leg armor and while the Battlemaster still does get hit in the ct plenty, there's not been any where near the squishiness it was experiencing prior. As if raising my leg armor made it actually register that I had 96 armor on the front ct.
My assumption is that it is more than likely something to do with their trademark super programming skills more than an intentional thing.
Lots of runs after cranking up my leg armor and while the Battlemaster still does get hit in the ct plenty, there's not been any where near the squishiness it was experiencing prior. As if raising my leg armor made it actually register that I had 96 armor on the front ct.
My assumption is that it is more than likely something to do with their trademark super programming skills more than an intentional thing.
#4
Posted 13 April 2015 - 07:43 AM
Get a couple buddies with premium time and go to the private lobby, test this and get some good data.
#5
Posted 13 April 2015 - 07:50 AM
cdlord, on 13 April 2015 - 07:43 AM, said:
Get a couple buddies with premium time and go to the private lobby, test this and get some good data.
It's an excellent idea to spend some time fighting 1v1 in private lobbies anyway. It's much better for building basic skill and simple combat awareness than 12v12 pug drops are.
For this case, fighting in a private lobby eliminates the extremely likely possibility that you were taking fire from 2+ hostiles at the same time and just didn't notice.
#6
Posted 13 April 2015 - 09:32 AM
In the case that set off the load out change it was on HPG Manifold behind one of the walls at the gateways. With heat vision on and bap I can be reasonably certain that it was indeed 1v1 with him coming up the little ramp towards me. But there was many matches prior and post that lend to supporting my thought here. Really not sure why it would do it other than some unintended bug, then again they have some ridiculously over complex algorithm for the weapon damage so there's no saying they don't for the armor as well.
I will though test it out further, with some other mechs I had armored in a similar way that were getting cored much quicker than they should have.
I will though test it out further, with some other mechs I had armored in a similar way that were getting cored much quicker than they should have.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users