IRON NEST has an official Steam Deck Verified announcement. The base game still lists Windows rather than native Linux support, and the developer FAQ discusses running through Proton. “Verified” describes the Deck compatibility experience; it does not create a native Linux executable.
2950790, public 1.0, official Deck status checked 2026-08-09. Proton versions and Valve compatibility data can change, so inspect the live Steam page before purchase or troubleshooting.Install the correct product
Confirm the Library entry resolves to base-game AppID 2950790. Demo AppID 4300500 is separate and can have different compatibility history. Install to internal storage or a healthy Steam-formatted microSD card with enough space beyond the 5 GB Store requirement for updates and shader data.
Allow Steam to select the default compatibility tool first. Avoid forcing an old Proton version before testing the Verified configuration.
Check controls in the Nest
Use the official/default layout and walk the station route: teleprinter, map, calculator, requisition, loading, gun controls, arming, and firing. Test focus release and fine adjustment. If a community layout is used, save the default as a comparison.
Touchscreen or trackpad convenience does not replace the need for a complete controller path. Report any station that cannot be completed with the current Verified layout.
Balance readability and performance
The Store’s minimum target is an average 30 FPS at 720p low settings. Deck resolution and power limits differ from a desktop, so begin with the default verified preset. Prioritize readable map text and stable interaction over an arbitrary frame-rate target.
Use the new Motion Blur toggle added in PATCH 1.0 (1558) if screen-shake blur is uncomfortable. Change one graphics or power setting at a time and revisit a consistent mission scene.
Troubleshoot Proton behavior
Update SteamOS, the game, and the selected stable compatibility components. Restart the Deck, verify game files, and return to Valve’s default Proton selection. Remove custom launch options during diagnosis.
If a different Proton version is necessary, record exactly which one, the public patch, and the symptom it changes. A community recommendation without date or hardware context should not become a universal fix.
Save and cloud precautions
The Store lists Steam Cloud. Let synchronization finish before moving between Deck and Windows PC. If Steam reports a conflict, compare timestamps and preserve the newer confirmed progress rather than blindly selecting a side.
PATCH 1.0 (1558) fixed crash-related save corruption and mission-entry failure. Update first, close through normal menus, and do not manually move unknown save files. The Save Support guide keeps paths unclaimed until verified.
Docked and external-device checks
When docked, retest output resolution, controller ordering, and audio device. A second controller or virtual input can change prompts. Diagnose handheld and docked states separately.
The Store lists stereo and surround sound support, but dock/receiver negotiation is system-specific. Confirm SteamOS output and the game’s volume controls before assuming a mission audio bug.
Report a Deck-specific issue
Include Deck model, SteamOS version, game patch, Proton version, handheld/docked state, storage location, controller layout, graphics preset, and exact reproduction. State whether the issue also occurs on Windows when known.
Do not report “Linux broken” when the issue occurs only under one forced compatibility tool. Conversely, Verified status does not make a reproducible station failure invalid; provide the details needed to investigate.
Recheck Verified status after changes
Return to Valve’s live compatibility details after a major SteamOS, Proton, or game update. Reproduce the affected station on the default configuration before rating a regression. A community workaround can be documented with date and Proton version, but should remain optional until it is consistently safer than the Verified default.
When switching between handheld and docked play, finish Cloud synchronization and close the game first. Record controller order and display resolution after docking. If a problem appears only in one state, preserve both results; that boundary is more useful than changing Proton globally and potentially hiding a dock or peripheral issue.