<- Back to field manual

TROUBLESHOOTING / IMPACT

Why Am I Overshooting?

A fault-isolation page for shots that land long, with one-change-at-a-time corrections and notes for the next attempt.

5 min read

Classify the miss before correcting

An overshoot is a symptom, not a diagnosis. Record whether the round is consistently long, only long at one range, or long after a shell change.

  • Consistently long: re-check the distance input, map scale, and elevation state.
  • Long only at one location: re-check the target reference and local measurement.
  • Long after a shell change: compare the shell requirement and the previous shot record.
  • Mixed misses: stop changing multiple inputs and rebuild the firing solution from the checklist.

Use a correction log

Write the original estimate, the observed impact, and exactly one adjustment. This makes a second shot informative and prevents a chain of untraceable changes.

Do not copy a fixed number from another build

A community answer can be a lead, but mission state, shell choice, map context, and game updates can change the result. Link the report and date your own confirmation before publishing a hard value.

FIELD NOTE

Current page status: workflow verified; universal numeric correction not claimed.

Evidence, status and related notes

STATUS

Workflow verified

Hard values need a dated test in the current build.

SOURCES / WHY-AM-I-OVERSHOOTING

Read the evidence trail.

Steam Community operator guideSteam store listing and update historyPro Game Guides beginner guide