I'm getting frustrated. I would like some feedback on this idea, but after posting this on another forum got practically zero response. Let me give it a shot here.
There are a couple of companies that have ballistic software on a PDA for use in the field. I bought the Horus product but found various drawbacks and decided to write my own. The problem I had with the Horus was that the firing solution was simply in terms of MOA. What if you wanted a MIL solution? What if you wanted the solution in terms of your particular scope turret?
This is a screen shot of a 1000 yd. solution where wind is at 4 mph from 220 degs and the target is moving at 3 mph at 80 degs relative to the shooter. The solution shows windage in both MOA and MILS, a lead MIL value (which deals with the target's motion) and a "Holdoff" value with combines both windage and target lead.
Note that in the window labled "Turret" is the result "33 - 2". This is the elevation correction of 29.1 MOA in terms of my particular scope turret: turn the turret to "33", then back off two clicks. The reason that this readout is valuable is that on my particular scope, although each click is supposed to equal 0.500 MOA, in fact each click equals 0.451 MOA. So the turret readout converts the elevation correction to my turret scale at a rate of 0.451 clicks per MOA and then tells me what the setting is based upon the scale on my turret knob. This firing solution is based upon the following preset values:
By way of another example, lets say that I put another scope on my rifle and this scope has a BCD that is set up for a .308 Win, 168 gr. bullet. From the setup, you can see that I am shooting something more akin to a 300 WM (actually, a 300 WSM
.) Usually, a BDC for the wrong bullet is useless. However, in this screen shot I have had the program output the turret information in terms of the .308 BDC scale.
The program is telling me to set BDC on '900' then back it off three clicks. So, even though I've got the wrong BDC, the program can still use the scale for a different bullet and muzzle velocity.
I'd like any feedback you guys may have concerning this type of output and your thoughts as to how usable this program might be.
[ 10-22-2003: Message edited by: Blaine Fields ]