IRON NEST: Heavy Turret Simulator is controlled through physical stations rather than one conventional weapon HUD. The useful skill is knowing which station owns an action, what state enables it, and how to leave it cleanly. Exact keyboard or controller labels can change with remapping, so this guide follows the prompt displayed by the current public build instead of publishing a brittle list of default keys.
2950790, Windows public version 1.0, checked 2026-08-09. The Store lists full controller support. Demo AppID 4300500 is a separate product and its old prompts are not treated as base-game bindings.Set input before entering an operation
Open Settings from the main menu and inspect every binding category with the device you intend to use. Confirm look sensitivity, interaction, backing out of a focused station, movement, and any hold/toggle behavior the menu exposes. Record a screenshot if you remap extensively; it is more dependable than a web list after a patch.
Test both ordinary movement and a focused control. A prompt can change when the cursor is over a lever, wheel, clipboard, or map tool. If a displayed label does not match the device in your hands, disconnect duplicate controllers, restart with only the intended device, and check Steam Input settings before changing mission data.
Learn the Nest as a chain of stations
The operational route begins at the teleprinter and notebook, moves to the tactical map, continues through the ballistic calculator and Requisition Console, then reaches loading, bearing, elevation, arming, and the firing cord. The post-shot map report and newspaper complete the loop.
Walk the full route without firing. At each station, identify the interaction prompt, the control that exits or releases focus, and the visible state that says the machine accepted input. Read the nearby tutorial clipboard. This makes a later problem easier to classify: input failure, locked machine state, or an incorrect firing plan.
Understand focus, levers, and wheels
Many controls require the player to focus a station before a mouse movement, stick movement, button, or trigger affects it. Do not assume a lever is broken because ordinary camera motion stopped. First use the displayed back/release prompt and refocus deliberately.
Large and fine adjustments serve different jobs. Move bearing or elevation quickly for the broad change, then use the fine control for the last fraction shown by the dial. Release the control and re-read the value. Long-range shots magnify a small angular mistake, so a visually close handle is not the same as a checked setting.
A disabled control often indicates sequence, not bad input. Elevation may depend on loading and breech state; firing depends on the intended gun being armed; mission progression may wait for a teleprinter page or newspaper. Inspect the machine before repeatedly pressing the same button.
Practice the map and calculator separately
On the map, practice selecting a drawing tool, placing a mark, measuring from a known origin, and clearing only the mark you intended. Keep evidence marks distinct from the final Nest-to-target solution. The Tactical Map guide explains the reasoning behind each layer.
At the calculator, enter a harmless practice solution and verify that selection fields, charge count, calculation control, and result display respond. Do not memorize community formulas as controls. The in-game calculator is the supported interface for ordinary play, and its output only applies to the shell, range, and charge combination entered.
Handle two guns without crossing states
The left and right guns can hold separate loading, elevation, and arming states. Before touching either set of controls, decide which side owns the current firing card. Trace that side from loading equipment to elevation control and arming lever. After a shot, verify that the expected side changed state.
Never arm both by habit. Dual-gun use belongs to a deliberate plan with both loads checked. The Dual Guns guide separates confirmed workflow from mechanics that still need repeatable public-build testing.
Recover from input trouble safely
PATCH 1.0 (1558) improved cases where the mouse could not move after loading the main menu or a mission. Confirm Steam installed the current public content, then release the focused station, open and close the pause menu, and return to the main menu normally if possible. Verify game files if the symptom persists. Avoid deleting a save for an input problem.
For controller trouble, test with one connected device, check the current in-game prompts, and compare the Store’s full-controller-support claim with the specific menu or station that fails. Capture the device model, Steam Input setting, public version, and reproduction steps for a useful report.
Verify the map-tool control chain
Enter the tactical map and perform a four-action test: select a bearing/range line, place its origin on a named observer, drag toward a reference, and release while watching the measurement. Then select a circle tool, center it on a different named point, set its radius, and return to ordinary cursor behavior. Finish by drawing the separate Nest-to-target line.
This sequence tests focus, press/hold behavior, stick or mouse precision, tool switching, and exit control without needing a mission spoiler. If only one step fails, report that step and active tool. If release leaves a line attached to the cursor, compare the displayed prompt and whether the same release works on a calculator or lever. Fine map input matters because an origin error becomes bearing and range error even when gun controls work perfectly.
Control questions
What are the default keys?
Use the current Settings screen. This page intentionally avoids a frozen key chart because remapping, keyboard layout, controller type, and patches can change labels while the station workflow stays valid.
Why can I rotate but not change elevation?
Check the load, breech, and current gun state. A mechanically unavailable control is different from a missing input event.
Does a gamepad support the whole game?
Steam lists full controller support for AppID 2950790. If one station fails, report that specific interaction instead of assuming the whole controller profile is unsupported.