• Win an RIX Storm S3 Thermal Imaging Scope!

    To enter, all you need to do is add an image of yourself at the range below! Subscribers get more entries, check out the plans below for a better chance of winning!

    Join the contest Subscribe

Applied Ballistics Mobile Moving Target Lead Direction?

robrob2

Private
Minuteman
Jun 13, 2019
26
20
I'm using AB Mobile for Android. It's up to date but I can't wrap my head around the moving target lead direction.

When I set calm wind, 1000 yd target with a moving target of 3 mph FROM 3 o'clock ("Move Angle" 3 o'clock, target moving to the shooter's LEFT), the HUD shows a RIGHT correction of 2.3 mils.

It seems to me the target is moving left so we need a left correction to get in front of the moving target.

Then I change only the target direction to 9 o'clock ("Move Angle" 9 o'clock moving RIGHT) it gives LEFT 2.3 mils.

Am I an idiot or is the moving target correction direction wrong?
 
  • Like
Reactions: Mr Flannel
I think the move angle is the direction it’s going not the direction it’s from.

7100017
 
"right to left is 90 degrees or 3 O'clock" so if the target is moving FROM 3 o'clock it is moving to the shooter's left. The instructions above clearly state target movement is "from" the clock position.
 
Last edited:
Are you using the Apple version? It looks different from my Android version.

Is that with 3 o'clock target direction? If so the bug must be just with the Android version.

Can someone with the Android version back up my results?

I have contacted Applied Ballistics about this but Doc replied with a short, "The direction is correct". He hasn't answered three more emails about the bug.
 
Are you using the Apple version? It looks different from my Android version.

Is that with 3 o'clock target direction? If so the bug must be just with the Android version.

Can someone with the Android version back up my results?

I have contacted Applied Ballistics about this but Doc replied with a short, "The direction is correct". He hasn't answered three more emails about the bug.
Yes I’m using apple which is AB mobile. I believe the Android is AB Tactical. @DocUSMCRetired can probablynassist
 
S
View attachment 7100048
View attachment 7100049
I get a right lead for a target moving left.
Switch the HUD view to show Lead instead of wind. Specifically I’m saying tap on the three dots in top right to show lead instead of wind. I’ve found that what you put in on the target page doesn’t always translate when you show the HUD. Sometimes you have to enter it again.
 
Idk man. Hopefully Doc will see this and chime in. Only thing I can think of is they r saying hold 2.3 on the R side of the reticle which is a L hold technically but that doesn’t make any sense.
 
Since the iPhone version disagrees with my Android version I'm pretty sure it's just a bug. I sent AB an email with a link to this thread. Hopefully Doc will check in.
 
"I’ve found that what you put in on the target page doesn’t always translate when you show the HUD. Sometimes you have to enter it again. "

Yes, I noticed this too. I reported it to Applied Ballistics as a bug. When you switch from "Wind Controls" to "Lead Controls" the previous value stays in the speed control box but the data isn't updated with the new number. For example, with wind set to 9 o'clock and 10mph and lead controls set to 3mph from 3 o'clock, when you switch from wind to lead controls the speed control will show 10mph but the data will be for 3mph target speed. The same thing happens when switching from lead to wind controls.
 
As of today, 9 July 2019, both bugs are still present in the Android version of Applied Ballistics Mobile. I have not heard anything from Doc or AB since the 24 June email.

Could another iOS user confirm the Lead/Wind control bug described in the previous post?
 
Yea, but both of these bugs can cause you to miss your target. I did read that they contract out the actual coding so they may have to go through quite a process to change code.
 
Does the lead factor in the wind and spin drift into the final lead output. I don’t think it is.