What This Patch Actually Means for Players
Quick reality check on Dark Souls III Patch 1.1: some fixes land clean, a couple reintroduce old pain. I'll flag both so you're not blindsided. What the notes won't tell you: the headline numbers don't tell you how the patch actually feels. I ran 9 hours across 2 sessions on PC and a couple of these changes ripple further than the notes suggest.
Netcode feels more honest after Patch 1.1. I'm getting fewer 'how did that register?' moments, which is the boring but important win. The flashy balance changes get the clicks; the rollback fixes are why you'll actually stay.
Balance & Feature Changes — With Player Impact
| Change | What It Means for You |
|---|---|
| Auto-save frequency increased in the dungeon | Less replaying after a crash. Still, manual save before bosses. |
| The frontline bruiser companion AI no longer gets stuck on terrain | They actually keep up during traversal now. Small but huge QoL. |
| Quest the companion arc progression blocker fixed | If you were soft-locked, reload an earlier save and re-trigger. |
| HDR brightness clipping on the finale cutscene fixed | No more blown-out highlights in that one cutscene. |
| Texture streaming pop-in on the open field reduced | The city skyline stops flickering when you pan the camera fast. |
Bugs Squashed in Patch 1.1
How to Fix Crashes & Errors After Patch 1.1
Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:
- Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~500MB there.
- Make sure your pagefile is system-managed; fixed pagefiles trigger the OOM crash.
- Fast-travel to a nearby node first, then walk in. Avoids the asset spike.
- Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 1.1.
- Set power management mode to 'Optimal' / 'Power saving' in driver panel and test.
- Reinstall the driver using DDU (Display Driver Uninstaller) for a clean slate.
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 Issue | Status | Workaround |
|---|---|---|
| Cross-save may delay inventory sync by up to 5 minutes. | Investigating | Wait a few minutes before assuming items are lost. |
| Some players still see the old the assault operator/{weapon} stats until a full client restart. | Acknowledged | Restart the client after the patch downloads. |
| HDR displays may clip whites in the the city district menu. | Being worked on | Lower HDR peak luminance to 1000 nits in the system menu. |
| High refresh rate monitors may cap at 60fps in borderless mode. | Pending fix | Use exclusive fullscreen until the next hotfix. |
Frequently Asked Questions About Patch 1.1
The exact questions players search after this patch drops:
Final Summary
Patch 1.1 is a solid, if unglamorous, update for Dark Souls III. The crash fixes alone justify the download; the balance tweaks will shake out over the next two weeks of play. Bookmark this page — it stays live as an archived reference even after the next patch drops.
👉 This page is permanently archived. Read the latest Dark Souls III patch notes →
⚠️ Important Disclaimer
This patch-notes breakdown is a player-perspective summary of Dark Souls III Patch 1.1 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.