Jim Poulette
NES Member
I just started using this, mostly to compare some of the chrono data I've accumulated with potential GRT results. Generally I like the interface.
One hitch: I know the physical difference between "barrel length" and "projectile path" - but does anyone know what exactly the relationship is in this software?
Example - using my 629, with a 2.625" barrel, if I enter 2.625" as the barrel length I lose about 100-150 fps of velocity and the results do not agree with my measurements.
If I change the barrel length to an arbitrary dimension that changes the projectile path to 2.625" - the numbers match almost perfectly. (Only the barrel length is a variable in GRT - the projectile path is derived)
I will post to Discord - but I was wondering if anyone has experience with this. Simple solution I suspect is to make a custom database item (".44 mag, 629, w/2.625", or something like that) so maybe that's the answer. Or maybe there's a software 'switch' somewhere I don't know about.
Entries on the left is a good match to my chrono data - entries on the right are WAY off. This mismatch is present in the 4 separate data sets I've attempted.
One hitch: I know the physical difference between "barrel length" and "projectile path" - but does anyone know what exactly the relationship is in this software?
Example - using my 629, with a 2.625" barrel, if I enter 2.625" as the barrel length I lose about 100-150 fps of velocity and the results do not agree with my measurements.
If I change the barrel length to an arbitrary dimension that changes the projectile path to 2.625" - the numbers match almost perfectly. (Only the barrel length is a variable in GRT - the projectile path is derived)
I will post to Discord - but I was wondering if anyone has experience with this. Simple solution I suspect is to make a custom database item (".44 mag, 629, w/2.625", or something like that) so maybe that's the answer. Or maybe there's a software 'switch' somewhere I don't know about.
Entries on the left is a good match to my chrono data - entries on the right are WAY off. This mismatch is present in the 4 separate data sets I've attempted.