We Were Here Tomorrow Not Loading: Fixes by Symptom

The official start-up guidance points at three causes: missing Windows Media Packs, an unsupported GPU, or corrupted files. Install the media feature pack if your Windows build does not include it, confirm your card meets the GTX 1660 Ti minimum, then verify the game files through Steam.

One player-reported workaround is capping the frame rate at 60, which the support page acknowledges as something "some players reported" helped. Try it before you reinstall anything.

If the game never reaches a menu at all, go to the crash section below rather than this one: a black screen that persists is a launch failure, not a loading failure.

On Windows the media component is an optional feature rather than a default install on some editions, which is why a clean system can fail here while a used one works. Check it before you spend an hour on drivers.

This was the most common launch bug and it is fixed. Patch 1.1.2 lists a black screen when loading checkpoints as resolved, so if you are seeing it, confirm your build is actually updated rather than assuming the fix failed.

On Steam, the client updates automatically unless you have paused updates or are offline. On console, check for a pending download in the console's update queue.

If you are on an older build deliberately, the workaround was to reload the checkpoint from the main menu. That still works, but the patch removes the need.

Symptom: floors, walls, terrain and objects pop in and out as you walk, or the world is simply missing around you. The official guidance is to verify file integrity first, then do a full uninstall and reinstall, including the install directory.

Patch 1.1.2 lists "part of the world content not loading" as fixed, and notes that reinstalling used to solve it. If you are patched and still seeing it, the reinstall step is the remaining option.

Reports of this cluster were still appearing on the subreddit in late October, so treat a single recurrence as a known residual issue rather than a new problem.

The voice system runs on a third-party backend, and the official known-issues page admits the servers had an emergency maintenance window. That is why the studio's patch notes apologised specifically for the "unexpected voice server outage".

Patch 1.1.2 also fixed voice not reconnecting after the servers came back, and the walkie-talkie sometimes disappearing. If your radio interface is missing, reload the checkpoint first.

Avoid campus and public networks. The support page warns that those networks often have protections or bans that block the voice servers, which is a different failure from a broken microphone.

The official recovery route is short: return to the main menu, choose change, click start new journey, and let the host manually re-select the last checkpoint. That keeps your chapter progress and is faster than replaying a section.

Patch 1.1.2 fixed several specific softlocks, including the Chapter 5 hook-gun route through a vent, a Chapter 5 floor hole, and a Chapter 7 test-room door that could trap a player.

Chapter 7 checkpoint reports were still appearing on the Steam forum on October 26, so the recovery route is worth knowing even on a patched build.

The official crash article gives an order rather than a single fix. Turn off VSync, both in the driver and in game; if you cannot reach the menu, edit the configuration file in the game's StreamingAssets folder. Check that your system time zone is correct. Then switch to DirectX 11 by adding the launch option -force-d3d11.

Next, run the game as administrator, verify files through Steam, and unplug unnecessary USB devices while disabling Discord, Steam and MSI Afterburner overlays. The support page specifically warns against campus and public networks because they can block the voice servers.

If it still crashes, the advanced steps are a clean GPU driver reinstall with DDU, restoring the card to stock clocks, forcing a laptop onto its discrete GPU, and clearing the shader cache directories under your local app data folder.

The official known-issues page has a "feature not bug" section, and it covers most of the false alarms. Temporal anomalies only respond when you stand directly in front of them, not from the side.

Goop block stacks sometimes cannot be climbed from one side, and walking around to the other side is the fix. Proximity voice means you hear your partner directly when close, with the walkie-talkie only appearing once you are out of range.

And most challenges have more than one solution, so a route that fails is not necessarily a broken puzzle. If you are reporting a bug, check these four first, because each one produces a report the studio has already answered.

The official support site keeps separate known-issue pages per platform, and we have only read the PC one in detail, so a console problem may be documented elsewhere. Check the page for your platform before filing a ticket.

The Discord has a bug-report channel, and the Steam forum has a Bugs and Feedback section with 40 active topics at the time of checking. Both are read by other players faster than by the studio.

When you report, include your platform, your patch version, the chapter and checkpoint, and whether voice or video failed. That is the difference between a report that gets an answer and one that gets a reply asking for the same details.

Add a screenshot of the checkpoint name if you can. The chapter numbers are used loosely in the notes, and a visible checkpoint name is the only identifier everyone agrees on.