UNOFFICIAL TOOL GUIDE · Reviewed August 27, 2026 · Version 1.0 (1622), build 24750322, Patch #5 · Public evidence, no author gameplay test
UNOFFICIAL TOOL GUIDE
Compare six charge, elevation, and predicted flight-time options from one target distance, then schedule an optional impact time and keep selected shots in a session log.
Enter the distance from the current Iron Nest to the target. The tool compares all six powder-charge options with elevation and predicted flight time. Bearing and shell remain optional log fields; planned impact time is optional and produces a per-row predicted fire time.
Enter the target distance to compare all six powder-charge, elevation, and predicted flight-time combinations. Optionally set an impact time to see when to fire, then pin an in-range row to the session target log.
Results use the build-aligned community formula E = 12D/C. Flight time uses the current-build shell speed curve. Verify low-angle estimates in game; impact timing does not include loading, aiming, trigger, network, or reaction delay.
E = 12D/C 5 * charges km u = (charges - 1) / 5; T = D / [0.7 × (0.3 + 0.7 × (3u^2 - 2u^3))] fire time = impact time - flight time | Powder charges | Estimated elevation | Predicted flight | Fire at | Configured maximum | Status | Action |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 | ||||||
| 4 | ||||||
| 5 | ||||||
| 6 |
Elevation uses the build-aligned community formula E = 12D/C. Predicted flight time uses the build 24750322 shell speed curve, independently checked against six charge samples.
Elevation and flight time use Iron Nest Guide display precision, not a claim about the game's own rounding.
Predicted fire time subtracts flight time rounded to the nearest second. It does not include preparation, loading, aiming, trigger, network, target movement, or reaction delay, and it does not guarantee an impact time.
Current inputs and pinned targets are saved automatically in this browser. Export the session before changing devices or clearing site data.
Pin any available firing solution to add its distance, bearing, shell, charge, elevation, predicted flight time, and optional impact timing.
The official release-period workflow places the ballistic calculator between tactical-map measurement and gun setup. OFFICIAL · 1.0 release period
This page deliberately stops short of computing map distance, target bearing, target lead, shell damage, cross-device synchronization, preparation delay, or dual-gun timing. Flight and fire times are current-build predictions, not exact impact guarantees. It records player-supplied bearing and shell without claiming that those fields are independently calculated or irrelevant to every official branch.
Build 24750322 gives all 21 extracted shell definitions the same six charge-range mappings. Each additional charge adds 5 km to the configured maximum, up to 30 km. IN-GAME TEXT · build 24750322
| Powder charges | Configured range band | Maximum used by this page |
|---|---|---|
| 1 | 0-5 km | 5 km |
| 2 | 0-10 km | 10 km |
| 3 | 0-15 km | 15 km |
| 4 | 0-20 km | 20 km |
| 5 | 0-25 km | 25 km |
| 6 | 0-30 km | 30 km |
The 0 endpoints are build configuration values. They do not prove that the current UI accepts every low-angle input, displays 0°, or uses no separate error rule. Community charts impose different lower cutoffs, so this page does not publish a fixed official minimum distance or angle.
The shared range mappings also do not prove that every shell field is irrelevant to the official calculator. For ammunition properties and the complete extracted catalogue, use the all shell types table.
The firing tool uses:
E = 12D/C
E is the estimated elevation in degrees.D is firing distance in kilometres.C is the whole number of powder charges, from 1 to 6.To calculate manually, multiply the distance by 12, divide by the planned charge count, and compare the distance with 5C km. Carry enough precision while calculating, then round only the displayed estimate to 0.1°.
Predicted flight time uses the build-derived curve u = (C - 1) / 5 and T = D / [0.7 × (0.3 + 0.7 × (3u^2 - 2u^3))]. Here u normalizes charge count 1–6, and T is predicted airborne time in seconds.
This speed curve is decoded from build 24750322 and checked against independent timed samples. It is build-specific, not a real-world physics formula or a promise that future builds use the same speed values.
Why this method is publishable with limits: the official ArtilleryComputer component in build 24750322 has 0° and 60° elevation endpoint settings, and its referenced shell mapping reaches from 0 km to 5C km for each charge count. Community calculators, charts, reports, and player explanations independently use the same straight-line relationship. IN-GAME TEXT endpoints plus REPORTED linear interpolation · reviewed August 27, 2026
What remains unconfirmed: the official method body has not been fully reconstructed, and this page has no controlled current-build gameplay matrix for non-integer distance, low-angle output, display rounding, range tolerance, clamping, or every error state. The equation is therefore a build-aligned community formula, not a claim that this site has cloned the official calculator.
Do not infer a fixed lower valid window from a community table. Do not reuse a value from another run as a universal firing solution. Range, charges, elevation, bearing, mission state, and observation still need to agree in the operation you are playing.
The Version 1.0 mission graph contains a BrakeCalculator event for The Gorge, so a calculator-loss scenario is part of the game rather than only a player rumour. IN-GAME TEXT · build 24750322 The extracted event does not establish whether every calculator failure is repairable, how long a failure lasts, or what resets between missions.
If the mission removes the calculator, keep the same preparation chain: establish the target, measure the firing line from the Iron Nest, choose charges, use the qualified manual formula if appropriate, and confirm with observed fire. The mission itself decides what equipment remains available and what signal completes the objective.
For the operation-specific engine restart, reconnaissance, observed-fire sequence, and completion signal, follow The Gorge manual-fire walkthrough. This calculator page does not copy that mission's route or promote one run's grids, bearings, ranges, charges, or elevations into general rules.
Version 1.0 text includes Bearing to Target, Distance to Target, Shell Type, Calculated Powder Charges, and Not Enough Charges. IN-GAME TEXT · build 24750322 Their presence proves that these labels exist in the calculator or firing-card context. It does not by itself reveal which values the official elevation method reads.
Community tools commonly reduce the linear estimate to distance plus charges. This page therefore accepts distance and generates all six charge options. That interface boundary is not evidence that bearing, target, shell type, or gun side can never affect the official calculator.
Treat Not Enough Charges as a prompt to check several things:
5C km configured maximum;The build-backed range ceiling is compatible with the common explanation that too few charges cannot cover the requested range. The complete trigger logic is not confirmed, and inventory or other UI states have not been ruled out.
Community-made calculators, spreadsheets, ranging charts, and firing tables are common because they make repeated linear calculations faster. They are useful evidence that players use E = 12D/C; they are not official specifications.
Before trusting an external result, ask:
Iron Nest Guide does not mirror an external tool's UI, source code, chart image, table, or decimal-precision promise. It also does not endorse one fan implementation as the official calculator. The firing tool on this page states its own formula, display choice, inputs, and unresolved branches so that its result can be checked rather than merely trusted.
The calculator is one link in a longer chain. Use the page that owns the problem you actually have:
Bearing-from-Spotter, full map measurement, exact elevation-query, moving-target lead, and dual-gun coordination remain separate candidate responsibilities. This page does not create empty links to unpublished owners.
No. It is an unofficial firing tool that uses official build endpoints and range bands with a community-confirmed linear method. The official interpolation method, rounding, low-angle output, field dependencies, and every error branch are not fully confirmed.
It uses E = 12D/C, where D is distance in kilometres and C is the number of powder charges. The equation is published as a build-aligned community formula, not as a complete reconstruction of the official calculator.
It always compares 1 through 6 charges. Build 24750322 gives the extracted shells six shared mappings, with configured maximum ranges from 5 km at one charge to 30 km at six charges.
The build contains a 0° endpoint, while community charts use conflicting lower cutoffs. Current in-game low-angle behaviour has not been runtime-verified, so the page keeps the estimate visible and labels the uncertainty instead of inventing an official invalid threshold.
The entered distance is greater than 5 * charges km for that row. Choose a different charge row if the game and inventory allow it, or recheck the distance; the page does not present the overflow result as a usable in-game solution.
This tool does not use shell type or bearing. The extracted shells share the same charge mappings, but the available evidence does not prove that the official calculator ignores every other shell, bearing, target, or gun-side field.
Predicted flight time divides distance by the adjusted shell speed from build 24750322. If you enter a planned impact time, the tool subtracts flight time rounded to the nearest second. It does not include loading, aiming, trigger, network, target movement, or reaction delay, so treat the result as a coordination estimate rather than a guaranteed impact time.
A range beyond the selected charge band's maximum is one evidence-compatible explanation. The complete trigger logic is not confirmed, and inventory or other interface states have not been excluded.
No universal firing solution is published here. Recalculate from the current Iron Nest with the current distance, choose the charge row for that shot, and keep observation and correction values tied to that operation.
Reviewed August 17-27, 2026. Evidence types and dates are stated beside each claim above.
Official: Release-period FAQ material supports the tactical-map-to-calculator-to-gun workflow; a dated developer explanation supports the intended 60° direction without publishing the calculator formula.
In-game text: Version 1.0 (1622), build 24750322, Patch #5 supplies calculator labels, shared charge and speed curves, the ArtilleryComputer endpoint settings, and The Gorge's calculator-loss event.
Observed footage: Reviewed player footage shows calculator, loading, manual-fire, and correction workflows in individual runs; no fixed firing solution is generalized from those recordings.
Reported: Community calculators, charts, timed samples, videos, and third-party guides corroborate the elevation method and current-build flight-time model, but do not establish exact impact timing, future-build behaviour, field dependencies, or complete error logic.
Spot an error or a post-patch change? This guide follows correctable public evidence — corrections update the page and its review date.