Skip to content
We Were Here Tomorrow

Launch Day Known Issues & Fixes

Launch-day issues reported by players — a door only the host can open, invite black screens, mic drops — with safe community workarounds and patch status.

Updated October 20, 2026Published October 20, 2026

Quick Answer: Is We Were Here Tomorrow Buggy on Launch Day?

Partly. The game launched on October 20, 2026, and the first hours of Steam player reviews describe four recurring trouble spots: a first door only the host seems able to open, invites that hang on a loading or black screen, walkie-talkie audio dropping mid-session, and lost progress after disconnects. None of these stop everyone — plenty of pairs are playing through — but if you hit one, it is not just you. Everything on this page is aggregated from launch-day player reports on the Steam store; workarounds are community-suggested, not official fixes, and this page updates as Total Mayhem Games ships patches.

Quick Answer: Is We Were Here Tomorrow Buggy on Launch Day?
IssueWhat players reportStatus
First door host-onlyOnly the hosting player can push the opening door; the partner's input does not registerMost-reported launch issue; no official fix announced yet
Invite black screenJoining a partner hangs on a loading spinner or black screenReported by multiple pairs; restart + re-invite helps some
Mic / walkie-talkie dropsVoice cuts out, partner cannot hear, or audio bleeds into other sessionsMixed: some is device setup (see our voice chat page), some is a game bug
Disconnect progress lossA disconnect late in the game rolls back a large chunk of progressSave behavior unconfirmed; treat chapters as checkpoints
Before troubleshooting anything, let a first-launch shader compilation finish on both PCs — interrupting it looks exactly like a hang.

"Only My Partner Can't Open the First Door"

The most-reported launch-day issue: at the very first door, only the hosting player can trigger the push interaction — the joining player holds the handle, the animation starts, and they get bounced out or nothing happens. Four independent early reviews describe the same failure. It is a progression blocker when it hits, because the door is the tutorial's first gate. What players report helps: the host pushes the door alone first (the partner does not need to hold it), and if the interaction still fails, save, fully restart the session and re-invite. One early reviewer confirmed getting through after retrying; others were still stuck at the time of writing. This has the shape of a day-one patch item — we will update this page the moment an official fix lands.

Invite Loads Forever or Shows a Black Screen

Several pairs report that accepting an invite leads to an endless loading spinner or a black screen instead of the session. Community-suggested order of operations: have the host re-send the invite rather than re-accepting the stale one; if that fails, both players fully restart the game (not just the overlay); on PC, verify the game files through Steam and let the first-launch shader compilation complete on both machines before inviting. Console pairs should confirm both systems are signed into the platform's online service before blaming the game. If invites accept but never connect at all, the crossplay guide's platform checklist rules out account and network causes first.

Walkie-Talkie Audio: Drops, Silence and Cross-Talk

Three distinct audio problems show up in launch reviews, and they have different fixes. First, mics that stop transmitting mid-session: players report rejoining the session restores voice — annoying but recoverable. Second, a partner who cannot hear you at all: that is usually device-level (the platform default input is not your headset), and the voice chat page walks the per-platform fix for Windows, PS5 and Xbox. Third, the strangest one: walkie-talkie audio bleeding into other players' sessions, described by one reviewer as hearing strangers. That last one is a server-side bug with no user-side workaround — it belongs in a patch, and it is worth reporting to Total Mayhem Games with the time it happened so they can trace the session.

First Launch: Shader Compilation Is Not a Freeze

Multiple launch-day reviews mention long waits at first startup while the game compiles shaders — one player quipped about waiting for a friend who was still compiling. This is normal first-run behavior on PC, and interrupting it is the fastest way to create the hangs described above. Let both machines finish their initial compilation before the first invite; subsequent launches are quick. If the compilation appears stuck for more than roughly fifteen minutes with no disk activity, a restart is reasonable — otherwise, wait it out.

Disconnects and Lost Progress: Treat Chapters as Checkpoints

The costliest report so far: a player who finished the game, disconnected, and found a large chunk of progress rolled back — there is no auto-save catch-up after a drop, per early accounts. Until save behavior is confirmed (or patched), the practical play is: treat each chapter transition as your checkpoint, re-invite promptly after any disconnect rather than finishing the puzzle, and do not close the game immediately after a disconnect — the client may still be writing state. If you lose progress, report it to Total Mayhem Games with the chapter you were in; concrete save reports are what push save fixes up a patch list.

How This Page Updates

Everything above is aggregated from public launch-day player reports on the Steam store, checked October 20, 2026 — we link what players say, not what we wish worked. As Total Mayhem Games ships patches (the store page news feed is the fastest official channel), each issue here gets re-checked and marked fixed, improved or still open. Pages on this site carry their last-updated date; if a workaround here stops being necessary, this page is where the correction lands first. Spoiler-free by design: no puzzle solutions appear on this page, so it is safe to consult before you play.

Published October 20, 2026 · Last updated October 20, 2026

Other Guides