You built a profile in a ballistics app, typed in the numbers off the ammo box, and got a clean drop chart. Then you shot at 450 yards and hit four inches low. The rifle didn't lie — the inputs did.
Truing (some solvers call it calibration) means reconciling what the calculator predicts with what the bullet actually does. You shoot at known distances, measure where the impacts really land, and adjust the two inputs you can't cheaply measure to high precision — muzzle velocity and ballistic coefficient — until the predicted curve passes through your observed hits. Done right, it turns a generic firing solution into one that matches your barrel, your ammo lot, and your air. Every serious long-range shooter does it, whatever their software calls the button.
The box velocity is not your velocity. Factory velocity figures come from test barrels that are usually longer and tighter than the barrel you're running. Differences of 50–100 fps between the box number and what the same ammo does in your rifle are routine, and lot-to-lot variation adds more on top. An MV error you'd never notice at 100 yards becomes a miss at 500.
Published BC is an average, at best. Drag changes with velocity, so a single G1 number is really an average over whatever speed band the manufacturer measured — which may not be the band your bullet flies through. Some published BCs also run optimistic. G7 referencing fits modern boat-tail bullets better across the band, but no single number is exact. Your effective BC even depends on your rifle: a bullet that's only marginally stabilized in your twist flies with more drag than the book says.
The air changes. Density altitude moves with temperature, pressure, and elevation. A solver handles that fine — if you actually feed it current conditions instead of whatever was saved last month.
And the system around the solver lies too. Turrets don't always track at exactly their nominal click value. Sight height gets measured with a guess. "The 500 berm" is sometimes 460. None of that is a ballistics problem, but all of it shows up as one — and if you don't rule it out first, you'll "true" a scope problem into your velocity number.
The order is the whole trick. Muzzle velocity and BC both affect drop, but not equally at every distance. At mid-range, drop is governed mostly by time of flight, and time of flight is governed mostly by muzzle velocity — the bullet hasn't flown far enough for drag differences to separate a good BC guess from a bad one. At long range the roles flip: velocity has bled off, drag has been acting on the bullet for a long time, and BC error dominates the miss.
So you isolate one variable at a time, in the range where it dominates.
Pick a verified distance far enough that drop is substantial and cleanly measurable — a couple of mils, not a half inch — but short enough that BC barely matters. For most rifle cartridges that's somewhere in the 300–600 yard window. Dial the solver's predicted correction, shoot a group at a clear aim point, and measure the vertical distance between the group's center and the point of aim. Then adjust MV in the solver until predicted drop matches actual drop at that distance.
Sanity-check the result. Trued MV should land reasonably near your chronograph reading or the box number. If the solver needs a wild velocity to fit your impacts, the problem isn't velocity — go find the bad zero, the mis-ranged target, or the turret that doesn't track true.
With MV locked in, move as far out as you can get a verified distance and readable impacts — well past your MV-truing distance, and ideally while the bullet is still comfortably supersonic. Shoot a group, measure the vertical error of its center, and adjust BC (leaving MV alone) until the prediction matches. If the fit is good at both your mid and long distances, the whole curve between them is now trustworthy.
Don't try to true through the transonic zone. As the bullet approaches the speed of sound, drag behavior changes in ways a single BC tweak can't represent. True BC at your farthest reliably supersonic distance and treat anything beyond that as its own project.
Do it in the wrong order and you bake velocity error into your drag number. The solver will bend the curve until it agrees with you at one distance — and disagrees everywhere else. That's the classic "my dope is right at 600 but off at 350 and 800" signature.
Truing on a windy day. Wind doesn't just move bullets sideways. A crosswind also produces a small vertical deflection (aerodynamic jump), and gusty conditions smear the group so its center is less trustworthy. Vertical error you blame on drop may be wind. If you must shoot in wind, at least keep it steady and log it — but the honest answer is to true on a calm morning.
Truing BC before MV. Covered above, and it's the most common ordering error. MV first, always.
A bad zero underneath. The second most common. Truing assumes your zero is perfect; every bit of zero error becomes phantom ballistic error downrange.
Truing off one impact. You just calibrated your solver to a random draw from your rifle's dispersion. Group centers or nothing.
Trusting the turret blindly. If your scope's actual click value is a few percent off nominal, every dialed correction is scaled wrong, and truing will absorb the scope error into MV. A tall-target test — dialing a known adjustment at 100 yards and measuring the actual shift on paper — separates scope error from ballistic error. Do it once per scope.
Ignoring temperature. Powder burns faster when it's hot. A muzzle velocity trued in August is not your January velocity. Log the conditions you trued in, and re-true (or keep seasonal profiles) when the temperature swings far from them.
Zero Considerations builds this workflow into the same photo loop it uses for zeroing. Print one of the free targets — the corner markers are coded, so a photo of the target gives the app true scale and lets it correct camera tilt and perspective. Shoot your group at a verified distance, photograph the target, and the app finds the holes, computes the group center, and compares actual drop against the prediction for your rifle and load. From that difference it backs out your trued muzzle velocity — stage one of the two-stage order described above. Stage two is yours to make: adjust BC by hand in the load editor once you have long-range data. The app solves for velocity, not for BC.
The trued numbers then feed everything downstream: the drop table, DOPE cards, turret clicks, and reticle holdovers for your specific optic. It all runs offline at the range, and it's a one-time $9.99 purchase — no subscription, no account.
Print a target, shoot a group, photograph it, and let the app do the measuring and the math.
Zero Considerations — photograph the target, get the measured group and the exact clicks to dial, then keep the DOPE. One-time $9.99 on both stores — no subscription, no account, works with no signal.
App Store — $9.99 once Google Play — $9.99 once What it does Free printable targets
On Android, Google Play gives you 48 hours to ask for a refund — try it on your next range trip and keep it only if it earns its spot in your range bag. Not ready today? Wishlist it on Google Play and Google will notify you if the price drops before opening day.