Crimson Desert Known Issues and Workarounds After 2.0

Pearl Abyss keeps one list, and edits it in place

Every Crimson Desert patch note since the Enhanced update carries the same line — "For known issues, please check the notice below" — pointing at a single notice on the announcement board. That notice is not reposted when it changes. It is edited at the same URL (board number 68), and the edit is marked by a timestamp inside the body.

This post was first built on the copy stamped "(Last updated: 2026/08/31 13:20 UTC)", which listed fourteen issues. The copy read on November 1, 2026 carries a posted date of November 1, 2026, 03:00 UTC and, in the body, the line "(Last updated: 2026/11/01 14:00 UTC)". Seventeen entries are open on it. Six of them come with written instructions from Pearl Abyss; the rest are acknowledged and nothing more.

The posted date moves with the edits: it read August 25, 2026, 19:00 UTC on the August copy and September 18, 2026, 10:00 UTC on the September copy. The November copy also sits at the top of the board's Notices list, between the 2.04.04 and 2.04.03 hotfix notes, so if you are scanning the board by date, it is near the top again.

That distinction is the whole reason to read the list rather than a forum thread: an entry on this page is confirmed by the developer, so the answer to "is it me or the game" is settled before you spend an evening reinstalling.

Every open known issue in the November 1 revision

Read the shape of that list before the contents. Entries 1 to 8 are all new since September 21, and several touch areas the DLC-era patch notes also cover (Gift, underwater sound, trade goods). Four of the seventeen are scoped to a platform (8 Xbox, 14 and 15 Mac, 16 PlayStation), and two more are tied to a specific PC component or setting (2 AMD driver 26.10.1, 17 FSR4).

Two entries come from the same source paragraph and are printed run-together in the official notice, with entry 13 starting mid-line immediately after entry 12's full stop. The same glitch was on the August 31 and September 21 revisions — MP1st reproduced the run-on when it republished the August list — which is a good sign it is in Pearl Abyss's HTML rather than in anyone's transcription.

What changed since the September 21 revision

Eight entries are new (1 to 8) and one is gone. The one that left is the odd entry from the September list: "Icons for newly discovered objects in certain regions do not appear on the map." Hotfix 2.03.02, posted September 23, 2026, 04:45 UTC, had listed that exact fix while the notice still carried it; the November revision no longer does, so the notice and the patch note now agree.

The other nine September entries are all still listed, including the two progression risks covered below: Greymane faction quests while playing as Damiane or Oongka (11) and the Evasion Control "Hold" entry (12). The Charting the Unknown DLC and five hotfixes after it did not clear either.

One thing the notice does not carry: Damiane's exclusive quest "End and Beginning." It is not a known-issues entry. It appears in the patch notes instead — hotfix 2.04.05 lists "Fixed an issue where Damiane's exclusive quest 'End and Beginning' could not be progressed if 'Journey's End' from the main story was completed within a certain timeframe."

What left the list since August 31

By the September 21 revision, five of the fourteen August 31 entries had gone and one had been added. Only two of the five departures had a patch-note line that names them. The November revision does not bring any of them back.

Removed from the known-issues list is not the same as fixed. Pearl Abyss does not publish a changelog for the notice, so for the two Xbox language-pack bugs and the GTX 1060 white screen the only evidence is absence: they are no longer listed, and no patch note claims them.

The entries with a written workaround

These are worth stating in full, because they are the entries where the developer has told you what to do instead of only what to wait for. Six of the seventeen carry an instruction. The Spanish voice-language entry from the August list also had one — select "Default" under Others > Options > Settings > Language and Audio — before it left the list after 2.01.00 listed the fix.

NPCs, mounts and objects stop responding (9). The notice says interactions become unavailable "in certain situations" and does not name them. The stated remedy is a game restart, and Pearl Abyss flags it as temporary rather than a fix. If your horse will not respond to a mount prompt, that is the first thing to try before assuming a broken save.

Version mismatch crash (6). The notice says the game may crash if the base game and DLC versions do not match, and the instruction is to update both to the latest versions. Notice 145 (the 2.04.00 hotfix) adds a wrinkle: the in-game version keeps displaying 2.04.00 after the hotfix installs, with the version to be corrected by future patches. Do not use the version number on the title screen to decide whether a hotfix landed; read the patch notice and its date.

AMD driver crash in Pailune (2). With the Cinematic option on and driver 26.10.1, the game crashes in Pailune. Pearl Abyss asks you to install driver 26.9.1 or earlier from the AMD website until it is resolved. Hotfix 2.04.02 separately lists an [AMD] fix for certain graphics appearing incorrectly on driver version 26.10.1 — a graphics problem on the same driver, not the Pailune crash, which stays on the list.

Samora trade goods (3). Packaged trade goods bought from the merchant of Samora island may show a wrong quantity when moved from a ship to a wagon. The notice says it does not occur when the goods are moved one at a time, which is a real cost on a trading run with a full hold, but it is the written fix.

Twitch Drops (7). The Drops & Rewards menu cannot claim them for now. The instruction is to click Claim in the stream chat and then link your Twitch account on the Drops event page.

PlayStation naming freeze (16). Typing quickly on the virtual keyboard while naming a pet or a horse can freeze the screen. Pearl Abyss asks you to enter characters slowly with brief pauses — an unusually candid piece of advice, and one that lands directly on the pets and mounts systems, where naming is the first thing you do.

The two that can stall a quest

Most of the list is irritation. Two entries are progression risks, and both are worth knowing before you start a session rather than after.

Greymane faction quests cannot be progressed while playing as Damiane or Oongka. Crimson Desert has three playable characters and update 2.00.00 made spending on one of them feed the other two, via Abyss Link — which is exactly the change that encourages you to spend more time as the other two. This bug pushes the opposite way on one specific quest line. Pearl Abyss has not published a workaround for it and has not said which quests in the faction line are affected.

NPCs required for quest progression cannot ride together on Legendary Animal mounts. The mounts guide counts eight legendary mounts — five animals you hunt and unlock with a crafted Sigil of Solidarity, plus three horses you tame. Pearl Abyss's wording names the animals, so if a quest needs an NPC on the back of your mount, a horse is the safer choice.

Neither of these has a published fix date. Both were on the August 31 revision and both are still on the November 1 one, which means they have outlasted every patch shipped in between — 2.01.00 through 2.04.05, including the DLC update itself — and none of those patch notes names either of them.

Entry 5 may be a third progression risk: the notice says the Camel Constellation and a blockaded stronghold are located in an inaccessible region. It names no workaround and no platform or setting.

A smaller but stranger one: fish caught while fishing in certain areas are unable to move. Fishing is one of the life skills the camp guide treats as a supply run for cooking ingredients, so this is a cosmetic-looking bug sitting on top of a productive loop. The notice does not say whether the catch still registers.

The graphics entries tied to a specific setting

Two PC graphics entries are on the November revision, and both name an exact component or setting.

The August list had a third: a white screen on an NVIDIA GTX 1060 with FSR Upscaling and Frame Generation both enabled. It is gone from the list, and no patch note from 2.01.00 to 2.04.05 names it. The GTX 1060 is the exact card on Pearl Abyss's Minimum PC tier, which the system requirements guide covers in full. One related change did land: the 2.04.00 patch notes say Upscaling and Frame Generation technologies can now be selected separately, for example DLSS upscaling with FSR Frame Generation. That is a settings change, not a stated fix for the white screen, so the cautious August advice stands: on a 1060, run one of those two features, not both, unless you have tested the combination yourself.

What the 13 patches since 2.00.00 have fixed

Thirteen patches have shipped since the Enhanced update: nine that Pearl Abyss labels "(All Platforms Hotfix)" and four numbered updates. The hotfixes are pure fix lists. Each numbered update adds something — and the last one, 2.04.00, is the Charting the Unknown DLC. There is no 2.04.01 notice on the board in the range I read (the numbering jumps from the 2.04.00 hotfix to 2.04.02).

The first four patches list all six storefronts — Steam PC, Steam Mac, PlayStation, Xbox, Epic Games Store and the Mac App Store — as "Patch available now." From 2.03.00 onward the Mac App Store line reads "Patch available at a later time (in-progress)" on every notice I read, through 2.04.05, so as of November 1 the board does not list any of those patches as available on that storefront. The DLC update also requires a one-time download of the full-size game package for Steam (Mac) and Mac App Store players, per the 2.04.00 notice. Separately, 2.04.04 and 2.04.05 list Xbox as "Patch available at a later time (in-progress)" too.

Pearl Abyss's stamps on the 2.04.00 hotfix and 2.04.02 both read October 30, 00:00 UTC, and 2.04.04 and 2.04.05 both read November 1, 04:28 UTC — the same kind of duplicate stamp discussed under 2.00.02 below, so treat the notice title and number as the ordering, not the minute.

One line appears on both 2.00.0x hotfixes: "Partially improved the lip-sync of characters in certain cutscenes." Same wording, two consecutive patches. Pearl Abyss does not say whether these are different cutscenes or a second pass at the same ones, and "partially" is doing real work in that sentence either way.

The Karin Quarry crane fix is the one to notice if you are working through the knowledge and research locations — an unresponsive interactable at a fixed world site is the kind of thing that reads as a soft-lock when you hit it. The 2.03.02 entries are the same shape: a quest NPC that does not spawn and an Abyss that will not progress are both soft-locks by another name, and neither appeared on the August 31 or September 21 revision of the known-issues notice. The same goes for the 2.04.05 quest fixes ("End and Beginning", the witch proposals, "Beyond the Margins"), none of which is on the November notice.

The date on 2.00.02 does not line up

The 2.00.02 notice prints a posted date of August 28, 2026, 00:00 UTC — byte-for-byte the same stamp as the 2.00.01 notice directly beneath it in the list. MP1st reported the same three fixes on September 1, 2026, naming the console download as Crimson Desert update 1.000.493.

Those cannot both be the deployment date. The version ordering is not in doubt — 2.00.02 sits above 2.00.01 on the board and carries the higher number — but if you are trying to work out whether the build on your console includes the crane fix, check for 1.000.493 rather than trusting the timestamp on the web notice.

The 2.00.00 fixes that touch systems you use

Coverage of update 2.00.00 concentrated on the story additions, the six new languages and the rebuilt skill system, all of which are in the Abyss Link write-up. Underneath that headline block, the same patch notes carry a long "Main Improvements" list our earlier coverage never quoted. These are the entries that change behaviour a guide might have told you to expect:

The Blackstar and trade-goods entries are the two most likely to change what you do. A dragon that could be re-summoned without its cooldown is a different traversal tool from one that cannot, and moving trade goods into horse inventory at the stable is a routine step in a trade run rather than an edge case. Blackstar came back in 2.01.00 with a second fix — summoning him "would cause other mounts to be summoned in certain situations" — so the dragon has been patched in two consecutive numbered updates.

What I could not verify

• Whether the two Xbox language-pack bugs and the GTX 1060 white screen were fixed or merely delisted. No patch note from 2.01.00 to 2.04.05 names any of the three; they stopped appearing on the notice between the August 31 and September 21 revisions, and Pearl Abyss publishes no changelog for it.
• The exact time the November 1 revision went up. The notice prints a posted date of November 1, 03:00 UTC and a body stamp of 2026/11/01 14:00 UTC; I report both as printed and cannot reconcile them.
• Whether a missing 2.04.01 exists. The board numbering goes from the 2.04.00 hotfix to 2.04.02 in the notices I read.
• Which Greymane faction quests are affected, or whether a character switch clears the block. Pearl Abyss names the faction line and nothing narrower, and publishes no workaround.
• The actual deployment date of 2.00.02. The notice board and MP1st disagree, as above.
• Whether the fishing bug affects the catch itself or only the fish's animation. The notice says only that the fish "are unable to move."
• Whether the two lip-sync entries cover the same cutscenes. Both 2.00.0x patches use identical wording.
• Any community-reported workaround. Nothing in this post comes from a forum thread; everything here is on Pearl Abyss's own notice board, with the 2.00.02 console build number from MP1st.

Quick Action Checklist

1. Check the notice, not the forums. Pearl Abyss keeps one live known-issues page and edits it in place — the last-updated stamp is inside the body. Compare that stamp with the newest patch note before trusting it, and remember the in-game version stays at 2.04.00 after the first hotfix, so identify patches by notice title and date.
2. If the game crashes after the DLC and the versions may differ, update both the base game and the DLC to the latest versions — the notice lists a version mismatch as a crash cause.
3. If you are on AMD driver 26.10.1 and crash in Pailune with Cinematic on, install driver 26.9.1 or earlier, as the notice says.
4. Moving Samora trade goods from a ship to a wagon? Move them one at a time; the notice says the quantity bug does not occur that way.
5. If an NPC, mount or object stops responding, restart the game before assuming a corrupted save.
6. Twitch Drops will not claim in the menu? Click Claim in the stream chat, then link your Twitch account on the Drops event page.
7. Type slowly when naming a pet or horse on PlayStation. Fast input on the virtual keyboard can freeze the screen.
8. Do not run Greymane faction quests as Damiane or Oongka until it is patched.
9. Use a horse, not a legendary animal, when a quest NPC needs to ride with you.
10. Give NPCs items one at a time, as a precaution. The notice lists the title-screen return when giving multiple items at once as open and publishes no instruction; the 2.04.03 hotfix added multi-select to "Gift", and the notice does not say whether the two are related.
11. On a GTX 1060, keep FSR Upscaling and Frame Generation apart unless you have tested the combination — the white-screen entry has left the list, but no patch note claims the fix.
12. Swap upscalers if rain looks wrong. FSR4 is the one named for disappearing rain and image distortion.
13. On the Mac App Store, expect to be behind. Every patch from 2.03.00 through 2.04.05 reads "Patch available at a later time (in-progress)" for that storefront.
14. On console, look for build 1.000.493 to confirm you have hotfix 2.00.02 and the Karin Quarry crane fix.