I hope that's all it is, maybe I missed a setting somewhere; I'll use an example that I've actually shot:
(note: embedded images for formatting purposes; I missed the table option)
Next is an Example that I haven't confirmed at distance but illustrates the issue:
In short, Comeup and Windage MOA and MIL values seem to be good, but drop and energy value readouts in the range card, to my knowledge, simply can't work in the equations.
Ex, using above values:
4.6 MIL = 46cm @ 100m; therefore 4.6 MIL = 276cm @ 600m (~278.9cm)
4.40 MIL = 44cm @ 100m; therefore 4.4 MIL = 264cm @ 600m (263.8cm)
4.45 MIL = 44.5 cm @ 100m; therefore 4.45 MIL = 267cm @ 600m (
351.2cm?)
or, (using
shooterscalculator and
ballistics101)
130gr @ 1676 fps = 811 ft. lbs. (811.3)
130gr @ 1695 fps = 829 ft. lbs (829)
130gr @ 1974 fps = 809 ft. lbs (
596.73?)
Spin Drift, Coriolis, and Aerodynamic Jump are Disabled, MV-Temp and DSF tables are Cleared, and all calculations were run using International Standard Atmosphere values. Unit is running Firmware V4.10.
I'm curious if this is a bug of this specific unit, or a "feature" of the line. Elevation and Windage MIL/MOA values look good, but the drop/energy output errors don't exactly inspire confidence in the unit's accuracy, especially once error/tolerance stacking is factored in and distance increases.
Thanks again.