Preserve the evidence window
A restart can replace the log from the crash you want to describe. Mobius requests the Unity Player log and any crash files provided by Unity. This guide only helps collect evidence; it does not diagnose the fault or establish that a driver/mod caused it.
| Situation | Do this first | Why |
|---|---|---|
| Game just crashed | Do not relaunch until you copy Player.log | Developer says the log is overwritten at every launch |
| Crash repeats | Save each run's log under a timestamped filename | Separates evidence across attempts |
| No log at expected path | Check Windows user/profile and install context | Do not borrow another OS path |
| Sharing with support | Review paths/usernames and attach only requested evidence | Logs can disclose local identifiers |
References: Mobius Digital: Outer Wilds support and corrupted-save recovery
Prepare a focused PC report
Mobius lists the Windows Player.log location and directs players to send it with relevant Unity crash files. Include the action and time that preceded the issue; do not send an entire user folder or unrelated account data.
- Record Windows version, storefront, game build if visible, hardware basics and the exact action/location before the crash.
- After the crash, leave the game closed and copy C:\Users\<username>\AppData\LocalLow\Mobius Digital\Outer Wilds\player.log to a separate evidence folder.
- Copy any crash report files that the game/Unity crash handler generated, without editing the originals.
- Open copies only to review; redact your Windows username, local paths or unrelated information before posting publicly.
- Send the focused report to Mobius using the contact route currently listed on its support page.
- If you already relaunched, state that the earlier log may have been overwritten; do not present a later log as the crash log.
References: Mobius Digital: Outer Wilds support and corrupted-save recovery · Outer Wilds Steam Community Discussions
Before you play
- Game stayed closed until the log copy was made.
- Player.log came from the matching Windows profile.
- Crash report is tied to the same attempt.
- Personal paths are redacted before sharing.
- No cause is claimed without evidence.
Frequently asked questions
Can I capture the old log after I relaunched?
Mobius says each launch overwrites Player.log, so the previous crash context may be gone.
Does this apply to console?
No. The directory is a Windows PC path.
Does this send my report automatically?
No. This worksheet stays in your browser and cannot read or transmit files.
Sources & revision notes
Editorial revision: November 7, 2026; not a gameplay test date. The reference notes identify source limits and version differences.
- Mobius Digital: Outer Wilds support and corrupted-save recovery (Official)
Mobius documents PC save backups, recovery prompts, profile folders and Steam Cloud precautions, and notes that Unity Player.log is overwritten every time the game is launched. Instructions are platform/store specific; do not apply Windows paths to console or Mac.
- Outer Wilds Steam Community Discussions (Community)
External player-created Steam discussions. Treat reports as anecdotal, match Steam/Epic/platform and save symptoms, and do not download unsolicited save files or utilities.
November 7, 2026: first publication, focused Mobius's log-overwrite warning into a pre-relaunch evidence checklist. No crash was reproduced.
How we research and correct guidesNo affiliate links or paid placement. Commercial disclosure.