If you already haven't, maybe try the following;
double-check scope height, zero offset, turn off spin drift and Coriolis and then try truing BC/MV from there.
Coriolis/SD/CWAJ/wind-deflection are secondary effects. Gravity being the primary. Gravity is the solvers' "baseline zero reference"
If your solver of choice supports it and it exists in your recorded numbers. The solver needs to account for it when "Lining Up" the trajectory
BEFORE making adjustments to MV or BC
By turning off settings you’re putting “Effect” before “Cause”
The “Cause” has to be enabled in software for the “Effect” to be present in your recorded results.
When you turn off “Coriolis” settings in most apps (Which groups Latitude and Azimuth together.) The solver is going to give you an equivalent solution based on the “physics” of a North Azimuth in Ecuador. (AZ:0/LAT:0) Which is NOT the REALITY of the output recorded on location. (Unless you actually are shooting on a north azimuth in Ecuador)
(example) “recorded” impact @1225 yards was 10.5 mils facing
270 W”
(going counter-clockwise) This is what was shot in reality
@1225 yards 10.5 mils on AZ:270 W (the real-world location:right output)
@1225 yards 10.4 mils on AZ:180 S
@1225 yards 10.3 mils on AZ:90 E
@1225 yards 10.4 mils on AZ:0 N
(This is what the MV/BC should be “lined up” back to: 10.4 @ AZ:0 N)
(going clockwise)
This is what “Lining up" the solver by “turning it off” does.
@1225 yards 10.5 mils on AZ:0 N (“Lining Up” from here gives you MV/BC for 10.6@270 W)
@1225 yards 10.4 mils on AZ:90 E
@1225 yards 10.5 mils on AZ:180 S
@1225 yards 10.6 mils on AZ:270 W
(the real-world location:wrong output from “recorded”)
(example) Actual target facing 270 W
(Settings turned on to match real-world azimuth) 1000 yd 7.4 mils@ az:270 W rem v=1669 tof = 1.370
BC= G1 .563
(Settings turned off to match "Shooters’ 12:00" Orientation to same target) 1000 yd 7.4 mils@ az:0 N rem v=1636 tof = 1.384
BC= G1 .545
Even if you only recorded data to 600 yards. (where Coriolis “doesn’t matter”) If the target faces 270 W the solver needs to know to account for it.
In the context of "Lining Up" (Backward-Extrapolating) “Your System” The Azimuth-of-fire and latitude is what aligns the solvers’ “zero” and the shooters’ “zero” (mechanical zero) so the “physics” are starting from the same “Baseline zero reference”
This way when you travel and update your (azimuth/lat) for the new location/target direction the solver is applying the correct “physics” going forward. (Instead of having to keep adjusting the MV/BC to compensate for the wrong azimuth/lat) You update the “Coriolis” setting just like you update the environmental info)
If you have any bias that wasn’t accounted for in the software prior to “Lining Up” (Backward-Extrapolating) you will be extrapolating back to where the solver "thinks" zero is. Which may or may not be where “mechanical zero” is.
That "bias" is going to be compensated for by getting adjusted into your MV (elevation) or BC (windage)
. I tried using the applied ballistic program and I cannot get it to match my Vortex LRBC data (which is correct for my rifle). Ive messed with all the setting possible to get it to match but nothing is working for me. It is coming in anywhere from .2 to .6 Mils off of my Vortex data. Any insight on what to do to get it matching up correctly. So far I am not impressed with the app. Only reason I am currently messing with it is because Vortex decided to change their program.
