Measure the current shot.
Keep the unit beside the number.
UNOFFICIAL GUIDE · Research checked August 31, 2026 · Steam build 24750322 · Version 1.0 (1622), Patch #5
UNOFFICIAL GUIDE
How to Calculate Elevation in IRON NEST
To calculate elevation in IRON NEST, measure from the current Iron Nest to the current target, choose the charge count you will actually load, and use the bounded manual estimate below. Recalculate whenever the Nest, target, unit, or charge count changes.
Quick answer: calculate elevation from range and charges
The official firing loop supports the order of operations: measure on the tactical map, enter that measurement into the ballistic computer, and load the same number of charges used for the calculation. When the computer is available, use the interactive firing calculator for its owned tool workflow and flight-time output. The arithmetic on this page is an offline estimate, not a second calculator.
Inputs before the math
| Field | Value to record |
|---|---|
| Range origin | The current Iron Nest position Official firing loop; operational boundary |
| Range endpoint | The current target point Official firing loop; operational boundary |
| Distance unit | Kilometres or metres, stated explicitly Mathematical unit conversion |
| Charge count | The count that will actually be loaded Official FAQ: calculated and loaded charges must match |
| Result | A gun-elevation estimate in degrees Community interpolation aligned with current build endpoints |
| Build baseline | Steam build 24750322, Version 1.0 (1622), Patch #5 Extracted game data and component configuration |
A clean calculation starts with a clean shot record. Do not reuse a distance because the target appears close to the previous one, and do not treat the charge count as a cosmetic setting. Check these fields together:
The range is shot-specific. If the Iron Nest moves, the target point changes, or the crew changes the intended charge count, the previous result is stale and should be rebuilt. This is a safe operating model derived from the official measurement loop and the site’s cross-page firing workflow; it is not a claim that the in-game UI detects stale inputs for you. If you still need the range, use the map grid and measurement guide. That page owns the measurement operation. This page begins once you have a distance and need to turn it into an elevation estimate.
Charge-band endpoints in the current build
| Charge count | Extracted maximum distance |
|---|---|
| 1 | 5 km |
| 2 | 10 km |
| 3 | 15 km |
| 4 | 20 km |
| 5 | 25 km |
| 6 | 30 km |
These are maximum endpoints in the extracted fields, not recommendations. They do not tell you that the lowest possible charge is always best, that the highest possible charge is always best, or that one charge is universally optimal where bands overlap. They also do not establish a gameplay-tested low-angle minimum.
The shared table means this page does not need 21 duplicated shell tables. It does not prove that every shell behaves identically in every ballistic system or future build. For caliber, ammunition, and charge context beyond this one extracted field, use the shell and charge reference.
Before continuing, make one practical decision: which charge count will the crew load for this shot? Use that same count as C in the estimate. If the loading decision changes, the elevation estimate changes too.
Manual elevation estimate and evidence boundary
For a distance in kilometres, the build-aligned community interpolation is:
E = 12D / C
Eis the estimated gun elevation in degrees.Dis the current Nest-to-target distance in kilometres.Cis the number of charges that will actually be loaded.
An equivalent form shows how the estimate relates to the extracted 60-degree and 5-kilometres-per-charge endpoints:
E = 60D / (5C)
If the map measurement is recorded in metres, use a different symbol so the unit change stays visible:
E = 0.012d / C
Here, d is the distance in metres. Do not put a metre value into the kilometre equation. A unit mistake changes the result by a factor of one thousand.
Illustrative arithmetic example
Suppose a teaching example uses D = 7.5 km and C = 3. The interpolation gives E = 12 × 7.5 / 3 = 30°. That number demonstrates the arithmetic only. It is not copied from a mission shot card, not a promise that the game will display exactly 30.00°, and not evidence for a universal three-charge firing solution.
Why the caution? The current build confirms the endpoint configuration, and multiple community explanations converge on the same linear interpolation. The complete calculator method body, all error paths, randomized behavior, and midpoint rounding have not been mapped into a gameplay oracle. The site therefore treats the equation as a useful, build-aligned estimate rather than an official formula disclosure. The calculator’s formula evidence boundary covers the corresponding tool-side limit.
Manual workflow when the computer is offline
Record the distance from the current Iron Nest to the current target, not from an old Nest position or a convenient map landmark.
Choose the charge count you will load.
Compare the distance with the extracted maximum endpoint to reject an obviously excessive range. Do not turn the overlap between bands into an unsupported “best charge” rule.
Calculate the estimate.
Use E = 12D/C for kilometres or E = 0.012d/C for metres. Label the result as an estimate.
Cross-check the shot record.
Confirm that the origin, target, unit, and intended charge count still describe the same shot. Record or communicate the elevation and charge together.
Load matching charges.
The official FAQ explicitly requires the physical load to match the charge count used by the calculation. If the crew changes the load, return to step 3.
Rebuild after a change.
A moved Nest, new target, new charge count, or correction decision invalidates the old solution. Re-measure or recalculate instead of quietly editing one field.
In The Gorge, the current task graph contains a BrakeCalculator event that activates an initially inactive broken-state overlay. That supports using a manual handoff when the device is unavailable, but it does not prove a permanent failure or a fixed repair time. Follow the mission-specific manual-fire walkthrough for the task context; keep this page for the reusable arithmetic.
Once the computer is available again, use its owned tool flow. This page does not reproduce the calculator interface, predict flight time, or decide the mission for you.
Limits and troubleshooting
The estimate is above 60 degrees
The current component configuration caps elevation at 60 degrees. A result above that ceiling is outside the extracted endpoint model for the selected charge count. Recheck the unit, distance, and charge entry; then choose a valid in-game plan rather than clamping the answer silently.
The estimate is very low
The extracted component contains a 0-degree configuration endpoint and a minimum range gate of 0.01, with no separate 10-degree or 12-degree reason in the decoded contract. That still does not prove that a 0-degree result is player-usable in the current UI. Low-angle button state, animation, randomized error, and visible output remain gameplay-verification gaps. Treat an edge result as a reason to check the shot in game, not as a published lower-bound rule.
The computer says “Not Enough Charges”
In the current package connection, the calculation-error event activates the object carrying that text. The decoded reasons are NoBlueprint, InvalidRangeBand, and OutOfRange; there is no inventory reason in that contract. Check blueprint availability, the charge band, range, and units. Do not read the message as proof that the inventory system is short of charge items.
The displayed number has two decimal places
The current elevation odometer and printed fire-mission card use a two-decimal display format. That confirms formatting, not the midpoint rounding algorithm. Do not reverse-engineer a rounding rule from one third-party output or round an illustrative example and call it the exact in-game value.
The next shot uses a changed point
Rebuild the firing line when the observed result changes the target point or when the Nest moves. The rebuild-or-adjust decision guide owns the post-shot correction branch; this page only recalculates after the inputs are settled.
Where each firing task belongs
Elevation is one number in a larger firing solution. Use the page that owns the next unresolved task:
- Interactive calculation or flight time: use the Calculator, linked from the Quick Answer.
- Map distance: use the Map measurement guide, linked under Inputs.
- Bearing and firing-line transcription: use the bearing handoff guide. Elevation does not replace turret bearing.
- Impact correction: use the Fire Correction decision guide, linked under Troubleshooting.
- The Gorge sequence: use the mission walkthrough, linked from the offline workflow.
- Shell and caliber context: use the Shell Types reference, linked from the charge endpoints.
This ownership split prevents a manual formula page from becoming a second calculator, a second mission walkthrough, or a general ammunition guide. It also makes refreshes safer: a change to map measurement, bearing reports, or mission scripting can be corrected at its owner without rewriting the arithmetic explanation here.
Build scope and known limits
This guide applies to Steam build 24750322, Version 1.0 (1622), Patch #5. All build-bound conclusions on this page use that baseline.
The first version intentionally leaves the prefilled-chart claim, post-archive Discord guidance, visible low-angle behavior, randomized-error presentation, midpoint rounding, and The Gorge repair path unresolved. None is required to use the bounded manual workflow.
No author gameplay test was used to close those gaps. A patch that changes the endpoints, calculator behavior, display, error routing, or task scripting triggers a factual refresh of this page.
FAQ
What inputs do I need to calculate elevation in IRON NEST?
You need the distance from the current Iron Nest to the current target, the distance unit, and the charge count you will actually load. If the Nest, target, unit, or charge count changes, rebuild the estimate.
Should the calculated charge count match the loaded charges?
Yes. The official firing-loop FAQ says the number of charges loaded must match the number used by the calculation. A mismatch means the elevation and physical shot no longer describe the same setup.
Is E = 12D/C the official formula?
No. With D in kilometres, it is a community linear interpolation that agrees with the current extracted endpoints. The complete official runtime method and every error or rounding branch have not been verified, so use it as a bounded estimate.
What is the minimum usable elevation?
This guide does not publish a gameplay-tested minimum. The build carries a 0-degree configuration endpoint, but visible low-angle behavior has not been verified, and community 10-degree or 12-degree rules conflict with the extracted configuration.
Does “Not Enough Charges” mean my inventory is empty?
Not according to the decoded calculation-error contract. The same UI object is used for calculation failures, while the listed reasons concern blueprint, range band, or out-of-range inputs rather than inventory stock.
What should I do when the calculator is broken in The Gorge?
Use the manual workflow for the reusable estimate, then return to the mission’s manual-fire section for the actual task sequence. The evidence confirms a broken-state event, not that the device is permanently unrepairable or returns at a fixed time.
Sources and version notes
Reviewed August 26–31, 2026. Evidence types and dates are stated beside each claim above.
-
Official: The 1.0 firing-loop FAQ supports map measurement, calculator output, and matching loaded charges; the pre-1.0 angle FAQ records the intended 60-degree ceiling.
-
In-game text: Steam build 24750322 supplies the charge endpoints, component limits, error connection, display format, printer fields, and The Gorge broken-state graph used here.
-
Observed footage: Release-period player footage identifies the offline scenario and the gameplay questions checked for this guide.
-
Reported: Community explanations provide the cross-check for the linear interpolation used by the manual estimate.
Spot an error or a post-patch change? This guide follows correctable public evidence — corrections update the page and its review date.