Skip to content

Over-travel hold: dial max clicks and hold the remainder on the reticle - #8

Merged
zxpower merged 1 commit into
mainfrom
fix_for_holdover
Nov 16, 2026
Merged

zxpower merged 1 commit into
mainfrom
fix_for_holdover

Conversation

@zxpower

@zxpower zxpower commented Nov 16, 2026

Copy link
Copy Markdown
Owner

What

When elevation needs more clicks than the turret has (Total elevation clicks is set and exceeded), the results now show the max clicks to dial plus how much to hold over on the reticle, instead of a click count you can't reach.

Changes

  • Trajectory & Targets tables
    • Elev clk shows the max dialable clicks, e.g. 100 (1t 0m+0) ⚠ max.
    • New Over hold MOA/MRAD column with the remainder to hold over. It's – for rows that fit on the turret, and only appears when at least one row runs out of travel.
    • Note under the table explains how to read it.
  • Phone view: cards show dial UP 100 (…) ⚠ max + hold over 1.12 MOA.
  • Turret tab: the result shows 100 clicks (max) and ⚠ needs N clicks, turret has 100 — dial max and hold over X MOA.
  • SFP: the hold-over is rescaled to the shooting magnification, like the other hold values.

Formula

hold over = (true drop angle − total clicks × click value) × SFP zoom factor (shooting zoom ÷ true zoom)

Example: a 100-click 1/8 MOA turret has 12.5 MOA of travel. At 500 m with a 13.62 MOA drop, dial 100 clicks and hold over 1.12 MOA (0.56 MOA on an SFP at 20× when true at 40×).

Tests

node test.js: 70 passed. A new test covers the over-travel hold for FFP and SFP, a drop that fits on the turret, and no limit set.

@zxpower zxpower self-assigned this Nov 16, 2026
@zxpower
zxpower merged commit 13020c1 into main Nov 16, 2026
2 checks passed
@zxpower
zxpower deleted the fix_for_holdover branch November 16, 2026 09:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant