ARMHOLD MUSCLEHOGGER, on 10 October 2025 - 07:39 AM, said:
Im sorry you got a little confused there. In the second example I clearly had the line "as another example".
As you were speed reading my post (likely because you disagreed with it and wanted to give a snappy retort) you seemed to have missed the point and instead threw out a bunch of wonderful LRM word salad that fits very closely with what PGI says. Thanks, Ive read their explanations and responses to similar complaints already.
Selective bias. You believe the LRMS are acting as they should. Slow hand clap for being able to know all the lrm mechanics (OR copying and pasting lrm data). Again thats just how the are SUPPOSED to work.
In response to your "your either not being completely truthful or not separating different situations..." comment. That as you say involves "shifting tales" I again refer to my clear statement of "as another example" which leaves you calling me essentially a liar.
This is against the rules of this forum. Im going to have to assume that your snarky insulting response that you took such lengthy effort to find fault with seems to have fallen a bit flat. Are you PGI? Did you write code for this game? Are you a Big fan of PGI and got mad for some reason? I can list all the many elements to LRM that has been posted by PGI over the years so I really dont think you need to but thanks.
So, my suggestion is, slow down, make sure you read what is written, ask questions if you think Im being "shifty" or "not being completely truthful" try staying away from vomiting bias before asking questions. I will be recording a series of videos to show exactly what I was referring to in my multiple and separate examples you couldn't separate for some reason.
I dont think your being shifty or lying. Lets stay away from not being friends eh? Lets all come home for the big win and see if what is going on with LRMS is an honestly unsolvable problem with the programming that has been swept under the rug, or maybe, god forbid, an overlooked issue that can be fixed on a reduced budget.
As you were speed reading my post (likely because you disagreed with it and wanted to give a snappy retort) you seemed to have missed the point and instead threw out a bunch of wonderful LRM word salad that fits very closely with what PGI says. Thanks, Ive read their explanations and responses to similar complaints already.
Selective bias. You believe the LRMS are acting as they should. Slow hand clap for being able to know all the lrm mechanics (OR copying and pasting lrm data). Again thats just how the are SUPPOSED to work.
In response to your "your either not being completely truthful or not separating different situations..." comment. That as you say involves "shifting tales" I again refer to my clear statement of "as another example" which leaves you calling me essentially a liar.
This is against the rules of this forum. Im going to have to assume that your snarky insulting response that you took such lengthy effort to find fault with seems to have fallen a bit flat. Are you PGI? Did you write code for this game? Are you a Big fan of PGI and got mad for some reason? I can list all the many elements to LRM that has been posted by PGI over the years so I really dont think you need to but thanks.
So, my suggestion is, slow down, make sure you read what is written, ask questions if you think Im being "shifty" or "not being completely truthful" try staying away from vomiting bias before asking questions. I will be recording a series of videos to show exactly what I was referring to in my multiple and separate examples you couldn't separate for some reason.
I dont think your being shifty or lying. Lets stay away from not being friends eh? Lets all come home for the big win and see if what is going on with LRMS is an honestly unsolvable problem with the programming that has been swept under the rug, or maybe, god forbid, an overlooked issue that can be fixed on a reduced budget.
I explain exactly what LRMs do and how they react in game. From experience. I practically wrote the guide on how to use LRMs. Wait. I did write a guide on how to use them. There is a link right at the bottom of every post I make to said guide. It's a little dated, but still completely accurate. (Trying to be funny here, encase you missed the link.)
From my many years of using LRMs, I can say they do not "home in on legs", or any other specific component. I use LRMs, a lot. My main ride is a rather controversial Huntsman Prime with 4 ERMLs and 2 CALRM15s. Most of my stable of mechs uses some form of LRMs (though not all, as that would be boring to play only the same thing all the time). I do believe, from experience, that I know what I'm talking about when it comes to LRMs and how they function, in practice and on the theoretical "technicalities".
I can say how they are suppose to work, and even times and conditions that they do not work "as they are suppose to". I can even go into great depth, which I've been trying not to, as it can be a lengthy "word salad" endeavor to go into all those technicalities and try to think and remember all the "not working as advertised" situations that can happen.
Suffice to say, LRMs are not inherently designed to hit "only legs", but there are situations and cases where they might favor hitting the legs over other components on a target. Sometimes, that even depends upon the target itself, as each mech's shape and the position of their hit boxes can play a role into where damage might get assigned to. Easy example, the Marauder is known for having a thin CT, so it's easy to spread damage across your torso by "wiggling your nose" when getting hit from the front. If targeted from the side though, it's almost going to be all damage to your ST, as your CT is almost completely hidden behind it.
I do want to comment, yes. You did say "another example". I somehow failed to catch that, causing my own confusion. I apologize for that. I tend to, every time I go to make a post, get pulled away while typing so I can't just "respond". For example, I started this post at 3:50ish, and it is now 5:20ish. I have been interrupted several times already since trying to make the post. (There is a reason my Jarls says I am retired. Not from lack of desire to play, but lack of life letting me play.) There was a reason I gave space for something being mis-stated, or more accurately, misread in this case?
As for the videos, post links to them here. Just realize, it happening once isn't a pattern... And I'm not claiming LRMs aren't more likely to hit legs over other components, though they do have a bit more chance to hit legs, depending completely upon what the mech's shape is and it's movement at the time. They are not designed to hit "only legs", and they rarely should hit "only legs". They should still be aiming for your Center of Mass, and artificially spreading from there. Beyond that, the final determination of where they hit depends upon where the missiles last angled themselves before fulling committing to their path (which is a combination of Tracking Strength and Velocity).
I can strongly say, with utmost confidence, that Aimbots are not being used to enhance LRM performance. They can't do anything to help LRMs. In order for someone to "enhance" their LRMs to target any specific component, they would have to hack into the server they are playing on, and change the parameters there (as MWO is a server authoritative game). I highly doubt anyone is doing that...
I will say, as far as I can tell, LRMs are a lot weaker than they use to be, and I do believe they are usually "acting as intended". I've not seen anything wrong with how they behaved when I was last playing a few months ago. If there is any problems, it's with it's LoS or Indirect determination program, as I've seen LRMs shoot with indirect when I could see the target, and other times it shoots with direct fire arcs when I can't see the target at all. (Not saying I wouldn't mind discussing or testing a change for LRM mechanics.)

















