What This Patch Actually Means for Players
Pulled the patch notes apart so you don't have to. Here's what Assassin’s Creed Shadows's Patch 1.12 actually changes the moment you boot it up. Reading between the lines: the headline numbers don't tell you how the patch actually feels. I ran 7 hours across 3 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.
Balance & Feature Changes — With Player Impact
| Change | What It Means for You |
|---|---|
| Quest the companion arc progression blocker fixed | If you were soft-locked, reload an earlier save and re-trigger. |
| Texture streaming pop-in on the dungeon reduced | The city skyline stops flickering when you pan the camera fast. |
| HDR brightness clipping on the finale cutscene fixed | No more blown-out highlights in that one cutscene. |
| Auto-save frequency increased in the city district | 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. |
Bugs Squashed in Patch 1.12
How to Fix Crashes & Errors After Patch 1.12
Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:
- Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 1.12.
- 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.
- 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.
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 |
|---|---|---|
| HDR displays may clip whites in the the dungeon menu. | Being worked on | Lower HDR peak luminance to 1000 nits in the system menu. |
| Some players still see the old the recon class/{weapon} stats until a full client restart. | Acknowledged | Restart the client after the patch downloads. |
| High refresh rate monitors may cap at 60fps in borderless mode. | Pending fix | Use exclusive fullscreen until the next hotfix. |
Downtime & Schedule
Scheduled: 2026-03-29 from 04:00 UTC for approximately 2 hours.
Details: Matchmaking disabled during the window. Assassin’s Creed Shadows ranks will not decay for missed placement games during downtime.
Compensation: No compensation planned.
Frequently Asked Questions About Patch 1.12
The exact questions players search after this patch drops:
Final Summary
If you held off updating because of the early crash reports, Patch 1.12 is now safe to grab on most rigs. The fixes above cover the worst offenders. See you in the next patch notes — this page stays permanent.
👉 This page is permanently archived. Read the latest Assassin’s Creed Shadows patch notes →
⚠️ Important Disclaimer
This patch-notes breakdown is a player-perspective summary of Assassin’s Creed Shadows Patch 1.12 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Assassin’s Creed Shadows'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.