Big Walk Connection, Crash & Black Screen Fixes

Fast triage

Big Walk connection timed out or stuck on connecting

This is the most useful concrete launch-week workaround reported in the Steam community. In two threads, players said that a guest who disconnected could still see the session but could not rejoin. The workaround was:

1. Have the host close the game completely, not just return to the title screen.
2. Relaunch the game and load the host's autosaved world.
3. Have the guest join through the new Join Code or the platform friends list.
4. Meet at a named landmark and confirm that everyone can see the same puzzle state before splitting again.

Switching hosts without closing the original host's game may leave the same connection in place. Treat that as a community report, not a universal engine rule; if a clean host restart does not work, capture the exact platform pair, world size and error text for support.

Sources: Steam rejoin workaround · Steam connection-timeout thread · official FAQ

Big Walk black screen, freezes or keeps crashing

Players have reported a black screen with audio still playing, a locked PC after an hour, or a GPU temperature spike in a particular area. These are community reports, not a confirmed platform-wide fault. Work through the reversible checks first:

1. Turn on VSync or set a conservative frame-rate cap.
2. Lower Render Scale before changing every other graphics option.
3. Close overlays and background capture tools for one test session.
4. Watch the GPU temperature while revisiting the same area; stop if the system becomes unstable.
5. Verify the game files and update the graphics driver before trying a fresh host world.

If the machine hard-locks, record the GPU model, driver version, render scale, frame-rate cap, area and whether you were hosting. Do not treat a power-button restart as a fix.

Sources: Steam hard-crash report · Steam graphics-settings discussion

Save missing after a PC crash

The host's world is the important save. A Steam report described a memory-error crash followed by a world that no longer appeared in the load list, even though a file was still present. That may indicate corruption rather than a missing file.

• Stop launching new host sessions until you have copied or backed up the existing save directory.
• Do not delete, rename or overwrite the original file while testing.
• Write down the last successful session, crash message, operating system and whether guests can still see the world.
• Ask official support for recovery guidance; do not download an unverified “save fixer”.

This page intentionally avoids a hard-coded local path: it varies by platform and can change between builds. See the co-op guide for the host-save model.

Since 1.5.1, the in-game save-deletion menu shows the name of the save being deleted, so confirm the name shown matches the world you intend to remove. Deleting a save is not a recovery step for a crash — see Known Issues before removing anything.

Source: Steam save-after-crash report

Mic volume and proximity voice

Start with the boring checks: choose the correct headset input, raise the operating-system input level, check the game's voice setting, and ask the other player to speak from a short distance. Proximity audio is supposed to fade with distance. A walkie-talkie or fixed radio is the intended fallback for a split team.

Independent per-player mic sliders are a recurring community request, not a confirmed missing feature on every platform; 1.5.1 added separate volume sliders for different audio categories, but the notes do not specify which categories are adjustable. Record the platform, headset and whether the issue affects proximity voice, radio voice or both before reporting it.

Source: Steam mic-volume thread

Join or host failures: check the version and the system clock

Two official-FAQ checks often get skipped when a guest cannot join:

• Version numbers only need the first two parts to match. Big Walk versions look like 1.2.3; players can play together when the first two numbers match, so a 1.5.0 and a 1.5.1 client can share a session (the current latest release is 1.5.1). A mismatch in the first two numbers is a real blocker.
• The system clock must be accurate. The official FAQ says a device clock that varies significantly from the online clock prevents both joining and hosting. If you have ruled out the obvious issues, sync the clock on every device before opening a support ticket.

Two 1.5.1 interface changes make failed attempts easier to read: the host-menu password prompt wording changed, and the password prompt shown when connecting is now cleared after a failed attempt — so an empty password field after a rejection is expected, not a new fault. For a guest who never appears in the list, also confirm the host's character is loaded into the world, the host has no connection warning in the lower-left of their screen, and each device has working internet.

Support-ready report template

Copy this into a Steam or support post:

Platform / host:
Platform / guest(s):
World size selected: 2 / 3 / 4+
Puzzle or island area:
Exact error text:
What happened immediately before it:
Did a full host restart change it? yes / no
Render Scale, VSync and frame-rate cap (if relevant):

For broader prevention tips, use Known Issues, Multiplayer Tips and Communication Tools.

Sources

• Official Big Walk FAQ
• Steam Community discussions
• Steam: hard crashes the whole computer
• Steam: connection to host timed out