But any changes to velocity will affect my longer solutions, which right now are dead on.
Bang
The idea is to make them all line up. Since you’re using BC and not a custom curve, if all your input data is correct:
Shoot longer distances, 7, 8, 1000.
Adjust BC if needed to make those line up if needed
Shoot at distances 600 and in, tweak velocity to make those line up.
Then go back and tweak BC again if needed to make the further distances line up again.
I’d also suggest ditching the numbers Sierra is giving and either use the g7 or custom curve provided by Applied Ballistics. It’s their software and the numbers they provide from their testing will work better.
Again, the idea is to gather real world data, and then tweak the numbers in the calculator to make it all line up. Don’t get hung up that things will take a little tweaking and be on a sliding scale. I.E. you
Change velocity a little to get the closer ranges to work, and then you have to go back and tweak BC a little to get the further numbers lined up.
General rule of thumb:
<600yds = velocity truing
>600yds = BC truing
When using custom curve, your only option is velocity truing unless you have access to transonic ranges.
I usually gather data out to 1k. I just use the calculator to get me close, then ignore it and write down real data.
I’ll then go back, not at the range and use a custom curve and a g7 profile. I’ll use the data I collected and see which one is easier or lines up better. This far, I’ve had pretty good luck with custom curves.