Black Flag Resynced 1.0.5: What It Fixed, What’s Still Broken

Update 1.0.5 for Assassin’s Creed Black Flag Resynced went live on July 23, 2026, as a PC-only download of roughly 183MB, and it targets stuttering rather than delivering a broad content patch. Ubisoft shipped it without a proper changelog, and the known issues list from Black Island’s missing side content is still very much unresolved. This piece covers exactly what 1.0.5 touched, what’s confirmed still broken from Ubisoft’s own tracker, and how PC crash reports are being handled by the community while an official fix is pending.

The Steam announcement for 1.0.5 is short and to the point: Earlier today we released a PC Only patch (1.0.5) to alleviate stuttering issues experienced by some PC players. There’s no itemized changelog attached to it, which is unusual compared to the previous update. Reporting on the patch confirms the same thing from the outside: Ubisoft did not share any release notes for it, and the patch only aims to resolve the stutters that could occur on specific PC systems, and nothing more. That stands in contrast to Title Update 1.0.4, released on July 16, which shipped with a full list covering save/load fixes, localization corrections, a dubbing issue affecting voiceover playback, and a fix for cutscenes locking to 30 FPS on Custom graphics presets. As of the most recent tracking available, the current verified version on console is Title Update 1.0.4, with no newer official title-update notes found — so if you’re on PS5 or Xbox Series X/S, 1.0.5 is a PC-only story for now, not something sitting in your update queue.

Ubisoft’s known issues list was last posted on July 16 alongside 1.0.4, and nothing in the PC-only 1.0.5 patch touches these items — they’re unrelated to stuttering, so there’s no reason to expect them fixed. Here’s the current state of the ones that matter most.

The Black Island 100% Blocker

This is the one that actually matters if you’re chasing full completion. Ubisoft’s own tracker states that on Black Island, “Morgan’s Treasures” and “Midnight Moonshine” may sometimes remain unavailable to the player. Neither 1.0.4 nor the stutter-focused 1.0.5 addresses this, and there’s no separate hotfix note for it. If you’re grinding toward a full sync completion, this is worth checking before you sink hours into everything else on the island, since there’s currently no confirmed workaround beyond waiting for a future patch.

Quest-Level Annoyances That Don’t Block Progress

The rest of the open list is more of a friction problem than a wall. Background music may stop playing when opening the Patch Notes menu during gameplay, which is annoying but harmless. The double assassination prompt issue near the first power keg in “Mark the Kings at the Camp” can compromise a stealth run if you don’t already know the keg is there. Food vanishing in “A Second Chance,” the blocked eavesdrop in “Commodore Eighty-Sixed,” and the retriggering tutorials in “The Treasure Fleet” are all cosmetic-to-mildly-annoying rather than progress-blocking.

The Templar Hunt Save Report

Separately, one journalist flagged a more serious concern around launch: a warning not to leave any Templar Hunt sidequest chains unfinished because doing so produced a save-data glitch. This was reported by a single outlet around launch week rather than confirmed as a widespread pattern, and it’s unclear whether it still applies after 1.0.4 and 1.0.5 — treat it as a “finish what you start” caution rather than a confirmed ongoing bug.

Alongside the stutter that 1.0.5 targets, players have reported outright crashes and freezes, including a DX12 error some PC users encounter. None of the fixes below are official — they’re what’s circulating from players and troubleshooting sites, and Ubisoft hasn’t attributed the crashes to any of these specific causes.

• Clearing the local cache folder in Documents plus the GPU-side shader cache, which forces the game to rebuild shaders on next launch.
• Disabling overlays (Discord, GeForce Experience, etc.), since overlays can cause crashes in games with heavy rendering, ray tracing, frame generation, or HDR.
• Switching input method — posts on the game’s Steam forum describe stutter easing after switching the controls to “controller only”, though this reads as anecdotal rather than a confirmed fix.
• Rolling back to an older GPU driver, which some players say resolved Havana-specific stutter on their setup.
• Turning off frame generation and capping FPS, particularly when running ray tracing on 40-series cards.

Independent troubleshooting coverage lines up with this: Havana stuttering is linked to heavy NPC density, asset streaming, CPU workload, and shader compilation, and community workarounds exist, but no universal fix is available yet. Treat every item above as “worth trying,” not “guaranteed to work.”

Myth: 1.0.5 Is a Real Content Patch

It isn’t. It’s a narrow, PC-only fix aimed at stuttering, shipped without a changelog. If you were expecting quest fixes or new content bundled in, that’s not what this update is.

Myth: Consoles Got the Same Update

They didn’t, at least as of the most recent check. PS5 and Xbox Series X/S are still on 1.0.4 from July 16, and there’s no separate console rollout of 1.0.5 confirmed anywhere.

Myth: The Havana Stutter Has One Confirmed Cause

Reports point to several overlapping culprits — asset streaming, shader compilation, CPU load, driver interactions — and no single official root cause has been named. Anyone claiming they’ve found “the” fix is describing what worked on their rig, not a universal solution.