Short answer
Choose your symptom below. The September 26 release adds named crash and grab fixes; the September 17 investigation list is historical. A named fix does not establish that every similar failure is resolved.
Compared September 27, 2026: 1.0.4, 1.0.3 and the September 17 report. No specific resolution identified means these sources do not settle the case; it is not a new developer confirmation that a bug persists.
Named fixes versus unresolved reports
| Symptom | Status | Useful next step |
|---|---|---|
| Loomis arrival, story completion or match loading crashes | Named crash cases addressed in 1.0.4 | Choose the crash stage. A failed challenge without an app crash needs a different check. |
| Xbox graphics option missing or performance changed | Platform settings changed in 1.0.4 | Check Series X versus Series S before resetting settings. |
| Grab too hard to escape at Bloodthirst 3; damage after a terrain-edge escape | Named grab cases addressed in 1.0.4 | Compare the grab symptom; a failed escape alone is not proof of a bug. |
| Shape Jump stuck on cooldown; Killer Sense cooldown lock | Addressed in 1.0.3 | Separate cooldown lock from normal restrictions; record a recurrence on the updated build. |
| Progressive target met; Passive Challenge appears locked after Prestige | Use the 1.0.3 counter checks | Check category, counter and visible completion rather than deleting progress. |
| Thomas: Linebacker; Rachel: Superstitious Tools; Alexis: Craftswoman; Laurie: Quick Thinking | Historical tracking reports; not individually certified resolved here | Compare the current requirement and progress. Changed targets do not settle every older report. |
| Purely and Simply Evil; Pumpkin Smasher; Heavy Handed | No trophy-specific resolution identified | Record the exact award, match role and in-game result; compare the private-host fix separately. |
| Movement lost after a grab; execution after an apparent escape | Named cases addressed in 1.0.3 | Keep a clip of any recurrence and the preceding interaction; do not assume a key binding caused it. |
| Residents on roofs | Historical report; no specific resolution identified | Keep map, building and version details. This is separate from the grab-related fixes. |
Difficult story challenges are a separate category
In the September 17 post, the developer described story challenges as technically completable while reviewing difficulty in Chapter 2/6, Chapter 4/5–6 and Chapter 5/6. That historical statement is not a confirmed universal route. The 1.0.3 progression section does not provide a new house-by-house story walkthrough. Start with the Chapter 2 no-alert guide or Chapter 4 sequence checks.
Other symptoms and community reports
Radio has no prompt
Activation trouble is not the same symptom as a crash when Loomis arrives.
Radio activation checks →Story progress resets
A player report, not a verified universal save-loss cause. Preserve saves; reinstalling is not a proven recovery method.
Chapter guide hub →Cannot sign in
An app that stays open with an access message needs a different path from an app that exits.
Authentication checklist →Party separates
Check installed versions and solo versus party behavior.
Crossplay checklist →Prepare a useful support report
Use the support contact in the official update above. Include username, platform, device specifications and the actions before the failure. Add your build, exact objective or error, and whether it repeated. Remove private account details from any public screenshot; do not send passwords or login codes.
Does investigating mean there is a workaround?
No. It identifies a known symptom, not a proven workaround or a release date. We link the closest diagnostic guide without promising a fix.
Why does an older patch say fixed?
An older note can address one case while a later report identifies another. Match the named issue and build rather than assuming a whole category is resolved.