What's Up With Srm Hitreg?
#1
Posted 30 June 2020 - 06:04 PM
Have SRMs always been that terrible at HitReg? I thought PPCs were bad, but HOLY CRAP!!! Honestly, when a PPC misses, I can see where I shot under someone's arm or something, but SRMs spread. Even if I'm accidentally shooting through an armpit, most of them should still hit the arm, side torso, and a little on the CT. Especially without Artemis, and from 150-200m away. Even a single missile in a salvo of 24 will register a "hit" on the crosshairs, so to have all 24 missiles "miss" when they clearly strike the torso areas of a target is frustrating to say the least.
And for some reason, I can't replicate this in the testing grounds. Only in live combat. I've got a few videos of it. I just need to upload them somewhere since MWO's forums can't support video or image hosting.
If IS SRMs have always been that bad, is PGI doing anything to fix them?
#2
Posted 01 July 2020 - 05:27 AM
#3
Posted 01 July 2020 - 05:35 AM
#4
Posted 02 July 2020 - 03:26 PM
EDIT: It embedded on its own! Nice! First time that happened. I wonder if it's because it was the first bit of text, instead of the third or fourth paragraph. Skip ahead to when the match starts (4 minutes), and then just watch me fight, cringeworthy though it may be. There are three or four examples of what I'm talking about, because every 2nd shot missed, even if it was pointing straight at the target.
1st example is just after 6:50. It's pretty consistent after that. I think the shots prior were spaced out enough for the doors to close between shots.
Edited by C337Skymaster, 02 July 2020 - 03:31 PM.
#5
Posted 02 July 2020 - 04:45 PM
You can try to remove some cool down quirks see if that helps.
#6
Posted 09 July 2020 - 10:45 AM
Monkey Lover, on 02 July 2020 - 04:45 PM, said:
You can try to remove some cool down quirks see if that helps.
It wouldn't. I skilled this up from zero and noticed it right away when I took it out the first time. I get Seismic first of anything, then go to cool run, mobility, THEN firepower last of all, so I didn't have cool-down of any sort for a very long time. The 'mech has some inherent cooldown quirks, I think, but I can't remove those manually.
#7
Posted 09 July 2020 - 10:53 AM
Monkey Lover, on 02 July 2020 - 04:45 PM, said:
You can try to remove some cool down quirks see if that helps.
You know what? I think you're on to something, there. In these cases, I'm holding the mouse button down, and letting the weapon refire as soon as it's done cooling down. The cooldown bar starts when I click the button, though, not when the weapons fire, so the weapons start cooling down while the doors are still opening. Thus, there hasn't been enough time from the actual projectile flight until the next attempted projectile flight for the weapons to have "really" cooled down, and if there's something in the server that thinks it's preventing cheating, that might be causing the problem.
Now we just need PGI to adjust the cooldown mechanism to start AFTER the weapons fire, and not let the weapons cool down while the doors are opening, because that's wreaking havoc with the cooldown timer and interfering with honest combat.
Thanks for pointing that out! Not something I'm likely to notice while I'm fixated on the crosshairs.
EDIT: and now that I watch for it, I see that it's not using ammo the "2nd" time that it fires, either. Honestly, I'd be interested in seeing these fights from the other point of view, because it's possible that the 2nd shot isn't going through the server, and the other guy isn't even seeing my attempt to shoot again.
Edited by C337Skymaster, 09 July 2020 - 10:58 AM.
#8
Posted 09 July 2020 - 12:26 PM
#9
Posted 09 July 2020 - 01:38 PM
afaik it is related to your client starting the cooldown when you press the button while the server starts it when you actually fire, so when the second shot goes out, you're technically still on cooldown for the server
#10
Posted 09 July 2020 - 01:52 PM
Edited by YouKnowNothing, 09 July 2020 - 01:53 PM.
#11
Posted 12 July 2020 - 04:12 PM
#12
Posted 13 July 2020 - 10:35 AM
#13
Posted 13 July 2020 - 01:27 PM
YouKnowNothing, on 09 July 2020 - 01:52 PM, said:
Nah, that shot at 6:52 simply disappears-- missiles that go wide left don't even impact the building behind the marauder.
#14
Posted 14 July 2020 - 09:22 AM
Monkey Lover, on 02 July 2020 - 04:45 PM, said:
You can try to remove some cool down quirks see if that helps.
Whoa! I went back and re-watched. I didn't even watch the heat bar beyond it going up. I didn't see it rapidly dumping the extra heat when the server says "that never happened". Of course, the cooldown doesn't correct... I wonder, though, if you took overheat damage or shut down from that heat spike, if any of that would get reversed, or if you're still hosed, even though "that never happened"?
#15
Posted 21 July 2020 - 06:38 PM
You did it bro!
#16
Posted 22 July 2020 - 07:04 PM
Kubernetes, on 21 July 2020 - 06:38 PM, said:
You did it bro!
Yup!! I emailed a link to this thread, and a link to that embedded YouTube video to their support email, and that got them to fix it. I'm quite convinced that they don't pay much attention to the forums on their own. You've gotta email them with concrete proof of the issue. Honestly, I think that Monkey Lover's help in diagnosing the fact that it was a server/client mismatch was pivotal, as well. If I'd just gone to them with "I dunno what's happening", they would have ignored it, but because I said "this is exactly what's going on, and you can see it here, here, and here", they went in and fixed it. I'd even be willing to bet it was a 10 minute fix.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users