IRON NEST Support

Support for IRON NEST: Heavy Turret Simulator starts by identifying the exact product and build. The base game is Steam AppID 2950790, released as full version 1.0 for Windows. The Demo is AppID 4300500 and the Playtest/Beta relation is 4300490. A fix, save path, or patch for either related app should not be applied to the base game without confirmation.

Confirm the supported baseline

The official minimum targets a 64-bit processor and operating system, Intel Core i5-4460 or AMD FX-8350, 4 GB RAM, Intel UHD or AMD Vega 8 graphics, DirectX 10, and 5 GB available storage. The Store notes that this aims at an average 30 FPS at 720p on low settings and recommends a dedicated GPU for smoother play.

Recommended hardware is an Intel Core i5-8400 or AMD Ryzen 5 2600, 8 GB RAM, NVIDIA GTX 1060 6 GB or AMD RX 580 8 GB, DirectX 10, and 5 GB storage. Requirements are a starting point, not a guarantee for every thermal state, driver, resolution, or background workload.

The System Requirements Guide turns those values into a pre-launch and performance checklist.

Apply public patches before troubleshooting

Official PATCH 1.0 (1547), dated 2026-08-07, fixed Czech and French localization errors that broke mission intel, a cat tooltip issue, coffee-machine interaction when returning to the menu, a pause-menu submit-button issue, and an incorrect/duplicate newspaper and record after High Tide.

PATCH 1.0 (1558), dated 2026-08-08, fixed save corruption and failure to enter missions after a crash, non-resetting elevation/linkage state after leaving a mission following a shot, and several visual/state issues. It improved cases where the mouse could not move after loading the menu or a mission, improved Discord account-link code generation, and added a Motion Blur toggle for screen-shake events.

Use those notes to narrow a report, not to dismiss it. If the same symptom remains on the current public build, record when it occurs and continue with safe diagnostics.

Protect saves before recovery

Steam lists Steam Cloud support, but Cloud synchronization is not a substitute for a known-good local copy. If the game crashes, allow Steam to finish synchronization before launching again. If a mission will not load, confirm the patch, restart Steam, verify the game files, and try the normal profile/mission flow.

Do not publish or follow a guessed save path. A path is actionable only when verified on the Windows public build with the installation method and account context recorded. Do not delete a profile, disable Cloud, or overwrite a newer save as the first step. Preserve existing data and make any experiment reversible.

When reporting corruption, include whether Steam showed a Cloud conflict, whether the crash occurred during a mission or transition, the last newspaper/mission state, and whether the same profile opens on another device.

Diagnose mouse, controller, and input issues

The Steam Store lists full controller support plus DualShock and DualSense support. Start by testing one active input device, disconnecting duplicate virtual controllers, and resetting only the relevant in-game binding after recording custom changes. Check whether Steam Input is translating a device and whether the on-screen prompts match the active input.

For a stuck mouse, install PATCH 1.0 (1558) first. Then test menu versus mission, windowed versus fullscreen if the game provides it, and whether an overlay captures focus. Avoid stacking several launch options; one controlled change produces a useful result.

If a button cannot be activated, identify the exact menu and whether keyboard/mouse and controller both fail. PATCH 1.0 (1547) fixed one pause-menu submit scenario, but an unrelated button needs its own reproduction.

Treat Steam Deck as a compatibility target

The game has an official announcement that it is verified on Steam Deck. The Store itself lists Windows, not native Linux. The developer FAQ says native Linux support is not planned at this stage and reports that Proton can run the game. Those statements together support a SteamOS/Proton compatibility guide, not a claim of a Linux build.

Record SteamOS version, Proton selection, handheld/docked state, resolution, control layout, and external display/controller when reporting a Deck problem. A fix for one combination may not apply to another. The official Deck announcement asks players to report bugs, crashes, and performance issues through the designated form.

Improve performance methodically

Start from the Store target closest to the hardware. On an integrated GPU near minimum, use 720p and low settings as the official baseline. Close overlays and background capture, verify the game uses the intended GPU, and check temperatures during sustained play. Thermal throttling can turn a stable opening into later slowdown.

Change one graphics option at a time and record the same repeatable scene. Motion Blur can be disabled in public 1.0 after PATCH 1558. Do not promise DLSS, frame generation, or a launch option unless the current menu or an official note confirms it. For black screens, record whether audio continues, whether the menu ever rendered, display mode, GPU/driver, and whether a clean relaunch reproduces it.

Use official report routes

The Steam Community Hub contains a developer-pinned Reports, Feedback & Localization hub and the FAQ links a question form. The Store website points to the official Linktree. Use those developer-controlled destinations rather than uploading saves or logs to a random guide site.

Remove personal information from logs and describe steps in order. A strong report contains AppID, public branch, date/version label, Windows/Deck environment, hardware, input device, language, expected result, actual result, reproduction rate, and the least destructive workaround tried.

Accessibility and audio boundaries

The Store categories include color alternatives, contrast controls, custom volume controls, playability without timed input, stereo sound, and surround sound. These are official capability labels, but they do not prove every mission, monitor, controller, or speaker layout is free of barriers.

Use the current menu to confirm available settings. Report a barrier at the exact screen or interaction, including whether it blocks progression and what alternative input or visual setting was tested. Do not infer voice acting: the developer FAQ says voice acting is not planned and teleprinter delivery is intentional.

Support FAQ

Does IRON NEST run natively on Linux?

No native Linux build is listed, and the developer does not plan official native Linux support at this stage. Steam Deck/Proton compatibility is a separate scope.

Where is the save file?

This hub does not guess. A path should be published only after verification on the current Windows base game, with Steam Cloud behavior and profile structure recorded.

What fixed the crash-related mission problem?

Official PATCH 1.0 (1558) says it fixed save corruption and failure to enter missions after a crash. Update and verify files before attempting a reset.

Is controller support official?

Yes. Steam lists full controller support and DualShock/DualSense support. Device-specific mappings and Steam Input behavior still need testing on the actual setup.

Sources

• Steam Store requirements and feature categories
• Developer FAQ
• Official Steam announcements and patches