One of our guys was having some issues yesterday with AB Mobile for IOS. He downloaded the app, set up his rifle (2" Ht. over bore, mil/mil, 2536 fps MV measured with Oehler 35P); he's shooting 175 gr. Black Hills red box so we used the 175 SMK from the bullet library as the drag model. Looking at the data from the drag model, it stated a BC of 0.243 (which is the same as the 2500 fps G7 for that projectile from the bullet library in the book). When we pulled up the trajectory table, the firing solutions were WAY off (8.4 mils at 1000 yds.). Looking at remaining velocity, the program thought there should be over 1600 fps at 1000 yds (not realistic for a 20" .308) We fired on targets at known distances from 100-1000 yds in 100 yard increments and arrived at a firing solution of 11.7 mils at 1000 yds. So we trued MV at 1000 yards and the app gave us a new MV of around 2217 fps (again not a realistic solution given the gun and ammo), and looked at the drop table, the predicted come-ups for intermediate ranges were WAY off (like 1-2 mils off in either direction).
We used identical inputs to build the same profile in AB Mobile for Android, and built a control profile in ATRAG using a G1 of .470, and both of those platforms gave us close algorithms that only needed to be trued by less than a mil and resulted in accurate tables from 100-1000 yds.
Bottom Line: Is there a problem with AB Mobile on IOS that could be generating this issue?
Sorry for the info dump, thanks for your help!