For IRON NEST: Heavy Turret Simulator public 1.0, several independent current Steam Community guides report the same manual starting relation: elevation in degrees ≈ distance in metres × 0.012 ÷ charge count. Equivalently, one charge covers about 83.33 metres per degree, and each additional charge multiplies that distance-per-degree value. Use it to obtain a first shot, then correct from the observed impact.
2950790 through PATCH 1.0 (1577). It does not encode height difference, shell-specific drag, weather, map-reading error, or a future balance change. Record live results before treating any row as precise.Quick charge table
The maximum column is a mathematical consequence of the reported 60-degree/5-kilometre-per-charge model, not a promise that every shell, operation, or height difference reaches that point. Read “about” literally.
Calculate a starting elevation
Use either form:
Elevation = distance × 0.012 ÷ charges
or
Elevation = distance ÷ metres-per-degree row
For a target at 6,000 metres with two charges:
- 6,000 × 0.012 ÷ 2 = 36 degrees;
- or 6,000 ÷ 166.67 ≈ 36 degrees.
For a target at 9,000 metres with three charges:
- 9,000 × 0.012 ÷ 3 = 36 degrees.
The repeated angle is expected because both examples use the same distance per charge. Set the bearing independently; the table does not solve azimuth.
Pick the charge count
Choose a count that places the calculated elevation within the gun’s usable current range and gives room to correct. Very low angles can make small elevation-reading errors significant, while a count that pushes the estimate beyond the mechanism’s range is unusable. The community model centres maximum distance near 60 degrees, but the game may impose operation or ammunition constraints you must read live.
Before loading, check the selected shell, available charges, target range, and whether the current objective permits a spotting shot. If the shell cannot be unloaded after commitment in the current mechanism, a hurried charge choice has a real cost. The Loading guide owns recovery for a wrong load.
Build a real firing record
The table above is a starting layer. Turn it into reliable local data by recording every shot in a consistent card:
Do not merge records with different unknown shell types, different origins, or different patches into one “exact” row. A table with fewer clean samples is better than a large false-precision database.
Correct from the impact
If the impact is short or over but left/right is sound, keep bearing stable and change elevation in one controlled step. If the impact is left or right at the right range, correct bearing. If both axes are wrong, first confirm origin, range, and scale; a plotting error can be larger than the ballistic correction.
Record the original setting and correction. A successful second shot does not retroactively prove the first estimate was exact—it proves the estimate plus observed correction worked for that shot state. Use the Shot Corrections guide for the complete loop.
Use the table when the calculator is broken
- Confirm the Nest’s current origin on the tactical map.
- Plot the target and measure bearing and distance.
- Select a charge count and calculate the starting elevation.
- Set bearing and elevation on the physical controls.
- Fire only when the objective permits a test or the solution is good enough.
- Read the impact, make one correction, and write it down.
PATCH 1.0 (1577) fixed turret position and movement not resetting between missions. Update before using inherited coordinates from an old replay. If the Nest moved in the current mission, replot even on the latest patch.
What this table cannot answer yet
Current public evidence is insufficient for an official per-shell firing table, height correction, exact flight-time table, dispersion radius, wind or weather coefficient, or guaranteed maximum range. Those need repeated AppID 2950790 measurements with shell, charge, elevation, height, map, patch, and impact all controlled.
For moving targets, a correct static range is only the first half. Continue to Flight Time and Moving Targets to turn the dial’s observed flight time and target speed into a lead estimate.