Set positions in Fieldkit
- Select the appropriate map and activate mortar placement. Click your position or enter X/Y coordinates.
- Select target placement and choose a target. Compare both markers with your intended positions.
- Hold the right mouse button to pan; the bottom-right plus and minus buttons control zoom. These actions do not place new points.
- Fit positions brings both markers into view. Lock the mortar position if it should remain unchanged while planning.
Understand the three outputs
Distance is the separation between your entered points. Azimuth is the direction to the target; MIL is the elevation interpolated from the tool’s stored L81 table. The planner uses east-positive X and north-positive Y. Its calibration assigns 100 meters to one coordinate unit. These are documented assumptions of our tool.
SPH-2 with low and high trajectories
Use “Weapon” to switch between the L81 mortar (132–684 m) and the SPH-2 (780–2629 m). The SPH-2 returns two solutions: the low trajectory with small MIL values and the high trajectory with large ones. Both come from the stored community firing table for equal elevation. Between 780 and roughly 1180 metres only the high solution exists. Park the vehicle as level as possible before firing: tilt changes the actual range and the tool does not model vehicle attitude.
Adjust fire after the first impact
- Observe the impact and estimate the miss in metres as seen from the gun: short or long, left or right.
- Enter the metres under “Adjust fire” and choose Add, Drop, Left or Right. The target moves by that amount along or across the firing line; distance, azimuth and MIL are recalculated immediately.
- Alternatively choose “Mark impact on map” and click the impact, or paste its coordinates. The target is shifted by the observed miss in the opposite direction.
- Every correction can be reverted with “Undo”. Coordinates from squad chat in the “x80.00, y70.00” format are applied with “Paste”.
Why an output may be unavailable
Empty or invalid coordinates do not produce a solution. The planner also stops outside its stored table range of 132 to 684 meters. Height differences and flight time are not fully modeled. A displayed value therefore does not guarantee a hit; observe results in-game and check the map version and coordinates.
Share a clearly identified deployment
Give saved plans distinct names and check the map and markers before sharing. A plan link contains positions in its URL fragment. Anyone with the complete link can read them. Shared plans do not automatically update when a target or your position later changes.
Frequently asked questions
Why can I not calculate any distance?
The planner only interpolates within its stored community table. Outside that range, supported reference points are missing; extrapolating would imply evidence that the tool does not have.