Check the patch before repeating a broken checkpoint

The developer’s Patch 1.1.2 announcement covers checkpoint black screens, voice recovery after a Vivox outage, lighter shader compilation and a DX11 launch option. Check the installed update before following an older workaround. A published fix describes the intended behavior; it does not diagnose your current session.

Source: Official Patch 1.1.2 announcement

Choose the right branch of the problem

What you can seeWhat to record first
Loading stops at a black screenCheckpoint, whether both players are affected, and installed version.
The level loads but speech is missingWhich direction of voice fails and whether it began after reconnecting.
A door or puzzle stops respondingChapter, object and the last action by each player.
The game fails before you can joinPlatform, launch option and exact message.

Chapter fixes worth recognizing

The notes include high-latency door fixes in Chapters 1, 2 and 4; disappearing fuses in Daphne’s Lab; a Chapter 5 vent-related softlock and plant-pot issue; and several Chapter 7 push-block and room-lock problems. Those are specific cases, not a promise that every closed door is a bug.

Source: Chapter-specific changes

Pause before changing the puzzle state

If one player is stuck, ask the other to describe their view before either repeats actions. A short record of both positions can help distinguish a missing step from a synchronization problem. Avoid restarting a chapter immediately if doing so would erase the only clear reproduction of the issue.

  1. Have both players identify the current chapter and last checkpoint.
  2. Record what each player can interact with.
  3. Note the last successful action and the first failed one.
  4. Check the current patch and the matching official fix.
  5. If it remains blocked, preserve a clip or screenshots before restarting.

Use DX11 as a controlled comparison

Patch 1.1.2 adds DX11 as a launch option. If your problem is compatibility at launch, you can compare the game’s offered launch options and record which one was used. Do not add undocumented command-line flags or treat this option as a universal fix for a puzzle or microphone problem.

When comparing, keep the same graphics settings where possible. Record whether the game opens, whether shader preparation finishes and whether the same checkpoint loads. A better result on one machine is not a benchmark for everyone.

Source: Official launch-option change

Build a useful support report

Include both players’ platforms, game versions, chapter and the exact time the failure occurred. For voice, say whether neither player can hear or only one direction fails. For a puzzle, describe the relevant object and both players’ last actions. The official launch post links the developer’s support and Known Issues pages.

This page contains troubleshooting structure, not puzzle solutions or a verified list of currently unresolved bugs. Check later announcements before assuming the October fixes are the newest changes.

Source: Official news and support links

More for this game

We Were Here Tomorrow Wiki We Were Here Tomorrow co-op: crossplay, microphones and a first-session plan

Sources & scope

This article uses the official and individually identified community references linked below. It is not a hands-on review. Screenshots are credited to their original publishers; they are not evidence that we tested these steps. Game details can change after publication.

Sources checked: 26 Oct 2026. Read how we use sources and AI assistance.