Treat a fast-travel crash as a loading-boundary problem only when the save still opens and the same beacon-to-destination transition fails again. Record both endpoints, test the identical route after updating with Frame Generation off, and compare it with respawn and ordinary Continue loading. If the save cannot enter the world from any route, stop this checklist and use the backup-first recovery guide.
Four tests that isolate the failing boundary
Keep the start point, destination, build and settings fixed while changing only the way the world is entered.
Repeat the exact start beacon and destination once after the update. Record whether it fails at the same point.
From the same start beacon, choose another destination. This separates one destination from all fast travel.
Note whether a respawn also crashes. Do not force a death if important unsaved progress is at risk.
If ordinary loading also fails, preserve SaveGames and switch to the recovery guide.
How this was checked
Evidence and limits
Method: Built a route-isolation worksheet from the Week 1 crash and softlock notes, the official known-issues report format, and the launch-week Steam thread that groups beacon, respawn and loading symptoms.
Evidence boundary: The shared loading boundary is an observed symptom cluster, not a confirmed common engine cause. This page does not diagnose save corruption from one travel crash.
Read the full editorial standard →Do this first
- Confirm the save opens normally, then record the starting beacon, destination and installed build.
- Install pending updates and verify the Steam files.
- Turn Frame Generation off, reload as required, and repeat the identical travel route once.
- Compare another destination from the same beacon and note whether respawn also fails.
- If ordinary Continue or Load now fails, close the game and switch to the backup-first recovery guide.
- Report the exact endpoints, failure timing, build and comparison results.
What the Week 1 Update changes
The patch notes name crash fixes for save loading and shutdown, change interrupted-save writes and repair several progression softlocks. Re-test the same transition on the updated build before using an older workaround; a remaining crash should be reported as a post-Week-1 issue.
Why these crashes are grouped
Players have reported crashes while loading a save, interacting with beacons, respawning and fast travelling. These actions all cross a loading boundary, but that does not prove they share one technical cause. The page therefore compares entry methods rather than prescribing a save-file edit.
When this stops being a travel-only problem
If Continue, Load, respawn and fast travel all fail, further route testing no longer isolates the problem. Close the game, preserve the complete SaveGames folder, and use the dedicated recovery guide. Keeping that procedure on a separate page prevents a travel symptom from being mislabeled as corruption.
- Do not repeatedly force-close while the save indicator is active
- Do not overwrite the only remaining save copy
- Do not start a new game in the affected slot before preserving files
Read the four-test pattern
If only one destination fails, report that route and avoid it temporarily. If every fast-travel destination fails but ordinary loading works, report the beacon interaction path. If fast travel, respawn and Continue all fail, preserve the save before further experiments. This progression creates a more useful report without claiming access to the game's internal crash cause.
- One destination only: route-specific evidence
- All travel destinations: fast-travel interaction evidence
- Travel plus respawn: broader loading-boundary evidence
- Continue or Load also fails: leave this page and protect the save
A useful bug report
Include platform, PC hardware where relevant, build string, exact starting beacon, destination, crash timing, whether another destination works, whether respawn works, and whether the save opens through Continue. The official bug-report format asks for location, build and reproducibility; this worksheet supplies the missing comparison detail.
Evidence log
Sources checked
External sources are linked for verification. Community reports describe symptoms and are not treated as universal fixes.
CommunityFrequent crashing discussionDocuments the launch-week loading, beacon, fast-travel and respawn symptom cluster.
↗OfficialGlobal release known issuesOfficial acknowledgment of crashes and the Recover Save path.
↗PlatformThe Week 1 UpdateCurrent save-loading, shutdown, crash and softlock changes.
↗Found a build mismatch?
Help keep this page current.
Send the page URL, platform, pause-menu build string, and a reproducible observation through the corrections desk. Game bugs still belong in the official developer channels.
Open corrections guidance →