The ballistic calculator is the supported bridge between a map solution and the elevation controls. It cannot validate where you placed the target or what was loaded; it produces an answer for the inputs selected. The operator’s job is to keep those inputs attached to the same firing card all the way to the cord.
2950790, Windows base-game public 1.0, checked 2026-08-09. No universal elevation table or hidden formula is asserted because exact values require repeatable current-build testing.Arrive with a measured range
Finish target plotting first. Draw from the Nest’s correct origin to the chosen target and record both bearing and distance. The calculator should not be used to compensate for a vague target mark. If two target candidates remain, resolve that uncertainty on the map.
Write a card with operation, target, gun side, shell, proposed charge count, bearing, and range. Leave elevation blank until calculated. This physical separation makes it obvious when a later supply change invalidates the answer.
Enter one coherent combination
Use the controls shown on the machine to select the intended context, range, ammunition, and powder. Choose a charge count the current interface accepts, calculate, and copy the result exactly. If the machine rejects a combination, do not force a nearby value or import a Demo table; change a permitted input and calculate again.
Read all displayed output, not only the largest number. Confirm the result belongs to the values still shown. A calculator panel left from an earlier target can look authoritative even after the map changed.
Charges are part of the solution
Powder is not an afterthought. The calculated elevation belongs to a particular charge count. At loading, count actual charges and compare them with the card. If requisition supply, an operator slip, or an already committed load changes the count, mark the old elevation invalid and recalculate for what can safely be fired.
Avoid publishing copied charge costs or range bands unless current base-game play reproduces them. Demo-era guides can explain why charges matter without fixing the public 1.0 values.
Transfer the result without drift
At the gun, set the card’s bearing and elevation on the side that received the matching shell and powder. Use coarse movement to approach, fine movement to finish, then release and re-read the dial. Do not round simply because the handle is awkward.
The two barrels can have different state. A perfect right-gun solution fired from a differently loaded left gun is not a calculator failure. Add “loaded side” and “armed side” to the final comparison.
Diagnose an apparently wrong result
When a shot misses, preserve the calculator input and classify the error. A left/right miss usually calls for reviewing target plot, origin, or bearing before elevation. A short/long miss calls for checking measured range, actual powder, and transferred elevation. An accurate impact with the wrong objective result calls for shell selection or target classification.
Change one variable and produce a new card. If every input changes at once, the next impact cannot validate the calculator or the correction.
Calculator unavailable or out of a choice
If an option seems exhausted, read the current mission state and Requisition Console before assuming a bug. Confirm the selected shell and whether a prior load has committed resources. There is active community interest in manual solutions, but those are advanced, version-sensitive methods; the Manual Aiming guide treats them as experimentation rather than guaranteed formulas.
For a stuck interface, release focus, revisit the station, and confirm the public build is current. PATCH 1.0 (1558) improved mouse movement after loading the menu or mission, but it does not turn an invalid mechanical state into a valid calculation.
Why real-world tables are unsafe here
The developer describes a deliberately game-readable artillery model and notes non-realistic elevation behavior. External physics calculators may use gravity, drag, muzzle velocity, or angles that IRON NEST does not expose or model identically. They can be research tools only after controlled in-game calibration.
For normal operations, the in-game machine plus observed impact is the authority. Record public version whenever testing a table so a patch can be identified as the reason results changed.