UNOFFICIAL GUIDE · Evidence reviewed September 1, 2026 · Build baseline 24750322, Version 1.0 (1622), Patch #5 · No current-build author playtest
UNOFFICIAL GUIDE
This page covers the task-specific signals around that shot. It does not provide a reusable firing card because the mission text treats the origin and target as current-operation inputs. Use the walkthrough to move through the task, then use the specialist guides when you need to calculate or diagnose one of those inputs.
Calibration Fire is IRON NEST Mission 1. Plot the firing line from your current Iron Nest position to the designated Target, load HE, and fire. If you miss, recheck origin, bearing, and range. The mission ends with a calibration confirmation and an order to stand down.
| Field | Value |
|---|---|
| Mission | Calibration Fire IN-GAME TEXT: the current Campaign registry and English title identify Calibration Fire in build 24750322. |
| Campaign position | Main-line Mission 1 IN-GAME TEXT: the Patch #5 campaign order assigns mainLineNumber: 1. |
| Objective | Plot a firing trajectory to the designated Target, fire, and confirm accuracy IN-GAME TEXT: the mission description and opening order state this task. |
| Required shell | HE IN-GAME TEXT: the order explicitly tells the crew to use an HE shell. This is an instruction, not a test of every other shell. |
| Firing line | Current Iron Nest position to Target IN-GAME TEXT: the order and detailed miss message identify the current origin, bearing, and range as the values to check. |
| Miss feedback | TARGET MISSED IN-GAME TEXT: build 24750322 contains detailed and short miss messages. Their trigger order and frequency are not established. |
| Completion signal | Calibration confirmed, combat ready, stand by, then go to the bunk and stand down IN-GAME TEXT: the completion message supplies the visible handoff. |
| Version | Build 24750322, Version 1.0 (1622), Patch #5 IN-GAME TEXT: extracted August 17 and reviewed September 1, 2026. |
Evidence
Official mission description: Plot the firing trajectory to the designated Target, fire HE, and confirm the accuracy of the Iron Nest before active deployment.
Calibration Fire is the first item in the formal Campaign order. For the complete sequence and the status of every mission guide, use the all 15 Campaign missions list. This page stays focused on the first task rather than repeating that index.
The order gives you three boundaries that matter. First, the firing line starts at the current Iron Nest position. Second, it ends at the entity displayed as Target. Third, the requested ammunition is HE. None of those statements supplies a universal bearing, range, elevation, or charge setting.
Treat the map reading as current-operation work. Mark the Iron Nest position you have now, identify the Target named by the order, and measure between those two points. If you begin from a report marker, an old position, or a visually convenient landmark, every later calculation can be internally consistent while still describing the wrong line.
Once the current inputs are written down, continue through the shared firing loop. That guide owns the general sequence across missions. Calibration Fire only adds its designated Target, HE order, miss text, and completion message.
The page deliberately does not publish a worked firing card. The audited mission fields do not contain one set of reusable coordinates or firing values, and a value seen in one recorded run would not establish that it applies to yours.
Read the title and opening order before moving to the firing controls. The task should be Calibration Fire, and the order should direct you to a designated Target. This is the success signal for setup: you know which task is active and which entity owns the firing line.
If the task text or target is not the one described here, stop and recheck the current Campaign state. Do not borrow a target from a later mission or an older guide just because it looks like the next obvious object on the map.
Use the current Iron Nest position as the origin. Draw or measure from that point to the Target, then record the bearing and range for this operation. These are inputs, not values supplied by this page.
If the direction looks wrong before firing, revisit the origin rather than adjusting the final elevation at random. The origin-first bearing workflow explains how a correct-looking line can still be referenced from the wrong point.
Take the current range into the manual elevation workflow, or use the IRON NEST firing calculator if you want the calculation handled for you. Match the charge used by the physical shot to the charge used by the calculation.
The success signal here is consistency: the origin, target, range, bearing, charge, and elevation all describe the same current firing line. The mission does not supply a page-wide fallback number when one of those inputs is missing.
Follow the order and load HE. Aim using the bearing and elevation produced from your current inputs, then fire at the designated Target. The order establishes HE as the requested shell; this guide does not claim to have tested every other shell against the completion event.
If the shot lands elsewhere, do not convert that one impact into a permanent offset. Read the feedback, preserve the inputs you actually used, and move to the troubleshooting checklist below.
Build 24750322 contains both detailed and short TARGET MISSED messages. The detailed message tells the crew to recheck the current Iron Nest position, bearing, and range. That is the task-specific recovery loop.
The extraction does not establish which miss produces which message, how many misses are allowed, or when any shell grant becomes visible. Continue from the message you receive rather than trying to force a hidden sequence described elsewhere.
After the designated Target is destroyed, the current build's Target-role event flows into the visible calibration confirmation. The message then marks the Iron Nest combat ready, orders the crew to stand by, and directs you to the bunk to stand down.
That confirmation is the success signal. If it does not appear, first verify that you engaged the displayed Target and not the Hospital, then recheck the firing inputs. Do not use collateral damage, a Steam achievement, or an assumed medal as a substitute for the mission's own completion message.
These symptoms appear in player questions, but the reports do not prove one shared bug or a single universal cause. Use them as a route into the input checks that the task itself supports.
| What you saw | First check | Next handoff |
|---|---|---|
| The shot flew in the opposite direction | Confirm that bearing was measured from the current Iron Nest position toward the Target, not in reverse. | Rebuild the line with the origin-first bearing workflow linked in step 2. |
| The shot went off map | Recheck the origin, bearing direction, and range transcription before changing the firing controls. | Return to the shared firing loop and confirm each current-operation input. |
| The shot landed short | Recheck the measured range, then recalculate elevation with the same charge you intend to load. | Use the manual elevation workflow or calculator linked in step 3. |
| The impact was visible but still missed | Keep the actual shot inputs and impact observation together. Do not apply an undocumented permanent offset. | Troubleshoot the miss and rebuild the firing solution. |
| The task still shows `TARGET MISSED` | Follow the current message and recheck Iron Nest position, bearing, and range. | Return to walkthrough steps 2 through 5. |
Change one uncertain input at a time when possible. If you reverse the bearing, replace the range, and change charge or elevation together, the next impact may move without telling you which correction mattered. The aim is to rebuild a coherent current shot, not to discover a number that can be copied into every run.
In build 24750322, the designated Target is a distinct entity carrying Enemy and Target roles. The Hospital is a separate Ally entity. The completion event filters for the Target role, so destroying the Hospital is not the condition that advances the current mission flow.
That answers the identity question, but it does not settle every collateral question. The available extraction does not establish whether a correctly placed explosion will affect the Hospital in every run, whether the relative placement is fixed, or what collateral would do to scoring, newspapers, achievements, or another result surface. This guide therefore does not promise either damage or safety.
Keep the firing order literal: engage the displayed Target with HE. If you need ammunition properties outside that order, use the complete shell types reference. Shell statistics do not change which entity the task names as its target.
The completion handoff is a sequence of visible instructions, not a reward number. The calibration is confirmed, the Iron Nest is described as combat ready, the crew is told to stand by, and the next action is to go to the bunk and stand down.
The current build flow supports the connection between Target-role destruction and that message. It does not require this page to expose internal node names, and it does not turn an achievement or medal into the mission trigger.
If you are checking rewards after the task, use the medals by mission reference. The current audit did not close the attribution of a specific in-game medal to Calibration Fire, so this page does not publish a medal slot or threshold. A platform achievement with a related name is also a separate system from the in-game completion event.
This walkthrough is anchored to build 24750322, Version 1.0 (1622), Patch #5. The shared game-data extraction was captured August 17, 2026, and the page facts were reviewed September 1, 2026.
Seven open questions do not block the task guide: exact miss-event ordering, Hospital collateral, complete starting inventory, medal attribution, current-build dedicated footage, completion with non-HE shells, and whether the Target and Hospital placement is fixed across runs. Those questions are why the page uses the visible order and confirmation while avoiding stronger inventory, reward, shell-exclusivity, and collateral conclusions.
Player footage shows a continuous formal-release run, but it does not display the current build. Its chapter length is an observation from that recording, not a target time. Community questions help identify confusing symptoms; they do not establish frequency or a confirmed defect.
Older Demo or pre-release material can use different framing. This page covers the current formal Campaign task. Use the IRON NEST Demo guide when the version boundary, download, or Demo mission set is the actual question.
Refresh this page if a later build changes the Campaign order, task text, Target or Hospital roles, completion filter, or visible stand-down message. A metadata-only or layout change does not create a new game-fact verification date.
Yes. Calibration Fire is IRON NEST Mission 1 in the main-line Campaign order for build 24750322. See Mission facts for the version and objective boundary.
Plot the firing trajectory from the current Iron Nest position to the designated Target, fire HE, and confirm accuracy. Read the orders before calculating so every input belongs to the same firing line.
Use HE because the current mission order explicitly requests it. That instruction does not prove that every other shell is unable to satisfy the runtime event; follow walkthrough step 4 for the approved task path.
Start by rechecking the current Iron Nest origin, bearing, and range, then make sure charge and elevation were calculated as one setup. These symptoms do not establish one confirmed cause. Use the miss troubleshooting checklist to choose the next check.
No. In build 24750322, the Hospital is a separate Ally and the designated Target carries the Target role used by the completion event. The available evidence does not settle collateral or scoring outcomes; see the Target and Hospital boundary.
Wait for the calibration confirmation and the instruction that the Iron Nest is combat ready, then go to the bunk and stand down. That task message is separate from medals and platform achievements. See Completion and stand-down.
Reviewed August 1 to September 1, 2026. Evidence types and dates are stated beside each claim above.
Official: The developer-maintained firing FAQ supports the shared mission-to-mission workflow, while the official achievement list supports the public task name and the achievement boundary.
In-game text: Build 24750322 Campaign order, mission graph, flow, entity roles, event filters, shell grants, and English localization support the task identity, orders, miss feedback, Target and Hospital boundary, and completion handoff.
Observed footage: A continuous formal-release player run supports the visible task sequence and transition.
Reported: Dated community questions and third-party guide material support problem selection and conflict checks for opposite, off-map, short, Hospital, inventory, and reward claims.
Spot an error or a post-patch change? This guide follows correctable public evidence — corrections update the page and its review date.