xenoglyph, on 22 July 2013 - 07:43 PM, said:
First off, where did they say they plan to fix it soon? Secondly, why couldn't they test SRMs internally before they publish the hit detection fix?
"
What about SRMs?!?! Buff them to 2.5!!!
Nuh uh. 2.5 SRM damage causes the same effect as the previous LRM-aggedon. While funny to test, the 6-SRM6 Catapult will decimate any Assault class Mech in 3 volleys. The third volley doesn’t even have to be a full volley, 2 volleys following up with a medium laser will probably kill most builds in the game. So what am I going to do about this? Well let me explain an issue…
Many of you have cited hit detection errors. We’re seeing this as well. While it happens across almost all Mechs, it’s most noticeable with small Mech chassis. Bumping damage is going to help deal a small amount more damage to small Mechs, but the larger Mechs are going to be destroyed VERY quickly. We are investigating the root cause of these detection errors but it’s a deep problem. We need to find out if it’s in HSR (host state rewind) or is it in the simulation running on the server etc etc. Once found we will be pouring heavy resources on to the problem to fix it ASAP. However, I can tell you this, it’s going to take a while to find due to its complexity.
That being said, here’s an opportunity for you to decide your fate when dealing with SRMs. In this feedback thread (
http://mwomercs.com/...-hit-detection/), there is a poll. You can vote to bump SRM damage up to 2.0, not this patch but next, or leave damage as is until hit detection is fixed. Keep in mind, this bump in damage is going to be a fairly big world of hurt for larger Mechs. NOTE: Cut off for voting will be Sunday 11:59PM PST."
From this thread, in the OP:
http://mwomercs.com/...general-update/
I forgot about this line, though: "However, I can tell you this, it’s going to take a while to find due to its complexity." It suggests that, though they will fix it ASAP once they find it, finding it in the first place might take a while. Thus, my earlier post may be somewhat in error.