Player Take

What This Patch Actually Means for Players

Quick reality check on Dark Souls III Patch 2.2: some fixes land clean, a couple reintroduce old pain. I'll flag both so you're not blindsided. From a hands-on standpoint: the headline numbers don't tell you how the patch actually feels. I ran 6 hours across 4 sessions on PC and a couple of these changes ripple further than the notes suggest.

Performance-wise the patch is a net positive on my rig. Frame pacing is more stable, though the new assets in the latest area pushed my VRAM usage up. Budget-card players, heads up.

Advertisement
Key Changes

Balance & Feature Changes — With Player Impact

ChangeWhat It Means for You
Quest the side quest progression blocker fixedIf you were soft-locked, reload an earlier save and re-trigger.
The frontline bruiser companion AI no longer gets stuck on terrainThey actually keep up during traversal now. Small but huge QoL.
The dodge roll exploit patchedSpeedrunners lose a skip; the intended route is the only one now.
Bug Fixes

Bugs Squashed in Patch 2.2

🐛Fixed a memory spike that could cause a disconnect after long sessions.
Player impact: Quality-of-life win the community has wanted for weeks.
🐛Fixed an achievement not unlocking when the condition was met offline.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Resolved audio cutting out during the co-op raid on certain sound cards.
Player impact: Quality-of-life win the community has wanted for weeks.
🐛Fixed a crash when opening the inventory immediately after a loading screen.
Player impact: Removes a recurring frustration for endgame players.
🐛Resolved an issue where the skill tree would silently fail under high ping.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Resolved a bug where party members loaded into different instances.
Player impact: Closes a loophole that was skewing leaderboards.
Crash & Error Fixes

How to Fix Crashes & Errors After Patch 2.2

Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:

💥Crash on entering the dungeon or fast-traveling
  1. Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~600MB there.
  2. Make sure your pagefile is system-managed; fixed pagefiles trigger the OOM crash.
  3. Fast-travel to a nearby node first, then walk in. Avoids the asset spike.
Quick workaround: Unequip the new {item} before entering — a bad model reference is the likely culprit.
💥Infinite loading screen after the patch
  1. Sign out of the launcher and back in to refresh your session token.
  2. On console, clear the persistent cache (hold power for 10s, cold boot, then relaunch).
  3. Check the game's server status page — the login queue is failing silently.
Quick workaround: Switching to a wired connection and avoiding VPNs clears the hang for most players.
💥Game closes to desktop right after the splash screen on Patch 2.2
  1. Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
  2. Update your GPU driver to the latest Intel build — the May/June branches break on this patch.
  3. Delete the cache folder at Documents/DarkSoulsIII/cache, then relaunch.
  4. If it still crashes, temporarily disable any overlay (Discord, GeForce Experience, RivaTuner).
Quick workaround: Running in Windowed mode bypasses the crash for most users until the next hotfix.
Advertisement
Known Issues

Known Issues Still Being Worked On

These problems are acknowledged but not yet fixed. Here's the status and a temp workaround for each:

Known IssueStatusWorkaround
HDR displays may clip whites in the the dungeon menu.Being worked onLower HDR peak luminance to 1000 nits in the system menu.
Cross-save may delay inventory sync by up to 10 minutes.InvestigatingWait a few minutes before assuming items are lost.
High refresh rate monitors may cap at 60fps in borderless mode.Pending fixUse exclusive fullscreen until the next hotfix.
Voice chat volume resets between matches.KnownRe-check your voice settings each session for now.
FAQ

Frequently Asked Questions About Patch 2.2

The exact questions players search after this patch drops:

AYes. Patch 2.2 is backward-compatible with saves from the previous version. Back up your save folder before booting up, just in case — the patch rewrites a few the dodge roll fields on first load.
AStart by verifying game files and updating your GPU driver — the Patch 2.2 build raised VRAM use, so dropping textures from Ultra to High fixes most splash and fast-travel crashes. The full step-by-step is in the Crash & Error Fixes section above.
AThe patch added denser the hub assets. Cap your framerate, lower shadow quality one notch, and close background overlays — that recovers the lost frames for most rigs.
ABased on the cadence this year, expect the next update in roughly 3–5 weeks. Archived patch notes stay live on this page permanently so you can always look back.
Bottom Line

Final Summary

Net positive for Dark Souls III players. A few rough edges remain (see Known Issues), but the core experience is more stable post-Patch 2.2. I'll keep this archived page updated if any hotfixes follow.

👉 This page is permanently archived. Read the latest Dark Souls III patch notes →

More Dark Souls III Patches

Other Dark Souls III Patch Notes

→Patch 2.4 LatestApr 21, 2026→Patch 1.1 Feb 8, 2026→Patch 1.0 Jan 17, 2026📋View all Dark Souls III patches

⚠️ Important Disclaimer

This patch-notes breakdown is a player-perspective summary of Dark Souls III Patch 2.2 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Dark Souls III's developer or publisher. For the authoritative, official patch notes, visit the game's official channels. All trademarks belong to their respective owners. Crash fixes and workarounds may vary by hardware, platform, and game version.