What players are hitting at launch

1 · Co-op connection problems

The loudest launch-window complaint, aggregated across Steam discussions and third-party troubleshooting round-ups, is multiplayer connectivity. Reported symptoms include:

• Public server browser showing no lobbies, or the host's session not appearing.
• Steam friend invites doing nothing — "Join Game" clicks with no result.
• Connection timeouts and infinite loading screens when trying to enter a co-op world.
• Occasional client crashes specifically when joining or entering multiplayer.

Most of these are networking and version-sync issues rather than a broken game. The workarounds players report actually working, in order:

1. Verify game files on every PC. A desynced or corrupted networking file is the cheapest explanation. Steam → Properties → Installed Files → Verify integrity of game files, then restart Steam.
2. Confirm everyone is on the same build. A small hotfix landing on one client but not another can break co-op before you realise the clients differ. Steam normally auto-updates, but check.
3. Match Steam download regions. Set the same region (e.g. US – Chicago) for the whole group under Settings → Downloads, then restart Steam and re-host.
4. Skip the public browser; invite via the Steam Overlay. Host enters the world, presses Shift+Tab, and right-clicks the friend → Send Invite. Several players report this is far more reliable than the in-game browser at launch.

2 · Crashes, black screens and Unreal Engine errors

The second cluster is startup and in-session instability: crash immediately after pressing Play, black screen (sometimes with audio), and Unreal Engine fatal errors. Community-aggregated workarounds, all standard UE fixes with no official fix confirmed yet:

• Force DirectX 11. Add -dx11 to the Steam launch options (Properties → General → Launch Options). DirectX 12 is the usual suspect for pre-menu crashes on certain driver/hardware combos.
• Clean-install the latest GPU driver. Use the manufacturer's installer with the clean-install option; don't rely on Windows Device Manager.
• Disable overlays. Steam, Discord and GeForce Experience overlays can conflict with the engine at launch.
• Run as administrator and, if you see a black screen with audio, press Alt+Enter to drop into windowed mode, then switch display mode to Borderless Windowed in-game.
• Clear the shader cache if crashes correlate with specific effects (blizzards, campfires).

3 · Save stability (developer-framed risk)

Save and progression reliability was named by the developer as a known Early Access risk before launch, and it remains the single most important thing to protect yourself against. Practical habit: back up your save file after any milestone, and expect Early Access builds to churn. We will log any official save-related fix on the changelog the moment it ships.

4 · What we are watching (no confirmed cluster yet)

We are tracking a few categories where reports could consolidate but have not yet formed a clear pattern. We list them so you know where to look, not because we have seen proof:

• Controller support. No clear cluster of controller-specific complaints has surfaced in the first hours. If you hit stick/button mapping or recognition issues, that is worth reporting on the official Discord so it gets onto the studio's radar.
• Localization gaps. The pre-launch patch touched localization; we are watching for region-specific text or audio issues as more non-English players come online.
• Performance in whiteouts. Heavy weather loads are the usual frame-rate risk near minimum spec — a developer-framed concern, not yet a confirmed widespread complaint.

5 · Community-reported gameplay bugs (separate from crashes/co-op)

Beyond connectivity and stability, the first day-and-a-half of player reports clusters around a handful of gameplay defects. None are confirmed by the studio yet; we list them so players know what others are hitting, and so the pattern is visible. Severity below is our read, not an official rating — and every game-mechanic value stays unmeasured on this site.

• Vanishing crafted items (high severity). Multiple reports describe a finished craft disappearing while still consuming its materials. In a scarcity-focused game this is the most damaging class of bug we have seen reported — it hits the core resource loop. Treat any expensive craft as risky until the studio confirms a fix; consider crafting in small batches and backing up your save afterward.
• Bridge collision / display bug. A recurring complaint: a broken bridge near the starting settlement shows as intact at night (or after using a flashlight), then drops the player through on crossing — and the new-player quest reportedly gates on that bridge. This is a progression-blocking frustration, not just a visual glitch.
• Key / door interaction bug. At least one report describes the church-rooftop key vanishing on pickup, leaving a quest step uncompletable. We are watching for more reports before calling it widespread.
• Building placement friction. Players report furniture cannot be nudged without full demolition, inward/outward placement arrows are unclear, and some placeables (e.g. a candle) are visible only to the owner and do not sync in co-op. Annoying rather than blocking, but it erodes the base-building loop the game leans on.
• Dog pathfinding. The companion can get stuck behind doors or struggle with stairs — consistent with afleurdenet’s "occasional babysitting" note. Manageable, but worth reporting if it strands your dog in a dangerous spot.

Two softer notes appeared often enough to mention: movement feel described as "sticky" or unresponsive (subjective, likely to improve with patches), and a "map feels small" sentiment from players who have already circled the starting region. Both are early-access expectations, not defects — but they tell the studio where the first content/update pass should land.

What was already addressed before launch

Context matters: the launch was delayed by several hours specifically to fold in feedback and crash reports from a second playtest that ran until 6 October 2026, and a pre-release patch covered movement key rebinding, performance, co-op and localization fixes (reported via Game Spark). So some of the obvious day-one issues were already being chased before the doors opened. That does not mean the build is clean — it means the studio was already in fix mode, which is the right instinct for an Early Access title.

Official channels (use these, not trainers)

The fastest path to a real fix is the studio's own channels. The Steam news hub is where patch notes and the weekly "Signal" dev-blog land; the official Discord (discord.gg/toplitz) is the named feedback hub. Report with your build version and steps to reproduce — that is what turns a "it crashed" post into a fixed bug.