Diff - known bugs and issues - Crimson Desert Wiki

11 Overview

33 Crimson Desert launched on March 19, 2026 across PC (Steam, Xbox app), PlayStation 5, and Xbox Series X|S. Like many large open-world RPGs, the launch came with a set of technical problems and gameplay bugs. Pearl Abyss acknowledged many of these issues on its official website and released a Day One Patch (version 1.00.02) alongside the launch to address some of the most pressing concerns. This page tracks every confirmed bug, glitch, and technical issue along with known workarounds and official fixes.

66 All issues listed below have been confirmed by either Pearl Abyss directly or by multiple independent player reports. Entries are removed from this page once a patch resolves them.

88 Official Known Issues (Pearl Abyss)

10-The official known-issues notice was last refreshed on August 25, 2026, alongside version 2.00.00. Several entries listed further down this page were fixed by patches released between April and August 2026 and are retained here as history rather than as live problems. For the current official list, including the three language-related issues introduced by the Crimson Desert Enhanced update, see Known Issues.

10+The official known-issues notice was last updated on September 11, 2026 at 06:00 UTC, half an hour after patch 2.02.00 shipped, and had not changed again as of September 16, 2026. It lists seven open issues, reproduced below. Everything further down this page is the longer community and troubleshooting record, including entries that patches released between April and September 2026 have since fixed; those are retained as history rather than as live problems. The three language-pack entries tied to Crimson Desert Enhanced are among the ones the September revision dropped, one of them because patch 2.01.00 fixed it.

1111

12-Pearl Abyss maintains a known issues list on the official Crimson Desert website. The following bugs are acknowledged by the developer as of March 22, 2026.

12+IssuePlatformDetailsInteractions unavailableAllNPC, mount and object interactions stop working in certain situations. Restarting the game is the published temporary workaround.Caught fish cannot moveAllFish caught in certain areas are unable to move.Greymane faction quests blockedAllGreymane faction quests cannot be progressed while playing as Damiane or Oongka.Evasion rebind ignoredAllWith Evasion Control set to Hold, the default Evasion key still works after it has been rebound.Shared Legendary Animal mountsAllNPCs required for quest progression cannot ride together on Legendary Animal mounts.Cursor offset when placing furnitureMacAt certain resolutions with keyboard and mouse, the cursor position differs from the actual furniture placement point.Colorblind filter not appliedMacThe colorblind filter is not applied to the UI when Colorblind Mode is enabled.

13+Two entries that appeared on this page as open have since been cleared by patches on the 2.x line: the Thornbriar Fortress liberation blocker was fixed in 2.02.00 on September 11, 2026, and the Martial Monk’s Cloth Robe being classified as headgear was fixed in 2.01.00 on September 4, 2026.

1314

15+The entries in the rest of this section are the older developer-acknowledged list, current as of March 22, 2026. They predate the notice summarised above and are kept for players on older builds and for the workarounds attached to them.

16+

1417 Gameplay and Movement Bugs

1518

1619 IssueDetailsStatusFruit theft lockupAttempting to steal fruit located at the rear of market stalls causes the character to lock up and stop responding to player inputs entirely.AcknowledgedTree clipping and stuck characterTaking damage while grabbing or climbing a tree can clip the character through the trunk, and in some cases the character gets permanently stuck on the tree.AcknowledgedQuest auto-tracking failureSome quests fail to auto-track the next objective after completing a step, leaving players unsure of where to go. Opening the quest log and manually selecting the objective works as a temporary fix.Acknowledged

1720 Quest and Boss Fight Bugs

1821

1922 IssueDetailsStatusDeferred Advance / Blackstar health bugCompleting or quitting out of the Ultimate Weapon fight during the Deferred Advance quest while Blackstar's Health is active causes Blackstar's Health to not respawn fully on retry.AcknowledgedGregor revival bugDuring the Gregor, the Halberd of Carnage boss fight, players cannot revive or continue if surrounding destructible objects are destroyed simultaneously with the player character's death.Acknowledged

2023 Graphics and Settings

2124

2225 IssueDetailsStatusFSR 4 rain artifactsEnabling AMD FSR 4 upscaling causes raindrops to disappear or introduces screen distortion and blurring in rainy areas.AcknowledgedAbyss visible from overworldUnder specific circumstances, the Abyss can be seen from the overworld, which also triggers minor framerate dips.AcknowledgedSettings not savingIn some cases, graphics and gameplay settings do not save properly after loading them, reverting to previous values on restart.Acknowledged

2326 Platform-Specific

2427

2528 IssuePlatformDetailsStatusFishing reel-in brokenXboxThe fishing reel-in function does not work when "Invert Right Stick Y-Axis" is enabled in device settings.AcknowledgedGame fails to launchXbox PC / ROG AllyThe game cannot launch properly on the Xbox PC app or on ROG Ally handheld devices. A workaround involves booting the game while offline, letting save data sync, and then reconnecting.Under investigationMap menu crashes (FIXED)PS5 / PS5 ProOpening the map menu sometimes caused a hard crash. This was fixed in Patch 1.00.03 (March 23, 2026). Turning off 3D map nodes was the pre-patch workaround.Fixed in Patch 1.00.03Pre-order items missingSteamSome Steam pre-order purchasers cannot claim bonus and deluxe pack items.Under investigation

2629 Fixes in Patch 1.00.03 (March 23, 2026)

2730

2831 The following issues from the launch period were resolved in Patch 1.00.03:

2932

3033 IssuePlatformResolutionPS5 Map menu crashPS5 / PS5 ProThe crash when opening the Map menu has been fully resolved. Players no longer need to disable 3D map nodes as a workaround.DualSense vibration not workingPC (Windows)DualSense controller vibration (haptic feedback) now works correctly on Windows when connected via USB or Bluetooth.Graphics card recognition failuresPCCertain GPUs that were not detected at startup are now recognized properly.Mac graphics defaults and crashMacDefault graphics settings on Mac have been corrected, and a launch crash on macOS has been fixed.

3134 For the complete list of changes in this patch, see the Patch Notes page.

3235

3336 PC Technical Issues

3437

3538 Intel Arc GPU Compatibility (Partially Resolved)

3639

3740 At launch on March 19, 2026Crimson Desert did not support Intel Arc graphics cards at all. Players who attempted to run the game on any Intel Arc GPU received a "The graphics device is currently not supported" error and the game refused to start. This affected the entire Intel Arc discrete GPU lineup (including the Arc A770, A750, A580, and B-series Battlemage cards) as well as the integrated Arc graphics found in Intel Meteor Lake and Lunar Lake mobile processors. The incompatibility was not disclosed on the Steam store page prior to launch.

3841

3942 Initial response (March 19-21): Pearl Abyss updated their FAQ to confirm that Intel Arc GPUs were not supported. The developer's official guidance to affected buyers was to "refer to the refund policy of the platform where the game was purchased." Intel issued a public statement through, revealing that it had reached out to Pearl Abyss "many times" over several years and provided early hardware, drivers, and engineering resources across multiple GPU generations, including Alchemist, Battlemage, Meteor Lake, and Lunar Lake. Intel described itself as "hugely disappointed" and said it "remain[ed] ready to assist."

4043

4144 Reversal (March 23-24): Following significant backlash from the gaming community and press coverage, and Pearl Abyss reversed course. The studio issued a new statement: "We are currently working on compatibility and optimization support so that Crimson Desert can also be enjoyed on Intel Arc GPU systems." Pearl Abyss apologized for the "confusion" that their earlier FAQ wording had caused. As of March 24, 2026, the game can now launch on Intel Arc hardware, but users should expect performance drops and stability issues until full optimization is complete. Intel confirmed they are "ready to assist" Pearl Abyss with the ongoing work.

4245

4346 Current status: The game is launchable on Intel Arc GPUs but is not yet fully optimized. Players may experience lower frame rates, visual artifacts, and occasional crashes compared to AMD or Nvidia hardware. Pearl Abyss has not provided a specific timeline for when full Intel Arc optimization will be completed. Check the System Requirements page for the latest supported hardware list.

4447

4548 DLSS and DLAA Black Screen

4649

4750 Nvidia DLSS, specifically DLAA (Deep Learning Anti-Aliasing) and DLSS 4.0 or later, is a primary source of black-screen problems on PC. DLAA can cause a black flickering bar at the top of the screen that progressively swallows the entire image. The workaround is to open the Nvidia App, locate the profile for Crimson Desert, and reset both the DLSS preset and the Super Resolution setting to "Use application settings." Alternatively, disabling DLAA entirely and switching to DLSS Quality mode avoids the issue. See the Best PC Settings Guide for recommended configurations.

4851

4952 Frame Generation Crashes

5053

5154

5255 Enabling frame generation can cause hard crashes when alt-tabbing out of the window or switching display modes. To fix this, navigate to the configuration file at C:\Users\YOUR_NAME\AppData\Local\Pearl Abyss\CD\save, open "user_engine_option_save" in a text editor, change "_numFramesToGenerate = 2" to "_numFramesToGenerate = 0", save the file, and then launch the game in Borderless Windowed mode.

5356

5457 Third-Party Overlay Crashes

5558

5659 The BlackSpace Engine used by Crimson Desert is highly sensitive to third-party software that injects into the rendering pipeline. MSI Afterburner, RivaTuner Statistics Server (RTSS), and similar monitoring or overlay tools must be closed before launching the game. Running these tools can cause hard system shutdowns, freezes, or repeated crashes to desktop. Discord overlay, GeForce Experience overlay, and other injected overlays have also been reported to cause instability.

5760

5861 GPU Driver Requirements

5962

6063 Outdated GPU drivers are one of the most common causes of crashes and visual artifacts. Nvidia users should update to driver version 595.79 or newer, using the "Clean Install" option rather than "Express" to ensure corrupted driver files are fully replaced. AMD users should similarly ensure they are running the latest Adrenalin driver release.

6164

6265 Linux and Proton Compatibility

6366

6467 Players running Crimson Desert on Linux through Proton may experience crashes during the intro video, especially on AMD GPUs like the RX 7900 XTX. Switching to GE-Proton 10-33 resolves the intro crash. Raytracing should also be disabled immediately on AMD Linux setups, as the current AMD Linux drivers crash when raytracing is engaged.

6568

6669 PlayStation 5 Issues

6770

6871 Blurry Graphics (120 Hz Output Bug)

6972

7073 A widely reported issue causes Crimson Desert to render at a significantly reduced internal resolution on PS5 and PS5 Pro when 120 Hz Output is enabled in the console's system settings. This results in extremely blurry, soft-looking visuals even in Balanced or Quality display modes. Pearl Abyss Marketing Director Will Powers confirmed the issue and advised players to disable 120 Hz output as a temporary workaround.

7174

7275 Fix: Go to the PS5 home screen, open Settings, then Screen and Video, then Video Output, and set "Enable 120 Hz Output" to Off. Restart Crimson Desert afterward. The game should now render at its intended resolution.

7376

7477 Performance Mode on Base PS5

7578

7679 found that the 60 fps Performance Mode on the base PS5 (non-Pro) is not recommended. Without upscaling support on the standard PS5, the frame rate in Performance Mode fluctuates between the high 30s and 60 fps, delivering an inconsistent experience. Balanced mode or Quality mode provide a more stable and visually clear result. Refer to the Performance and Graphics Settings page for display mode comparisons.

7780

7881 Controller Issues

7982

8083 Controls Feel Unresponsive

8184

8285 A significant number of players across all platforms reported that the controls feel sluggish, unresponsive, or overly heavy, particularly during combat. Pearl Abyss acknowledged this feedback and announced they are "currently preparing a patch to address" the control complaints. No release date for this patch has been confirmed yet.

8386

8487 Controller Not Working on PC

8588

8689 If a gamepad is not detected on PC, try the following steps in order:

8790

8891

8992 Restart Steam completely (not just the game).Unplug any secondary input devices such as racing wheelsflight sticks (HOTAS), or specialized mice. Crimson Desert defaults to the first USB game controller it detects, and a throttle or secondary device may register as a stuck joystick.Try a wired USB connection instead of Bluetooth or a wireless dongle.Disable Steam Input: right-click Crimson Desert in your Steam library, select Properties, go to the Controller tab, and set "Override for Crimson Desert" to "Disable Steam Input." The BlackSpace Engine has native support for Xbox and PlayStation controllers, and Steam Input's wrapper can cause double-input glitches or dead zones.Update controller drivers through Device Manager under Human Interface Devices or Xbox Peripherals.

9093

9194 DualSense Showing Xbox Button Prompts on PC

9295

9396 When a DualSense or DualSense Edge controller is connected via Bluetooth on PC, Crimson Desert displays Xbox "ABXY" button prompts instead of PlayStation icons. There are two workarounds:

9497

9598 Disable Steam Input (preferred): Open your Steam library, right-click the game, go to Properties, then Controller, and set it to "Disable Steam Input." This lets the engine natively detect the PlayStation gamepad and display the correct Triangle, Circle, Cross, and Square prompts.USB handoff method: Connect the DualSense via USB cable first, confirm PlayStation icons appear at the main menu, then unplug the cable while the game is still running and let the controller reconnect over Bluetooth.

9699

97100 General Troubleshooting

98101

99102 Verify Game File Integrity

100103

101104 Corrupted or missing game files are a common cause of crashes, menu freezes, and failed launches. On Steam, right-click Crimson Desert in your library, select Properties, navigate to the Installed Files tab, and click "Verify integrity of game files." Steam will re-download any files that are damaged or missing.

102105

103106 Clear Steam Download Cache

104107

105108 Open Steam, go to Settings, then Downloads, and click "Clear Download Cache." This forces Steam to re-verify your local files and can resolve launch failures caused by stale cache data.

106109

107110 Add Antivirus Exception

108111

109112 Some antivirus programs (including Windows Defender) may flag the game executable or the anti-cheat module and prevent the game from launching. Add the Crimson Desert installation folder to your antivirus exclusion list.

110113

111114 Xbox PC App Workaround

112115

113116 For players who purchased Crimson Desert through the Xbox PC app and cannot get the game to launch, the most reliable workaround is to disconnect from the internet, restart the computer, immediately launch the game while still offline, allow save data to sync, and then reconnect to the internet. Connecting to the internet before launching the game causes the launch to fail. Also verify that the same Microsoft account is signed into both Windows and the Microsoft Store, and that the PC is registered as a device on the account.

114117

115118 How to Report Bugs

116119

117120 Pearl Abyss encourages players to report new bugs through the official channels:

118121

119122 Official website: Navigate to the Crimson Desert official site, go to News then Notices, and select the "Report an Issue" post for the bug report template.Steam Community: Post in the Crimson Desert Steam Community forums under the Bug Reports section with your system specs, a description of the issue, and steps to reproduce it.Console support: PlayStation and Xbox players can contact Pearl Abyss through the official website or through their respective platform's support channels.

120123

121124 See Also

122125

123126 Day One Patch NotesPatch NotesSystem RequirementsBest PC Settings GuidePerformance and Graphics SettingsControlsFAQs

Compare Revisions

Compare Other Revisions