While using an AC/20 for ~25hrs of play-time between a Hunchback and an Atlas with huge success - proper lead and prediction with aiming works as I would expect (~90%+ hit-rate).
While aiming with an arm-mounted AC/20 (~8hrs), it does not behave the same. ~50% of the time, the shot fires as I expect. ~20-30% of the time, the shot fires where my arm-reticle was pointing 2-3 seconds prior - and NOT where the O reticle is when pulling the trigger. The remaining shots seem to exhibit other, unexpected behaviors (IE, passing through a SLOW MOVING target, and striking the ground behind).
I have many theories to this, and none can be explained by "internet lag" or "I'm doing it wrong".
Aiming with an arm-mounted Gauss or AC/20 on a Centurion-A/AH did not behave as they do now.
What am I not seeing in the difference?


Ac/20: Arm Vs Torso Mounting
Started by Hythos, Nov 19 2012 08:57 AM
3 replies to this topic
#1
Posted 19 November 2012 - 08:57 AM
#2
Posted 19 November 2012 - 08:59 AM
Hythos, on 19 November 2012 - 08:57 AM, said:
While using an AC/20 for ~25hrs of play-time between a Hunchback and an Atlas with huge success - proper lead and prediction with aiming works as I would expect (~90%+ hit-rate).
While aiming with an arm-mounted AC/20 (~8hrs), it does not behave the same. ~50% of the time, the shot fires as I expect. ~20-30% of the time, the shot fires where my arm-reticle was pointing 2-3 seconds prior - and NOT where the O reticle is when pulling the trigger. The remaining shots seem to exhibit other, unexpected behaviors (IE, passing through a SLOW MOVING target, and striking the ground behind).
I have many theories to this, and none can be explained by "internet lag" or "I'm doing it wrong".
Aiming with an arm-mounted Gauss or AC/20 on a Centurion-A/AH did not behave as they do now.
What am I not seeing in the difference?
While aiming with an arm-mounted AC/20 (~8hrs), it does not behave the same. ~50% of the time, the shot fires as I expect. ~20-30% of the time, the shot fires where my arm-reticle was pointing 2-3 seconds prior - and NOT where the O reticle is when pulling the trigger. The remaining shots seem to exhibit other, unexpected behaviors (IE, passing through a SLOW MOVING target, and striking the ground behind).
I have many theories to this, and none can be explained by "internet lag" or "I'm doing it wrong".
Aiming with an arm-mounted Gauss or AC/20 on a Centurion-A/AH did not behave as they do now.
What am I not seeing in the difference?
This has been a problem since CB with arm mounted ballistic weapons with sub 1200m/s velocities. The AC10 suffers from the same problem.
#3
Posted 19 November 2012 - 09:18 AM
xRaeder, on 19 November 2012 - 08:59 AM, said:
This has been a problem since CB with arm mounted ballistic weapons with sub 1200m/s velocities. The AC10 suffers from the same problem.
I dunno; It felt much different up until just before Open Beta.
Also - the hours I've mentioned are from the past three days - in OB vs CB... so it is a current-state vs previous (change?) I suppose.
Additionally - velocity should not affect the firing... IE - arm-motion 'lag' while aiming. If that's hard-coded and intentional, I have my answer.
#4
Posted 19 November 2012 - 09:23 AM
The other thing that makes aiming difficult is the lead time you have to factor in is also affected by if your mech is moving, if your turning, and if your torso is twisting. And the ping time of your target. Each of them dramatically changes the aim point.
Mech turning seems to have the most dramatic effect. Whenever I have to line up a shot, I make sure I'm not turning at the same time. Makes a huge difference.
Mech turning seems to have the most dramatic effect. Whenever I have to line up a shot, I make sure I'm not turning at the same time. Makes a huge difference.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users