Build a clean target line first
The calculator only works when the target point is validated first. Use active map proof, then draw one final Nest-to-target line for firing input and stop when that line is fixed. Do not place bearing and distance values into the calculator directly from spotter geometry.
Spotter values still need to be converted into a measurement from the Nest before the output can be trusted. Keep one final firing line visible while you compute, and clear secondary marks if they could be mistaken for the active target. This keeps the calculator input narrow and repeatable.
Enter range first, then charge
Open the calculator after you have final range and bearing from the same final fire line. Enter the measured target distance as the ballistic input, then choose the powder-charge count you intend to load. Keep the bearing beside the calculation because it will be transferred separately to turret traverse.
Do not imply that every displayed field changes the elevation result. The supported relationship here is measured target distance plus selected powder charge producing the required elevation. When distance or charge is not final, return to the map line and recompute before touching turret settings.
Read charge and elevation as one result
The calculator presents charge and elevation as a matched firing solution. The first charge option shown as available is the minimum that can reach the entered range, while choosing more charge changes the elevation and flight time. Read the complete result instead of copying only the elevation number.
Choose the charge you will actually load, then keep the elevation produced for that exact choice. If you change the charge after leaving the calculator, the previous elevation no longer describes the same shot. Recompute and replace the fire mission card before moving to the turret.
Use one fire mission card per target
For one target, keep one current card and ignore older cards after the solution is regenerated. A card from a previous charge value is not a valid fallback. Even when two targets have a similar range, a change to shell or charge requires a different card.
Match the card to the active selection before loading. After card generation, verify the shell type and charge count against the current order and target in one pass. If any mismatch appears, remeasure from the Nest and compute again.
Transfer bearing and elevation to turret
Apply the latest bearing and elevation pair together to the turret controls. Use one final control pass to avoid leaving either value on an older setting. If you prepare both barrels, do not apply one card to a barrel loaded for a different shell or charge.
A barrel mismatch usually means that part of the firing solution came from another setup. Perform one final visual check before loading so turret rotation, elevation, shell, and charge all match the same card. If one value is from an older cycle, cancel and regenerate the solution.
Keep clipboard and card hygiene
Clear stale entries before you begin the next cycle. A visible old value can mislead even when the current numbers are correct in the map. If the map changes after a shot and you still use old clipboard data, the next calculation starts from the wrong state.
Recreate only one active card after the latest conversion. A quick clean routine before loading reduces wrong-load errors more than any advanced optimization. Keep this routine strict during both calm phases and pressure phases.
Run one-loop correction after impact
After impact, start correction from the same controlled order: map check, conversion redraw, calculation, turret transfer, second shot. Confirm the target is still current before changing the turret. Do not begin correction by changing one turret value while keeping old range or charge data.
One hidden stale input in the loop will often make the miss worse. If multiple misses happen, verify each loop step in sequence before the third shot. When correction becomes clean, repeat the same loop structure for consistency.
Use calculator-only boundaries
This page is for in-game calculator workflow, not external formulas or fixed constants. A single number from one build should not become a universal replacement for live state. If you need manual methods for backup, use them only after repeated live-test verification.
Until then, treat them as experimental rather than the primary process. Keep calculator outputs tied to the current target and load, and keep unverified manual methods outside the normal firing cycle. That boundary prevents a fixed formula from being carried into a different mission or game build.