Hi folks.... anybody heard anything about the (supposedly incoming) new Android version of the venerable FFS ballistic software/app? Thanks
Field Firing Solution (FFS) new Android release?
- Thread starter overspin67
- Start date
I actually have a working version in alpha test right now. Trying to work out the BT protocols for LRF's and the Kestrel.
Some screen shots of the work in progress
So quick follow up question is this only being created and formatted to fit on a phone size screen or will it work on one of the Samsung pad sized devices?
Long term we want it to be screen agnostic. Right now, the target test device is a Nautiz X81, a field rugged handheld.
Certainly future versions will take some advantage of the options available, but the initial release will follow the original program for familiarity. The reality is a field ballistics program is just some numbers in and some numbers out. Look at the success of the Kestrels with ballistics, the worst user interface possible, but still quite functional.I think that being targeted to run on Android devices, the UI should be revamped a lot to fit the modern designs and at the same time taking advantage of the current UI paradigms. Honestly, refactoring the old FFS won't cut the deal. Still looks like an obsolete DOS
Your right regarding Kestrel. It's an unfathomable mystery why nobody enters this market with a XXI century design. IMHO they are, somehow, begging for a new player to take over their place. Won't be hard to tackle, just a matter of time. For instance, CB for Android is way different in terms of the UI compared to their old Windows Mobile version and yet very functional, indeed much easier to use.
I
I'm a Windows guy, been using and programming it since the beta. I'm finding programming for Android a HUGE shift, and I don't begin to understand all the UI options.
I want a UI that lets me select a platform, enter the environment, then present a page with the relevant data for the shot. All other functions should be layered behind that. I have no use for graphical representations of reticle holds, nor graphs of the trajectory or stuff like that. I don't need a map view of targets, a list with range and azimuth is plenty. As a rule, fancy and flashy just get in the way when working.
I always found the Windows CB software very difficult to use in the field, very klutzy UI for me.
I'm a Windows guy, been using and programming it since the beta. I'm finding programming for Android a HUGE shift, and I don't begin to understand all the UI options.
I want a UI that lets me select a platform, enter the environment, then present a page with the relevant data for the shot. All other functions should be layered behind that. I have no use for graphical representations of reticle holds, nor graphs of the trajectory or stuff like that. I don't need a map view of targets, a list with range and azimuth is plenty. As a rule, fancy and flashy just get in the way when working.
The above being said, if there are any Android UI experts out there that would like to contribute ideas on the UI, feel free to send me notes or sample files. The project is currently Xamarin Forms, as we had some issues with MAUI.
UI elements like mapping, reticles, graphs, etc are basically dictated by the market. Not necessarily useful or needed by most people, but sought after by some guys because it looks neat and "powerful" Of all of these, the only ome I'd ever care about is mapping.
Would be very interesting if you can do a comparison between FFS and Hornady 4DOF. You know, the BC vs Drag they are always hammering all the time, most especially say at 1 mile and beyond.
Last edited:
I have 4DOF, and if they are both tuned to the load and rifle they are within .05 mil and 10fps to 2300, which is my nominal test range limit.
Nice, question is which one is harder to tune, for instance, when using Hornady bullets? What BC values should be use when running FFS?
It's more or less the same. If possible on 4DOF, use the 4DOF calculator and the custom drag models, then at 3/4 or so of max SS adjust the Axial Form Factor is need be. Otherwise the standard G1/G7 calculator is tuned like anything else.
With FFS, we use G1 and then make long range adjustments using the DK, or deceleration constant.
For ELR shooting, it's very handy to get downrange velocities, but otherwise it's important to get a group and proper correction to POA, so shooting paper, or a clean plate where you can go downrange with a ruler is important. That's why I use the Shotmarkers. they give very precise shot placement data AND target velocity. Makes setup easy.
With FFS, we use G1 and then make long range adjustments using the DK, or deceleration constant.
For ELR shooting, it's very handy to get downrange velocities, but otherwise it's important to get a group and proper correction to POA, so shooting paper, or a clean plate where you can go downrange with a ruler is important. That's why I use the Shotmarkers. they give very precise shot placement data AND target velocity. Makes setup easy.
Very useful tips thanks! Regarding the G1 value, which one to use with Hornady? I mean they publish 3 values for different velocities. I guess a ShotMarket will be ordered soon. Basically you have debunked what they say about the never ending BC vs Drag BS given your results at 2300
The G1 from your muzzle velocity range is the starting point. You may need to alter that by a few percent after you find velocity /drop at range.
Is the "CB for Android" released to the public yet? Got rid of my Android device awhile back.
Thanks.
You should contact Patagonia about the latest details, but yes, it's up and running.
OK, import of a KML file for targets and FFP's in now on the list. That should allow for integration to ATAK or Google Earth for targeting.
Similar threads
