How to Triangulate
Triangulation turns two directional reports into one estimated position. Accuracy depends less on complicated math than on using the correct origin for each report and drawing both bearings in the correct direction.
What triangulation solves
A single directional report describes a line, not a unique point. A second report from a different known position creates another line. Their intersection is the estimated unknown position.
Translate each report literally
For every message, record three things: who or what occupies the known origin, what unknown object the bearing describes, and the stated direction. Do not combine two reports until both describe the same unknown object.
Plot the intersection
Work carefully and keep every report tied to its own origin. Small errors grow when the lines meet at a shallow angle.
- Place the first known reporting position.
- Draw its reported bearing outward in the correct direction.
- Place the second known reporting position.
- Draw the second bearing.
- Mark the crossing point as estimated, not confirmed.
- Use later messages or recon to validate it before spending scarce ammunition.
Check the geometry before firing
A strong intersection uses lines that cross cleanly and lands in a plausible area. Nearly parallel lines magnify tiny drawing errors. If the result lies far outside the described region, first test whether a bearing was reversed by 180 degrees or a report was started from the wrong marker.
Common failure points
The four recurring mistakes are reversing a bearing, measuring from the NEST when the report originated elsewhere, mixing observer and battery reports, and measuring the final shot before updating a moved NEST marker. A convincing intersection can still be false, so preserve the source label beside every line.
Sources & verification
Mechanics can change after patches. Official references and clearly labeled community findings used for this guide:
Official Steam page ↗Community beginner discussion and examples ↗