TRASOL Is Messed Up

GatorMD97

Precisely Inaccurate
Minuteman
Dec 10, 2017
19
9
Thomasville, GA
I’m in the process of comparing ballistic calculators and TRASOL is giving messed up data at every 100 yard interval range . I have triple checked the inputs and even deleted the program and reinstalled and recreated the profile. Any thoughts, all the other programs I’m testing correlate well but in the past I’ve had better results with TRASOL past 800 yards. Pics of the 200 yard range and my build attached.

BADEC966-C8CB-4F64-A425-0622E9A51105.png
27E9EEFC-E49B-4E64-99EA-4B1ECD43B51F.png
 
Not trying to match anything but my actual dope but I am comparing to AB. Every hundred yards the election goes crazy. Literally at every 100 yard increment. See the picture above where the elevation at 200 is 2.38 MOA up and then at 205 it’s 1.34 up that’s crazy.
 
  • Like
Reactions: LastShot300
Yep I see it now.... You goofed mine up too! It only does it for me at 200 and 300 yards. Further out it looks fine. If I recall correctly there was something about this in the Official Trasol Thread. I hadn't noticed this before as I hardly use the table function.
 
  • Like
Reactions: LastShot300
Ok I ran the numbers again on CB and the "jump" is not there, so this is clearly TRASOL not the engine. I wrote about the same issue time back at the official thread. Don't know if they fixed it or not though.
 
  • Like
Reactions: GatorMD97
I just read the explanation of the "jump" in the data curve and it amazes me that it's almost dismissed as a non-issue/artifact.

If I expected a center hit on a small to target, looked for solution at 205 (just taking software at face value after truing), dialing 1.3MOA vs 2.4 MOA is a significant issue. Shooting a 3MOA target and aiming center, leaves 1.5MOA max for low shot. If gun is +-.5moa POI from POA, that could result in a miss of nearly 1.6MOA low (solution off by 1.1 MOA + gun precision of .5moa = 1.6MOA low) which would completely miss target.

Hopefully they are working to correct it with a better algorithm or better way to "proof" data before presenting dialing solution.
 
Last edited: