Support

IRON NEST Controller Support

Set up and troubleshoot IRON NEST controllers, Steam Input, prompts, station focus, sensitivity, and device-specific bug reports.

Steam lists full controller support for IRON NEST AppID 2950790, including PlayStation controller categories. Because the game uses many physical stations, troubleshoot the exact failed interaction rather than reducing the whole profile to “works” or “does not work.” Current on-screen prompts and Settings are the binding authority.

Game: IRON NEST: Heavy Turret Simulator. Scope: Windows base-game public 1.0, checked 2026-08-09. Controller models, firmware, Steam Input layouts, and remaps vary; fixed button charts are intentionally omitted.

Begin with one device

Disconnect duplicate pads, wheels, virtual controllers, and unused adapters. Start Steam with the intended controller connected, launch the base game, and inspect Settings. Confirm interaction, back/release focus, movement, camera, and menu submission.

Test first in a non-critical state. Walk between stations, focus a lever or wheel, release it, open the tactical map, and exit cleanly. Record which prompt appears.

Decide how Steam Input participates

Open the game’s Steam controller settings and note whether Steam Input is enabled, disabled, or using a community layout. Change only one layer at a time. A remap in Steam plus another in-game remap can make troubleshooting opaque.

Return temporarily to an official/default layout when isolating a fault. Export or screenshot a customized layout before resetting it.

Tune station motion

IRON NEST mixes ordinary look movement with focused mechanical adjustments. Set look sensitivity for comfortable navigation, then test coarse and fine gun movement. A setting that feels good in the room can overshoot a bearing dial.

Release the focused control and re-read the value. If camera motion stops only while a station is focused, use the displayed exit action; that can be intended state rather than a lost controller.

Fix wrong or flickering prompts

Prompt flicker often indicates another input source. Remove the mouse movement, virtual pad, or second controller that is competing. Restart with one device and compare main-menu prompts with mission prompts.

If a PlayStation controller displays generic labels, check the current Steam Input configuration and cable/wireless mode. The Store’s support categories establish compatibility, not a guarantee that every platform glyph appears under every remapping layer.

Diagnose one broken station

Name the station, focused state, expected action, displayed prompt, and result. Verify prerequisites: a loading lever may be locked by mechanical sequence, elevation by breech/load state, and firing by arming. Test the same input in another menu to separate device failure from interlock.

PATCH 1.0 (1558) improved mouse movement after loading the menu or mission. If controller and mouse focus both fail, update and verify files before changing saves.

Build a useful controller report

Include controller model, connection type, firmware, operating system, Steam Input state/layout, in-game remaps, public patch, station, and concise steps. State whether keyboard/mouse can perform the same action. Attach a short video if it reveals prompt switching, but review it for private information.

Avoid recommending third-party driver executables as a universal fix. Official firmware, a wired test, one-device isolation, and file verification are safer first steps.

Steam Deck boundary

The game has an official Deck Verified announcement, but Deck uses its own Steam Input and Proton environment. Use Steam Deck Support for that platform. Deck verification does not establish native Linux support.

Retest after remapping

Run one complete low-risk shot after any layout change. Menu navigation alone cannot prove map tools, fine elevation, arming, and newspaper submission are reachable. Keep an emergency way to restore the default layout, and change one binding at a time so a conflict has a known cause.

Also test text entry or search fields used by any linked leaderboard interface separately from mission controls. A layout that fully operates the Nest may still need an on-screen keyboard workflow. Describe that distinction in a report rather than calling the entire controller profile incomplete. Keep the mission and online-service observations separated.

Retain the controller layout export or screenshot with the report so another operator can reproduce the same input layer and station sequence.

Sources

Continue with another focused IRON NEST guide.

Support

IRON NEST Accessibility and Comfort

Configure IRON NEST color alternatives, contrast, volume, timed-input comfort, motion blur, controller, stereo, and surround support.

Support

IRON NEST Crash Troubleshooting

Troubleshoot IRON NEST crashes, black screens, frozen input, and mission-entry failure using patch-aware, save-safe steps and useful reports.

Support

IRON NEST Performance Guide

Tune IRON NEST performance from official minimum and recommended targets using controlled graphics changes, thermal checks, and reproducible reports.