IRON NEST: Heavy Turret Simulator Guides

IRON NEST: Heavy Turret Simulator turns a single artillery shot into a chain of jobs. Read the teleprinter, plot the intelligence on the tactical map, measure from the Nest to the target, prepare a firing card with the ballistic calculator, choose ammunition, load the requested powder charges, set bearing and elevation, arm the correct gun, and fire. A missed step is usually more important than quick movement. This guide hub organizes that loop so a new Operator can solve the next problem without confusing the Steam base game with the older Demo or Playtest.

Start with the complete operator loop

Every mission begins with information rather than a visible crosshair. The developer FAQ describes the canonical sequence: orders arrive through the teleprinter, useful details go into the notebook, measurements are made on the map, and those measurements feed the ballistic calculator. The resulting solution determines the gun’s elevation for a chosen shell and number of powder charges. Only then should the Operator load, rotate, elevate, arm, and fire.

Treat the loop as a paper trail. Keep the current order visible, place markers for friendly observers and reference points, and make the final Nest-to-target line with the tool intended to create a firing solution. At the calculator, compare every field with the target rather than turning dials from memory. At the gun, compare shell, charge count, bearing, elevation, and armed side with the card. This deliberate workflow is faster than recovering from a shell sent to the wrong grid.

The Beginner Guide walks through a first session in practical order. Once the sequence feels familiar, the specialist hubs below help with a narrower question.

Choose the guide by the station that stopped you

Read the map before touching the calculator

The tactical map is both the battlefield view and the Operator’s working surface. Orders may identify spotters by grid position, bearing, distance, or a relationship to a reference point. Plot known positions first. A line drawn from the wrong spot can look precise and still produce a bad solution. When two bearings are provided, the target is near their intersection; when a distance is involved, the compass creates the corresponding circle. Reconnaissance and illumination can replace an estimate with direct map evidence when the mission provides them.

After locating a target, measure from the Nest’s actual map origin to that point. Community guides repeatedly warn that measuring from the visible body instead of the designated origin can magnify the error at long range. The Tactical Map Guide explains the grid, subgrid, pencils, compass, markers, and the transition from intelligence marks to a firing line without publishing an unverified universal coordinate table.

Do not enter the calculator while the map still contains two plausible targets. The calculator converts an input into a setting; it cannot decide which interpretation of an order was correct.

Load and aim as two separate checks

The official description and FAQ emphasize manual operation. Ammunition choice, powder charges, breech state, turret rotation, gun elevation, gun selection, and the firing action are distinct. That matters because correcting one does not silently correct the others. A valid elevation for a chosen charge count is not valid after adding a charge, and a correct bearing does not compensate for the wrong shell.

Use coarse controls to approach a bearing or elevation and precision controls to finish, following the labels and hint clipboards in the current public build. Wait for the loading cycle and breech state required by the interface. Before firing, perform a verbal comparison: target, shell, charges, bearing, elevation, left/right/both, armed. If one field cannot be confirmed, stop the shot and trace it back to the card or map.

The base game’s two 800 mm guns can be operated independently in situations the mission supports. Independence is useful, but it doubles the number of states to verify. Do not assume linked elevation, identical loads, or simultaneous firing simply because both barrels point in a similar direction.

Plan requisition around the objective

The Requisition Console supplies more than ammunition. Official material identifies extra powder, reconnaissance, specialized ammunition, and battlefield-control abilities as part of progression. That makes requisition a mission plan: buy what turns uncertain information into a confirmed firing solution, what gives the target the required effect, and what preserves enough capacity for the next order.

Avoid treating a community price list as permanent. Public 1.0 launched on 2026-08-06 and received two official patches by 2026-08-08. Costs, unlocks, and exact effects can change independently of the broad system. Read the current console and record the available total before committing. A recon option may be more valuable than another destructive round if location is the actual bottleneck.

The Arsenal hub separates shell roles, loading, requisition, abilities, cards, and target matching. It also keeps the official phrase about “30 unlockable ammo types and abilities” from being misread as 30 different shells.

Recover from a miss without guessing

A miss carries information. First check whether the impact appeared on the tactical map or in a recon photograph. Compare direction and distance from the intended point. A consistent left/right error points toward bearing or origin; a consistent short/long error points toward range, charge count, or elevation; a completely unrelated impact suggests the wrong target card, gun, shell, or load.

Change one variable at a time. Preserve the original map mark and card until the corrected shot is prepared. If the target is moving, if the Nest has repositioned, or if new intel changed the reference point, invalidate the old solution rather than “nudging” it. Recalculate from the new geometry.

After a crash or a mission-entry problem, consult Support before deleting data. Official PATCH 1.0 (1558) specifically addressed save corruption and failure to enter missions after a crash. Confirm the public build has updated, verify game files through Steam, and protect any existing save before trying destructive recovery.

Keep versions and products separate

The Steam base game is AppID 2950790 and released as full version 1.0, not Early Access. The Demo is AppID 4300500 and has its own release, content, saves, and historic patches. SteamDB identifies 4300490 as a Playtest/Beta related to the base game, but that third-party classification does not turn test behavior into public-branch documentation.

The developer uses numbers such as 1547 and 1558 in official patch titles. This site preserves those titles but does not call the numbers Steam BuildIDs. Likewise, a newer testing-branch BuildID does not prove that its changes reached ordinary players. The Updates hub records official public announcements and keeps roadmap promises separate from shipped features.

Quick operator answers

Is IRON NEST multiplayer now?

No. The developer FAQ says public version 1.0 is a single-player experience. Multiplayer for this base game is planned, and a separate future co-op title has also been discussed, but neither should be described as a current 1.0 mode.

How long is the campaign?

The developer estimates roughly 8–12 hours to complete every mission once without replays. That is an estimate from internal and community playtests, not a guaranteed completion time. Challenge missions provide the repeatable layer beyond a first campaign run.

Is Steam Deck the same as native Linux support?

No. Steam lists the game for Windows, and the developer does not promise native Linux. Steam Deck verification and reports of Proton compatibility describe a compatibility route, not a native Linux build.

Where should a new player go next?

Open the Beginner Guide and complete one firing solution end to end. Then use Ballistics when the map or calculator is the bottleneck, or Support when the software or hardware prevents the normal loop.

Sources

• Steam Store page for AppID 2950790
• Developer-authored Frequently Asked Questions
• Official Steam announcements
• Community operator basics guide — useful for station order and map terminology; older Demo-era values are not treated as public 1.0 facts.