Lock a live objective before compute
Start from the active mission objective and verify that your current target candidate matches it. Build target geometry only for that candidate and keep it visible until you finish the calculate, load, and fire checks. Treat this as the only shot being prepared, and do not mix it with older objectives.
Build target point then remeasure from IRON NEST
Use report and spotter geometry to define a stable candidate point first. Report and spotter values belong to their named origins, while turret firing geometry must use a fresh IRON NEST-to-target line. Any candidate sent to the calculator must match the current objective and active reports.
Draw the final red line from IRON NEST to the candidate only after that candidate is verified. Keep bearing and range as a linked pair from this one line. If the candidate drifts after the last command update, redraw the red line before any compute action.
Avoid using an old spotter line as if it were the turret line, because stale geometry will poison the result. A stale red line causes every downstream output to be stale even when it looks precise. The same red line must be your only active geometry before compute.
Set the load plan before opening compute
Choose the shell for the active target and choose the powder-charge count before opening the ballistic workflow. Keep both in the shot plan, while recognizing that the supported elevation relationship on this page is target distance plus selected charge. Keep the map bearing separately because it controls traverse.
The same target distance can need a different elevation when the charge changes. The charge plan must therefore stay fixed while you read one result card. If the selected charge changes, recalculate from the same current red line.
A shell change can still invalidate the operational shot plan even when this guide does not claim it changes the elevation math. Recheck the target role, shell, charge, bearing, and computed elevation together before loading. Recompute immediately whenever distance or powder charge changes.
Turn final range and load into elevation and flight time
Open the ballistic screen and enter the live red-line distance, then select the powder-charge count. Read back elevation and flight time from that distance-and-charge result before touching turret controls. Keep the red line, selected shell, and charge plan synchronized at all times.
Use this same card as your active baseline until any measured or load value changes. The card output is a full current-cycle setup, not just elevation. Use both elevation and flight time to compare before you rotate and set barrel inputs.
If one part of the input stack changes later, treat the previous output as obsolete and return to the compute screen. Then re-open the same card path and rebuild with one live chain. A mixed stack is the common reason a corrected shell still misses.
Match turret settings to the same card
Transfer the live card values to the turret and keep the setup grouped as one package. Do not compare only elevation across different cards and assume the rest still applies. Range and load context must remain identical from card to turret.
After loading begins, hold to the current cycle state and avoid opening a second card for a different setup. If an accidental mismatch appears, halt before firing and recompute from the same final line. This prevents stale values from surviving into a live barrel input.
Your correction sequence should be map check first, then card verification, then turret settings. This keeps one consistent firing solution instead of two competing sets of values. If they diverge, stop and rebuild the solution before continuing.
When a miss happens, restart from the map
A miss should first trigger a map check, not a turret-only micro-correction. Confirm the active target candidate, active red line, shell, and charge still match the current run state. This check should happen before any turret value touch after every miss.
If any part changed, redraw the candidate point if needed, remeasure from IRON NEST, and recompute before touching turret values again. A clean rebuild can remove three-cycle confusion from one pass. Rebuilding from first principles removes hidden carry-over from old context.
The cycle is often shorter this way than tuning offsets across several rounds. Use map-based correction first, then card verification, then turret update. This order keeps every change tied to the current target and load.
Keep a single live state, not a fixed formula
Treat any fixed formula from one test as a temporary baseline only. Conditions in the current game state can shift, so elevation should be read from the current input and setup, not copied from a screenshot. Do not build fixed offsets from one captured shot.
Do not treat one-shot solutions as universal answers. Keep your records together: target point, red-line range, shell, and charge, then recompute. This approach stays useful across changes without hardcoded, stale values.
Verify compute timing and post-fire comparison
After firing, use impact and timing feedback to confirm that map, compute, and turret states stayed aligned. If impact is on-shift, the correction loop starts with rerunning the live chain, not by guessing an offset. When your feedback is clean, keep the next cycle on the same sequence.
If the feedback is unclear, discard the old assumptions and rebuild the target from the map before computing again. The sequence is short: confirm the candidate, draw a fresh red line, compute, load, then check the result. This prevents one bad correction from carrying into the next shot.