Forums
New posts
Search forums
What's new
Articles
Latest reviews
Author list
Classifieds
Log in
Register
What's new
Search
Search
Search titles and first posts only
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Rifles, Reloading, Optics, Equipment
Rifles, Bullets, Barrels & Ballistics
New Nightforce Ballistic Program......Trajectory Validation.....Help Please.
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="SBruce" data-source="post: 439249" data-attributes="member: 21068"><p><strong>Thanks for the link, sending them an e-mail right now.</strong></p><p> </p><p><strong>Here it is:</strong></p><p> </p><p>Hello,</p><p> </p><p>I've had this PC version of your software for approx. a year now. I really enjoy it and have been able to figure out and use most every part of it exept one.</p><p> </p><p> TRAJECTORY VALIDATION...............It simply doesn't work on my program! </p><p></p><p>I've used the same feature on an older PPC version and it changed the velocity to match drops....quite easy to understand and use. However, when I type the same exact data into the new PC version it always says "calculations did not converge".......no matter how many times I try or what numbers I input, always the same popup??</p><p> </p><p>The pocket PC version has a spot to click moa or mill or IPHY, ect. On my PC version they are greyed out and unable to change anything. Also, when I input a distance and then hit TAB.....it automatically enters a bogus number into "sight adjustment used" ( like 54.5 moa) and takes my curser down to the next distance box. I can change the number in the adjustment box and then type in the "measured error", but these are not things that I remember happening with the PPC version.</p><p> </p><p>With these issues, it's easier to just play with the velocity until I get the program to match my actual field drops. I am pretty sure this isn't how you designed it to be however, and I am wondering if there is a patch or update that will solve the problem?</p><p></p><p>I click "trajectory validation" option</p><p>I enter a distance (example: 700 yds)</p><p>I enter an amount under <em>sight adj used</em> (same amount the program gives for comeup, example: 12.5 moa)</p><p>I enter a number under <em>amount of measured error</em> (Example: 4 inches) </p><p>I click calculate. . . . . . . . . . . . . . . .Assuming I am doing it correctly.</p><p> </p><p>Thank You in advance for any help on this issue.</p><p></p><p><strong>Hopefully I'll get a response back soon.</strong></p></blockquote><p></p>
[QUOTE="SBruce, post: 439249, member: 21068"] [B]Thanks for the link, sending them an e-mail right now.[/B] [B]Here it is:[/B] Hello, I've had this PC version of your software for approx. a year now. I really enjoy it and have been able to figure out and use most every part of it exept one. TRAJECTORY VALIDATION...............It simply doesn't work on my program! I've used the same feature on an older PPC version and it changed the velocity to match drops....quite easy to understand and use. However, when I type the same exact data into the new PC version it always says "calculations did not converge".......no matter how many times I try or what numbers I input, always the same popup?? The pocket PC version has a spot to click moa or mill or IPHY, ect. On my PC version they are greyed out and unable to change anything. Also, when I input a distance and then hit TAB.....it automatically enters a bogus number into "sight adjustment used" ( like 54.5 moa) and takes my curser down to the next distance box. I can change the number in the adjustment box and then type in the "measured error", but these are not things that I remember happening with the PPC version. With these issues, it's easier to just play with the velocity until I get the program to match my actual field drops. I am pretty sure this isn't how you designed it to be however, and I am wondering if there is a patch or update that will solve the problem? I click "trajectory validation" option I enter a distance (example: 700 yds) I enter an amount under [I]sight adj used[/I] (same amount the program gives for comeup, example: 12.5 moa) I enter a number under [I]amount of measured error[/I] (Example: 4 inches) I click calculate. . . . . . . . . . . . . . . .Assuming I am doing it correctly. Thank You in advance for any help on this issue. [B]Hopefully I'll get a response back soon.[/B] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Rifles, Reloading, Optics, Equipment
Rifles, Bullets, Barrels & Ballistics
New Nightforce Ballistic Program......Trajectory Validation.....Help Please.
Top