Okay, this one is kinda hard to sum up in a subject, but I tried my best.
I was just running around in my cicada and realizing I was having a really hard time being accurate with my shots. It seemed like my crosshairs were all over the place! This seems odd to me, since in this configuration I have no weapons on my arms whatsoever, all my guns are on my torso, so why should I ever be firing anywhere but straight ahead?
Under closer inspection, I realized that when aiming, my whole torso moved, but my view lagged behind. This seems so backwards! I'm sitting in the torso of the mech, and I twist the mech to the right, and for some reason my view lingers back to the left? The pilot's head doesn't even have to move to stay in sync with the torso's crosshairs!
Where it gets really weird is later: After maintaining a sustained torso twist, eventually the view catches up and PASSES the crosshairs. You can imagine why I've been so disoriented!
tl;dr: When starting a turn to the right, my crosshairs move to the RIGHT side of my screen (along with the rest of the torso) so my view is lagging behind, then after a moment, my view passes the crosshairs, so now the crosshairs are on the LEFT of my screen.
I'm guessing this only affects mechs with very high torso twisting speeds, but it's something that should be looked at.
Okay, I just found a bug report of this, apparently this only affects the cicada. I can't reply to that thread anymore, so I'm linking it here.
http://mwomercs.com/...-bug-cicada-2b/


View Not Accurately Following Torso Reticle
Started by Tresch, Apr 22 2013 02:41 PM
6 replies to this topic
#1
Posted 22 April 2013 - 02:41 PM
#2
Posted 22 April 2013 - 03:51 PM
just confirmed that it does apply to the jenner as well.
#3
Posted 22 April 2013 - 04:13 PM
I think I experienced the same problem with another mech, not remember which one though. So your view is moving ahead of the targeting reticle AFTER upgrading the basic efficiency of torso twist speed (before that I think they were in sync).
Edited by Neolisk, 22 April 2013 - 04:13 PM.
#4
Posted 22 April 2013 - 04:42 PM
It's likely due to uneven torso and arm twisting speeds after you get the torso twisting speed tweak and the arm reflex tweak.
One thing you can probably do to mitigate it is enable the arm-lock in settings when you pilot the Cicada.
One thing you can probably do to mitigate it is enable the arm-lock in settings when you pilot the Cicada.
#5
Posted 22 April 2013 - 04:47 PM
Durant Carlyle, on 22 April 2013 - 04:42 PM, said:
It's likely due to uneven torso and arm twisting speeds after you get the torso twisting speed tweak and the arm reflex tweak.
The thing is that it happened for me on a mech that has no arms (why do you even have arm reflex there?), meaning arm and torso reticle are one thing. And yet the view goes first, and then both reticles catch up.
#6
Posted 22 April 2013 - 05:11 PM
I'm confused.
As far I know it does this on every mech.
You can look faster then your mech can turn so when you look to the side really fast it takes time for the mech to catch up. Your torso weapons do have a bit of freedom to move so they your cross hair can move across the screen too.
As far I know it does this on every mech.
You can look faster then your mech can turn so when you look to the side really fast it takes time for the mech to catch up. Your torso weapons do have a bit of freedom to move so they your cross hair can move across the screen too.
Edited by Hauser, 22 April 2013 - 05:12 PM.
#7
Posted 23 April 2013 - 10:37 AM
No, actually, I think you misread.
I would potentially expect the view to move first and then have the crosshairs catch up, but this is NOT what happens. The crosshairs move first, and then the VIEW catches up. Eventually the view catches up and PASSES the crosshairs, leaving them lagging behind.
I would potentially expect the view to move first and then have the crosshairs catch up, but this is NOT what happens. The crosshairs move first, and then the VIEW catches up. Eventually the view catches up and PASSES the crosshairs, leaving them lagging behind.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users