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 live on September 26, 2026 carries a posted date of September 18, 2026, 10:00 UTC and, in the body, the line "(Last updated: 2026/09/21 14:00 UTC)". Ten issues are open on it. Two of them ship with a workaround written by Pearl Abyss. The rest are acknowledged and nothing more.

That posted date is itself a change: on the August copy it read August 25, 2026, 19:00 UTC. Same URL, but the notice now sits between the 2.03.01 and 2.03.00 patch notes on the board index rather than back with the Enhanced launch, 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 issue 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 September 21 revision

Read the shape of that list before the contents. Four of the ten are scoped to something narrower than "the game" — two Mac (7, 8), one PlayStation (9) and one tied to a specific PC graphics setting (10). That leaves six that can happen to anyone on any platform, and those six are the ones worth memorising.

Two of the ten come from the same source paragraph and are printed run-together in the official notice, with issue 6 starting mid-line immediately after issue 5's full stop. The same glitch was on the August 31 revision — MP1st reproduced the run-on when it republished that list — and it is still there on the September 21 one, which is a good sign it is in Pearl Abyss's HTML rather than in anyone's transcription.

Issue 1 is the odd one out. The notice's body stamp is 2026/09/21 14:00 UTC, which is the same minute hotfix 2.03.01 was posted. Hotfix 2.03.02, posted September 23, 2026, 04:45 UTC, lists "Fixed an issue where icons for newly discovered objects in certain regions would not appear on the map." Pearl Abyss has not revised the notice since, so the first entry on the list is one the patch notes say is already fixed. The notice and the patch note cannot both be current; the patch note is the newer document.

What left the list since August 31

Five of the fourteen August 31 entries are gone, and one entry is new. Only two of the five departures have a patch-note line that names them.

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 two bugs with an official workaround

These are worth stating in full, because they are the only two where the developer has told you what to do instead of what to wait for. There were three on the August 31 revision; the Spanish voice-language entry, whose workaround was to select "Default" under Others > Options > Settings > Language and Audio, left the list after 2.01.00 listed the fix. If Spanish is still missing on a build older than 2.01.00, that workaround is the one Pearl Abyss published. Update 2.00.00 added five voice languages — German, French, Spanish, Japanese and Brazilian Portuguese — so the bug landed on one of 2.00.00's headline additions.

NPCs, mounts and objects stop responding. 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. Hotfix 2.03.01 separately fixed "an issue where the game would crash when interacting with NPCs in certain situations" — a crash, not the unresponsive-interaction entry, which stays on the list.

PlayStation naming freeze. 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

Eight of the ten are irritations. Two 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 September 21 one, which means they have outlasted the four patches shipped between those two revisions — 2.01.00, 2.02.00, 2.03.00 and 2.03.01 — and 2.03.02, posted two days after the second revision, does not name either of them.

The third one guide readers should note is smaller but stranger: 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 bug tied to a specific setting

The August 31 revision carried two PC graphics entries, both naming exact settings. One is left.

The other — a white screen on an NVIDIA GTX 1060 with FSR Upscaling and Frame Generation both enabled — is gone from the list, and no patch note from 2.01.00 to 2.03.02 names it. The GTX 1060 is the exact card on Pearl Abyss's Minimum PC tier, which the system requirements guide covers in full, so that entry landed on the cheapest supported configuration, where turning on upscaling and frame generation is the obvious thing to do. Until a patch note claims the fix, the August advice stands: on a 1060, run one of those two settings, not both.

What the seven patches since 2.00.00 have fixed

Seven patches have shipped since the Enhanced update: four that Pearl Abyss labels "(All Platforms Hotfix)" and three numbered updates. The hotfixes are pure fix lists. Each numbered update adds something — small, but not nothing.

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 all three notices, so as of September 26 the board does not list 2.03.00, 2.03.01 or 2.03.02 as available on that storefront. If you bought the game there, the Mysterious Pot and Ether Rest fixes are not yours yet.

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 appears on the August 31 or September 21 revision of the known-issues 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.03.02 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.
• Why the map-icon entry is still on the notice when 2.03.02 lists it as fixed. The notice has not been revised since September 21, 14:00 UTC, two days before that hotfix was posted.
• 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; on September 26 the notice was two days older than 2.03.02.
2. If Spanish voice is missing, make sure you are on 2.01.00 or later — that patch lists the fix. On an older build, the workaround Pearl Abyss published was to select "Default" under Others > Options > Settings > Language and Audio.
3. If an NPC, mount or object stops responding, restart the game before assuming a corrupted save.
4. Type slowly when naming a pet or horse on PlayStation. Fast input on the virtual keyboard can freeze the screen.
5. Do not run Greymane faction quests as Damiane or Oongka until it is patched.
6. Use a horse, not a legendary animal, when a quest NPC needs to ride with you.
7. On a GTX 1060, keep FSR Upscaling and Frame Generation apart until a patch note says otherwise — the entry has left the known-issues list, but no patch note claims the fix.
8. Swap upscalers if rain looks wrong. FSR4 is the one named for disappearing rain and image distortion.
9. On Xbox, the two language-pack deletion bugs are off the list with no patch note naming them. If a pack vanishes after you add or delete another, report it — Pearl Abyss no longer lists it as known.
10. If map icons for newly discovered objects are missing, check you are on 2.03.02 — it lists that fix, even though the notice still lists the bug.
11. On the Mac App Store, expect to be behind. 2.03.00, 2.03.01 and 2.03.02 all still read "Patch available at a later time (in-progress)" for that storefront.
12. On console, look for build 1.000.493 to confirm you have hotfix 2.00.02 and the Karin Quarry crane fix.