Bought a new Bushnell 3.5-21x50GZA in FDE for my 260 Imp 30* late last fall, and finally got around to shooting a box with it last evening. I put a couple of rounds into the X-ring on the reduced SR-21C to confirm my 100yd zero, then moved 1 mil right, 1 mil up, (would've gone 2 mils up, but that'd have taken me off the repair center), 2 mils back left, 1 mil down, and finally 1 mil right, back to original 100yd zero, firing one shot after each adjustment. Scope returned to original zero pretty well, no issue there. But, the two shots fired at 1 mil above the 100yd zero both measured 4-1/8" high, instead of the expected 3.4".
These results go a long way towards explaining why I consistently get groups 4.5"-5" above the aiming point at 600 when I use the 3.5 mil come-up both Shooter & Applied Ballistics calls for with 123s. I've been over this issue at least twice, starting out by confirming my 100yd zero while shooting over the chrono, then using this fresh/real-time velocity data when inputting data for the 600yd come-up. I've got a Kestrel 4500NV, and typically use it so my wind inputs are more than just a SWAG. And we checked my CED M2 chrono against a friend's MagnetoSpeed last August, getting velocity readings out of the M2 that were consistently 4-6fps lower than the MS's output.
We've got a practical steel match coming up in a week, so there's not enough time to get in touch with Bushnell's service dept, get the scope sent in & get it back. If I could get out on a day with decent conditions to double check these results, as well as check it out at 1000yds, I could do the math and come up with a conversion factor. But one of the main reasons I went with the FFP G2DMR reticle in a mil/mil scope was to minimize the amount of mental math while on the line. Has anyone else had this sort of problem with their HDMR or GZA scopes? If so, was Bushnell able to fix it, or replace your scope?
These results go a long way towards explaining why I consistently get groups 4.5"-5" above the aiming point at 600 when I use the 3.5 mil come-up both Shooter & Applied Ballistics calls for with 123s. I've been over this issue at least twice, starting out by confirming my 100yd zero while shooting over the chrono, then using this fresh/real-time velocity data when inputting data for the 600yd come-up. I've got a Kestrel 4500NV, and typically use it so my wind inputs are more than just a SWAG. And we checked my CED M2 chrono against a friend's MagnetoSpeed last August, getting velocity readings out of the M2 that were consistently 4-6fps lower than the MS's output.
We've got a practical steel match coming up in a week, so there's not enough time to get in touch with Bushnell's service dept, get the scope sent in & get it back. If I could get out on a day with decent conditions to double check these results, as well as check it out at 1000yds, I could do the math and come up with a conversion factor. But one of the main reasons I went with the FFP G2DMR reticle in a mil/mil scope was to minimize the amount of mental math while on the line. Has anyone else had this sort of problem with their HDMR or GZA scopes? If so, was Bushnell able to fix it, or replace your scope?