Groper, I shoot many rifles, I only have this problem with one rifle, so I dunno. I know how to adjust my click values and have had to do the same for several scopes. The repaired scope may actually be on another rifle. I do know that I often measure the distance between POA and POI and use the dials l to correct these and have never noticed any real deviations. I have also used the MOA reticule as part of the equation without noticing any real differences. Say one day I dial 12 MOA, then the next day instead of dialing hold 10 MOA and dial two MOA, no problems.
The only difference with this particular rifle is a 40MOA base rather than a 20MOA base. So I have to keep coming back to that in the back of my mind. I cannot wrap my mind around what relating to the base would cause this, but do not know enough about the subject to even venture a guess. I have not shot the rifle much in the last year because of illness, and probably will not play with it again until I start getting ready to head to NM to shoot cow elk.
I am not aware of a G7 BC for this bullet but would be interested in trying it.
Why would I change a known value such as velocity to make a correction to BC. Maybe you are finding problems with BC that you are factoring out in the same manner in which I resolve mine. I have a chart around somewhere with my actual drops shot on a tall target (10 ft). I can make these drops match exbal predictions almost perfectly out to a mile using a stepped G1 BC.
Most times when I build a rifle I have the rifle sighted in within 3 shots at 100, assuming I do a good job bore sighting the rifle by looking through the bore. Even cleaning between each round shost no.4 through the end of break in and load work is shot on my 800 yard target. (It is actually 787 but I account for that) In most instances I can take quickload estimates as a velocity plugged into exbal and be pretty close to where I need to be. I could change velocities instead of BCs but why would I. Velocity is a much easier measurement to verify.
Now when I arrive where ever I am going to hunt is a different story. By that time I have a "working BC" that I trust and have to hope that velocity and enviromental changes can be the only causes for POA-POI differences.
The only difference with this particular rifle is a 40MOA base rather than a 20MOA base. So I have to keep coming back to that in the back of my mind. I cannot wrap my mind around what relating to the base would cause this, but do not know enough about the subject to even venture a guess. I have not shot the rifle much in the last year because of illness, and probably will not play with it again until I start getting ready to head to NM to shoot cow elk.
I am not aware of a G7 BC for this bullet but would be interested in trying it.
Why would I change a known value such as velocity to make a correction to BC. Maybe you are finding problems with BC that you are factoring out in the same manner in which I resolve mine. I have a chart around somewhere with my actual drops shot on a tall target (10 ft). I can make these drops match exbal predictions almost perfectly out to a mile using a stepped G1 BC.
Most times when I build a rifle I have the rifle sighted in within 3 shots at 100, assuming I do a good job bore sighting the rifle by looking through the bore. Even cleaning between each round shost no.4 through the end of break in and load work is shot on my 800 yard target. (It is actually 787 but I account for that) In most instances I can take quickload estimates as a velocity plugged into exbal and be pretty close to where I need to be. I could change velocities instead of BCs but why would I. Velocity is a much easier measurement to verify.
Now when I arrive where ever I am going to hunt is a different story. By that time I have a "working BC" that I trust and have to hope that velocity and enviromental changes can be the only causes for POA-POI differences.
Eddy, my NXS 5.5-22x56 has +2.5% error - which means when i dial 40clicks, im really getting 41 on the target... Ive had other scopes with upto 5% error like this.
I shoot a group @ 100, dial 100clicks up, shoot another group then measure on the target group 1 center to group 2 center. I dont bother doing the same with windage because the most wind ive ever had to dial is about 20 clicks and a few percent of this is gonna be within 1 click anyway...
I use a "custom click value" in my ballistics calculator to take this error out in my trajectory calculation- which becomes (0.1mrad*1.025) clicks. For this scope.
Eddy, have you tried adjusting your velocity instead of the BC? I dont use my chrony anymore in this regard, because IT was the source of half my problems... If you have a bullet that Litz has tested, use the exact Litz G7 derived BC, make sure all other variables are correct, including your dead on zero @ 100 for that load, ignore your chrony and adjust the VELOCITY in your calc, and see how your trajectory fits then- i bet it you will hit everything at all distances out to 1 mile...