Dead Reckoning is officially associated with Trust Dead Reckoning and the gold award Quiet Precision. Trust should mean a traceable chain of evidence, not blind confidence in one approximate map mark. Preserve how every point was derived.
2950790, Windows public 1.0, checked 2026-08-09. This page avoids invented coordinates, hidden inputs, and medal thresholds.Write provenance beside each mark
For every point or line, record dispatch page, origin, bearing/range type, and time. Distinguish direct known positions from derived intersections and predictions. If the operation supplies incomplete data, label uncertainty rather than hiding it.
This record lets you return to the one assumption behind a miss.
Choose among candidate positions
Two circles or a bearing/range can create multiple intersections. Use map context, target description, later intelligence, or reconnaissance to eliminate alternatives. Do not choose the point closest to a familiar feature without support.
If clues conflict, recheck origin and measurement meaning. Averaging them produces false precision.
Derive the gun solution separately
Once the target candidate is credible, draw a new line from the Nest origin. Copy bearing/range into a card, calculate with the selected shell and charge count, then load the same barrel described by the card.
Check actual powder and reread fine bearing/elevation after releasing controls. The derivation is only as strong as its final transfer.
Use impact as another observation
After firing, mark the impact without erasing the target. Classify direction, range, effect, or state. If uncertainty in target position was large, a miss may refine the estimate; if the target was strong, inspect load/aim first.
Change one input and note why. A quiet methodical correction fits the operation better than an undocumented salvo.
When the mission seems to demand guessing
Search for unread teleprinter output, a map legend clue, a reference point, or an available recon ability. Re-read whether the value was from the observer or to the observer. Confirm message order.
Use current community discussion as a lead only after matching public version and mission stage. Demo geometry is not base-game proof.
Quiet Precision research
The gold title suggests a theme but not a formula. Capture medal text after normal completion. Test accuracy, number of corrections, assistance, requisition, and time separately.
Keep the provenance map with the result. It proves that a low-shot solution came from replicable reasoning rather than a memorized spoiler coordinate.
Preserve the ending state
Read and dismiss the newspaper and allow saving. If a crash leads to mission-entry failure, update to PATCH 1.0 (1558) and verify files. Do not manually clear a profile.
For a report, include all clue origins, candidate selection, final card, impact, response, and patch. Redact or label exact coordinates as spoilers.
Score the strength of a solution
Give each candidate one point for every independent compatible clue and note any contradiction. Independence matters: two marks derived from the same dispatch are not two confirmations. Map context can break a tie, but label that judgment separately from measured evidence.
Before firing, state what future observation would disprove the chosen point. This makes the test falsifiable. If impact feedback contradicts the position, return to the weakest assumption instead of protecting the initial choice. If it supports the point, increase confidence but do not erase alternative evidence until the mission confirms the target. This practice is especially helpful when comparing community routes, because it reveals whether another operator solved the intelligence or simply knew a coordinate in advance.
At the end of the run, archive the original clues alongside the result rather than only the final target point. Another player should be able to reconstruct why the point was chosen without seeing your screen. If a later patch changes one clue, the derivation reveals exactly which conclusion needs revision. A coordinate-only guide offers no such maintenance path and can send players to the wrong location while appearing precise.