Welcome to Elderfield Steam Deck Launch Help

Quick answer: Install the latest Steam update—v1.0.2 plus the September 23 Hotfix, checked October 2—then use Full Screen ON and Stretch Screen OFF, the developer's v1.0.1 Deck baseline. For a launch failure, the support checklist lists Proton 9.0-4 or 10.0-4. Test one change at a time and match it to the failure point.

Verified is the current compatibility status, not a diagnosis

Steam currently labels Welcome to Elderfield as Steam Deck Verified, and the developer announced that result on August 28. That gives a player a clear purchase and compatibility answer: the Steam release has passed Valve’s current Deck review. It does not mean every launch failure has the same cause, nor does it turn a pre-release or non-Steam build into the supported Steam installation.

Begin by confirming what you installed. This guide concerns the Steam store version of Welcome to Elderfield, not an older Demo build, a copied Patreon build, or a manually added non-Steam shortcut. Those installations can use different folders, compatibility settings, and update paths, so they should not be diagnosed as though they are the same program.

If the game opens and runs but stutters, use the game’s settings and report the exact location and effect rather than applying the splash-screen workaround below. The developer has separately noted that individual devices can see frame drops, which is a performance question rather than proof that the game cannot launch.

Keep the documented Deck settings on the latest build

The v1.0.1 notes describe substantial Steam Deck performance improvements and give two explicit display settings: turn Full Screen ON and Stretch Screen OFF. Restart the game after applying them, load the same save, and revisit the same location. Comparing one route before and after the change is more useful than judging performance in two different maps.

These settings address performance after launch. They do not diagnose a window that never opens, a crash after the Kwalee screen, or one damaged save. If the game reaches the menu but one map still stutters, record the map, weather or visual effect, frame-rate range, and whether the problem appears on a new save. The update fixed several fog, dust, radio, and storage crash paths, but it does not promise identical performance in every scene.

Check the exact failure before changing Proton

The developer’s Proton instruction is narrowly tied to a Steam Deck report where the game crashed after the Kwalee splash screen. First launch the game once and note what actually happens: does it fail before a splash screen, close after that screen, reach the title menu, or load a save and then stop? A precise symptom determines whether this workaround even matches your problem.

Also note whether you are launching the full game or the Demo. The two have separate Steam entries, and mixing them up can make an old shortcut look like a current installation failure. Keep a screenshot or short note with the Steam Deck model, SteamOS version, the game version, and any on-screen error before changing settings.

This small record is not bureaucracy. It gives you a clean way to undo a test, compare results after an update, and write a useful report if the launch still fails. It also prevents a well-meant compatibility change from being mistaken for a confirmed solution to a completely different crash.

Try a listed Proton version for a launch crash

For the specific after-splash-screen crash described above, open the game’s Steam Properties on the Deck, go to Compatibility, enable the option to force a Steam Play compatibility tool, and select Proton 9.0-4. A developer reply identified that version for the original report; the current pinned support checklist also names 10.0-4. Launch once with one listed version and record whether the last visible screen changes before testing the other.

Do not change several settings at once. Test this one compatibility change before altering controller layouts, deleting configuration files, moving saves, or installing community fixes. If Proton 9.0-4 solves the exact splash-screen crash, leave a short note of the date and game version for yourself; a future update may change the best setting.

If neither listed version is available or both fail, restore the previous selection instead of cycling through random releases. Use the general launch guide to check the update, stuck nw.js process, and installation without deleting save data.

Protect your save while you troubleshoot

Changing the compatibility tool is a reversible launch setting. Deleting files, overwriting cloud data, or repeatedly reinstalling without identifying the failure is not equivalent. Before doing anything that could affect a save, make a note of the affected slot and stop if Steam reports a cloud conflict you do not understand.

Avoid copying advice intended for a Patreon or non-Steam build. The developer’s old instructions for manually added builds involve separate paths and are not a reason to move a Steam-store save. If you need to reinstall after a confirmed file problem, check the official Steam status first and preserve enough information to say whether the issue happened before or after the reinstall.

For a problem that occurs only after loading a particular save, do not assume Proton is the cause. Record the save slot, location, task, and error message if one appears. That turns an otherwise vague crash report into something the developer can compare against a reproducible state.

When and how to report the problem

Use the official Steam discussions or bug-report area after you have tested the one matching workaround. Include the exact launch point, whether Proton 9.0-4 was selected, whether the game is the Steam release or another build, the game and SteamOS versions, and any visible error. A screenshot of the compatibility setting is more helpful than a long list of unrelated fixes you tried.

Do not report the game as “not Verified” merely because one setting failed. Verified is Steam’s current status; a specific failure can still be real and worth reporting with good evidence. Likewise, do not promise other players a Proton change will solve stutter, a controller issue, or a crash in a different scene.

For the broader question of which hardware is officially supported, see Platform Status. For Windows hardware rather than Steam Deck troubleshooting, use PC System Requirements.

If the crash coincides with an achievement

v1.0.2 adds a potential fix for an achievement-unlock crash when the Steam connection fails. If that is your exact trigger, update and confirm Steam connectivity before changing Proton. Read the current patch guide and record the achievement if it still crashes. This October 2 patch review does not claim a new Deck benchmark or replace the earlier display-setting evidence.

Sources and version boundary

Steam Deck Verified status, v1.0.1 guidance, and the support checklist were checked on September 19, 2026 through the Steam store page, official announcements, and the developer's pinned launch thread. The Proton 9.0-4 step is also supported by a developer reply to a Deck splash-screen crash.

That reply supports one symptom and one fallback, not a universal performance or crash guide. If a future announcement changes the recommended Proton version, the newer first-party instruction should replace this page’s dated guidance.