![]() ![]() I thought the number I was to enter on the correction distance was how much the shot was off from where Strelok Pro said it should be. I realize 1.8 inches is not close to 12.5 inches, but here's where it becomes apparent this was, as it often is, pure user error. I was just trying to put in something close, but off enough it would cause a different BC to be calculated so I would know it was working. However, if I entered 12.5 inches like CC mentioned, it DID properly calculate and return a new "trued" BC.ģ) CC asked where I got 1.8 inches. For instance, When zeroed at 50 yards, and truing the BC for 100 yards, when I entered either +/- 1.8 inches, it simply returned 0.000 for the new BC. ![]() It was actually the use of the Multi-BC function that was "nonstandard" and causing the error message I was getting, not the use of the GA Drag Function.Ģ) There appears to be useful data tolerances in place that prevent a proper calculation if the data entered is too far from anything realistically useful. like CC said, you can't use Multi-BC when using the Truing Function. at least a few things going on that made things puke.ġ) First and foremost. I am not seeing what is not right, but it appears just using the GA drag function should not prevent this from working. I also zero at 50 yards, and entered 100 yards for my distance to true, then for testing purposes, I use both +/- 1.8 inches in the elevation window, and I get no correction calculated. If I change it to Single BC mode, I don't get the error message, but I just get a BC of 0.000 showing after I hit calculate. When I'm configured to use Multi-BC, and I try to true it up, I get the error message I quoted above. It makes me think I've got something else configured wrong. ![]() It also bothers me that others seem to be able to use the Truing function with the GA drag function, whereas I can't. As soon as I ran the same data through Chairgun's calculator and came up with more realistic BCs, I knew there had to be a difference that I wasn't aware of. Until I started suspecting my BCs were low, I had no idea there was a difference between the BC calculators. Until today, I was using the lower BC values calculated from the generic BC calculators on all the airgun websites. Yeah, I think the ones calculated with Chairgun using the GA drag function are good. 30 cal 44.75 gr shot to 50 yds):ĭistance Velocity (fps) Pyramyd BC Chairgun BC I would assume if one is using the GA drag function in Strelok Pro, when determining your actual BC data, you should definitely use the BC calculator in Chairgun with the same GA drag function selected? To do otherwise seems to introduce error into Strelok Pro. So, my question is, do the other BC calculators on airgun sites not us the GA drag law, and therefore they are calculating much lower BC(s) using the same distance data? Chairgun also indicated in the BC calculator it was using the GA drag law. I went into the Chairgun app and calculated my BC(s), and they were much higher. In thinking about this, I remembered that Strelok Pro indicated the GA drag law was from Chairgun. I'm using the Airgun Drag Function (GA) offered in Strelok Pro. I've felt the BCs I've been getting were on the low side, so I tried to use the Truing Function in Strelok Pro, but it displayed an error message, indicating I could not true the BC when a non-standard drag function is used. I've been using the Pyramyd Air BC calculator and determining my actual BC(s). This provides good velocity data for the BC calculators on Pyramyd Air, AoA, etc. I've been using a LabRadar to collect velocity data at different distances. ![]()
0 Comments
Leave a Reply. |