You drop into SNAP Mode at 1920×1080 and the whole screen turns into soft mush. At 1280×720 it looked fine. That was a real bug: on pre–October 17 builds, entering SNAP above 1280×720 broke depth-of-field focus. The October 17, 2026 bug-fixing build lists it as fixed.
This page is the narrow complement to the broader low FPS / lag / crashes guide. Fix blur first if SNAP is unreadable; chase GPU settings second.
Confirm you still have the bug
- Set resolution above 1280×720 (e.g. 1600×900 or 1920×1080).
- Enter SNAP Mode the same way you always do on your bind.
- If the world stays incorrectly soft-focused while UI chrome looks wrong, you are on the old DoF failure—or a different post-process issue.
If blur exists outside SNAP too, stop treating this as the October 17 SNAP bug. Follow the FPS guide (bloom/shadows/resolution) instead.
Fix path after October 17
- Grab a current build from Download.
- Prefer a clean launcher update or fresh zip folder—do not stack patch zips on a half-updated tree (launcher / zip guide).
- Retest SNAP at your target resolution.
- If still blurred on a post–Oct 17 folder, delete leftover mod post-process injectors (ReShade, old PoseMod stacks) and retest vanilla.
DevBlog source: October 17th Bug-Fixing Build.
Temporary workarounds (old builds only)
If you cannot update yet:
- Play at 1280×720 while using SNAP-heavy routes.
- Avoid SNAP for intel and use quieter observation when the blur blocks reads.
- Do not “fix” blur by maxing post-effects—the bug was focus logic, not missing AA.
Workarounds are stopgaps. Update when you can; SNAP is part of Info Point economy for many 202X plans.
Related October 17 checklist (while you are here)
Same build also touched other quality landmines worth a five-minute smoke test after updating:
| Item | Why smoke-test |
|---|---|
| Sewing Room listening-device prompt | Prompt broke after a relocate; should work again (new position). |
| Hazu spare uniform spawn | Uniform reward location was wrong; confirm pickup spot. |
| Floating lunch bullies | Midair lunch eaters should be grounded. |
| Library 5:55 PM skip | Advancing to 5:55 via library broke Osana/Taro end-of-day; retest if you use that skip. |
None of those replace the FPS guide’s driver/SSD advice—they are “did my update actually land?” canaries.
When it is still a performance problem
Readable SNAP with 20 FPS is a different ticket. After DoF looks correct:
- Drop shadows/bloom per FAQ performance tips.
- Close capture overlays.
- Compare 202X vs 1980s weight on the same preset.
Blur that tracks crowd density rather than SNAP entry is usually fill-rate, not the October 17 DoF bug.
Ship the update, verify SNAP at native resolution, then return to rival timing with a sharp phone feed.