Ballistic solvers, for those that use them.

[Stubbers]

Added bore sight / line and the option to enable/disable. No plans on going too crazy with embellishments.

Another empty slot in the bottom right corner will have to add something!

-Matt

 

[Stubbers]

And now its filled and can do SFP scopes...that didn't take long. Shown enabled here with 10 mag calibration set to 20x mag.

-Matt

 

[Revoman]

Nicely done Matt!!

mike

 

[Stubbers]

added toggles for chart and plot.

Chart look at the moment. Can adjust intervals.

-Matt

 

[Stubbers]

Weather sheet updates, include MSLP (mean sea level pressure), when checked it'll calculate pressure from altitude/temp, otherwise it assumes ambient.

Weather is updated based on City / State, latitude/longitude is based on City State (and even address if you want precision) if set to auto, hemisphere automatically detected based on latitude. Setting to 0 pretty much automates everything if you want based on local conditions for the listed city.

Changed the graph for when its set to Drop (Mil) or Drop (Moa) to show a minimum of 5 yard , as at 0 yards its infinity and you cannot reflect that visually, so now you can see a hold over slope from 5-10 or 5-20 yards depending on the interval you go with...example:

Not relevant to the ballistic solver, but modified the sheet that holds some gun data to be relational.

Sheet now holds data for 10 guns, and for each gun it holds 6 tunes, for a total of 60 tunes. The tunes are automatically loaded upon selection and saved upon any edit.

Also consolidated some random calculators included currently in the sheet:

-Matt

 

[Stubbers]

No major changes, been "Beta Testing" things such as swings in temperature and pressure to see if they track with MERO/Chairgun/Sterlok, which they do.

Also changed over from o'clock for direction to degrees.

-Matt

 

[Stubbers]

Newly added, optimal zero / battle zero / MPBR range based on kill zone, and pbr kill zone for current zero.

Also changed the UI a little.

 

[Revoman]

So, it would appear that you have duplicated virtually every aspect of the Strelok app with this last bit of kit Matt.
Nicely done.
Do you think that it might be a possibility to release it in the future at all?

mike

 

[Stubbers]

So, it would appear that you have duplicated virtually every aspect of the Strelok app with this last bit of kit Matt.
Nicely done.
Do you think that it might be a possibility to release it in the future at all?

mike

I do plan after thorough beta testing and squeezing out every last bit that I can. Trying to optimize code, debug, manage errorhandling, and all the other fun dev stuff isn't my forte, but I find it relaxing and fun when I have time for it and actually see big changes/improvements.


-Matt

 

[Paul Be Careful]

Kudos

 

[Stubbers]

Added target PBR to the data, which can be seen as range margin of error where you'll still hit target within your target killzone if the range were off.


Showing 50 vs 100 yards with 1.5" kz:

As you see, 50 yards is very forgiving, showing that if the killzone is within 36.6-56.7 yards, its dead, however, at 100 yards, very unforgiving in target ranging error, where the target must be at 98.1-101.8 yards to get within the killzone.

-Matt

 

[Stubbers]

I DID IT, I ADDED MOA RETICLE AND IT SWAPS ACCORDINGLY. (Cap locks for how thrilled I am about it!)




MOA VS MRAD

 

[Stubbers]

Added:

-Some minor UI changes
-Zero range and target distance can be inputted in yards/ft/meters
-Scope clicks units
-POA margin of error below target pbr, both determined by killzone.
-Option to Include/exclude shot direction with wind direction

-Matt

 

[Stubbers]

-Added projectile diameter to Group size expected from identical POA with fps + wind variance in mind only.
-Changed UI on range card/chart for Mil to show U/D L/R instead of - values only.

Example below

(also added chart increment and end point)

h&n 15.89 moving 630 fps 15 fps and 1 mph variance:

h&n 15.89 moving 630 fps 30 fps and 3 mph variance:

Group size expected growth is 3.44" to 7.83".


jsb mkll 33.95 moving 876 fps, 15 fps spread and 1 wind mph variance:

jsb mkll 33.95 moving 876 fps, 30 fps spread and 1 wind mph variance:

Only 1.06" expected growth from 5 to 30 fps spread. Much less than one might expect, however enough to make one appreciate the low fps spread of a finely tuned pcp.

*disclaimer, the above predicted group spread is only from the factors mentioned, wind and fps, other factors such as barrel harmonics, pellet dimensional discrepancies, ect, are not considered*

-Matt

 

[Stubbers]

Added 'Update thresholds' to update based on temp, humidity or pressure changes when set to auto. May make the threshold a user input but for now its


Pressure +/- .05 "Hg
Temp +/- 5F
Humidity +/- 10%

Before, when set to auto, the spreadsheet would check for every .1 or even 1 degree temp change, which is a bit excessive as there isn't much change in required POA below the above thresholds.



-Matt

 

[Stubbers]

Question, do I bother with multiple wind zones? Ie: wind mph 2 wind angle 300 0-30 yards. wind mph 3 wind angle 200 30-60 yards...ect?

Would be a fun challenge programmatically but I feel its probably not a function often used with current ballistic solvers that do implement this feature.


-Matt

 

[JFS737]

I'm late to this show, very cool project.... programming skills! Re: multiple wind zones, I'd say maybe yes. Why?.... consider if you have 4 mph at the muzzle for 1/3 of the way and then 0 for the rest.... it would be much different than having zero for the fist 2/3 and then 4mph for the last 1/3, no? Might be interesting, but easy for me to say!

 

[Revoman]

Matt --=--
I believe that you are hitting all of the right buttons in your quest to make this ballistic solver the best one out there.
So, with that in mind, most, if not all users are on a mobile device. Meaning that all of the information needs to be readable in various weather conditions, sun being the most difficult to see the device screen.
When finalizing your solver, that might be something to consider. Strelok for instance has a tough to read screen in the sun (SoCal).
Perhaps make a few screen colorization options or simply make it readable under most weather conditions.

mike

 

[Ballisticboy]

Question, do I bother with multiple wind zones? Ie: wind mph 2 wind angle 300 0-30 yards. wind mph 3 wind angle 200 30-60 yards...ect?

Would be a fun challenge programmatically but I feel its probably not a function often used with current ballistic solvers that do implement this feature.


-Matt

I added multiple wind profiles to the point mass model I used. It was simple to do and only took a couple of extra lines to calculate the wind at the start of each time step based on the range at the previous step. It is very useful if you want to see the relative effects of wind at different ranges. It was more of a problem to create the additional lines for the extra input data.

 

[Stubbers]

I added multiple wind profiles to the point mass model I used. It was simple to do and only took a couple of extra lines to calculate the wind at the start of each time step based on the range at the previous step. It is very useful if you want to see the relative effects of wind at different ranges. It was more of a problem to create the additional lines for the extra input data.

I just don't see most users taking the time to input that data so I feel it would be an unused feature, I know I would never bother.

I would agree its more of an issue to deal with on the front end than the back, as I have no efficient means to have the wind profile inputted.

The equipment needed to get multiple wind speeds and angles accurately enough at multiple distances to be fruitful with ballistic solver ouputs is...beyond 99.999% of the shooters that will use a solver to calculate dope.

MERO and Sterlok both exclude this from their solver, and I likely will follow their path.

-Matt