Current official status at verification
The August 30 review checked the official Steam news chronology for App 3312250 and found no Patch 0.05.008 or higher announcement. Patch 0.05.007 is the current build reference at the displayed verification time. A version label does not prove every system works on every configuration, and it must be checked again when the developer publishes another update.
The AMD FSR Frame Generation crash is marked resolved, but Frame Generation itself is temporarily disabled while the cause is investigated. Standard FSR remains available, and the developer explicitly says there is no need to delete the settings save. That temporary feature state is different from an unresolved crash and must remain visible.
Fixed in PATCH 0.05.007
The developer marks the AMD Frame Generation crash fixed and also repairs Steam invites, lobby searches, other networking features, Endless Mode cross-mode map switching, the new main-quest notification for clients, the negative session player count, and the death screen that could appear after a completed mission.
ABSOLUTIST and GRINDER are fixed, along with the Armored Ghoul head and the Goddess transforming players before a match or in the hub outside the Red Cursed Hub. These are named fixes for 0.05.007, not a promise that every graphics, network, achievement, or enemy behavior is resolved.
- AMD FSR Frame Generation launch crash: fixed in 0.05.007.
- Steam invites, lobby searches, and networking features: fixed in 0.05.007.
- Endless Mode cross-mode map switching: fixed in 0.05.007.
- ABSOLUTIST and GRINDER: fixed in 0.05.007.
Triage an unexpected result safely
First separate launch or performance problems from gameplay misunderstanding. Record operating system, hardware, build or update time, mode, party size, reproduction steps, and visible message. Restart only after saving what can be observed. Avoid deleting saves, configuration, or system files as an early step. This guide does not authorize destructive recovery actions.
Compare the visible build with the latest patch note, then repeat only when repetition is safe. If behavior occurs during a spell, generator, lobby, or bunker interaction, verify the current in-game description before diagnosing it. One surprising result may reflect procedural context, connection conditions, local security software, or misunderstood feedback rather than a game defect.
- Record the August 30 verification boundary and installed build.
- Capture the exact visible message without paraphrasing it.
- Write minimal reproduction steps and whether solo or co-op was used.
- Check official Steam announcements before relying on reposts.
- Prefer reversible tests and preserve local data.
Current community reports and questions
The August 30 evidence still leaves the Windows 11 required-file blocking report at community level. It is too limited for a dedicated Windows route. Multiplayer intent is different: 0.05.007 now supplies first-party Steam invite, lobby-search, and networking fixes, while 0.05.005 supplies version and disconnect evidence, so the focused multiplayer troubleshooting page can publish without claiming undocumented product behavior.
Use those discussions as discovery signals. Look for the installed build, exact message, configuration, reproduction steps, and independent matching observations. A popular or recent post can still describe a local setup, an incomplete diagnosis, or a state changed by a later patch. Link the origin when discussing it and keep the attribution visible.
What Patch 0.05.005 still records
Patch 0.05.005 explicitly records missing string values, a cat extraction animation problem, a player-dragging animation problem, and an interaction hint that could remain visible after a player left an object. HOTFIX 0.05.006 reports several text repairs but does not say every missing value or every animation item is resolved. The older statements stay attached to their source until a later official note clearly replaces them.
The same 0.05.005 post contains many fixes, balance changes, and quality-of-life changes that are not issue entries. Read the patch-notes hub for the full scope. This page extracts only what helps a reader understand evidence status and avoids turning a long update into a speculative defect list.
Earlier fixes remain in patch history
Hotfix 0.05.006 fixed spell purchasing, CHOPPER dead-player behavior and pathfinding, a Day 3 B.O.S.S. departure progression case, and the host-only DOUBLE TAP award result. Patch 0.05.005 supplies version mismatch, disconnect-reason, Private and Solo lobby, equipment, spell, enemy, shop, quest, and mode changes.
A newer patch does not erase those records. It changes only the subjects it addresses. The patch ledger keeps each source in descending chronology so an old report can be compared with the build that fixed it without being repeated as a present official problem.
Prepare a useful official report
A useful report is concise and reproducible: build context, platform details, mode and party size, location or system, steps, observed outcome, expected outcome, frequency, and non-sensitive media if appropriate. Remove personal information. Check the official developer or Steam channels for the preferred reporting route rather than sending private data to an unofficial guide.
Return to this page's sources after updates. If a report receives an official notice or resolution, retain its verification history so readers can distinguish reported, acknowledged, fixed, and historical states. Until then, describe what was observed and who reported it without promoting the observation into a universal diagnosis.