Skip to content
Crimson Desert official wordmarkCrimson Desert Guide
Technical CentreKnown issues, diagnostics and performance
CurrentPatch 2.00.02

PC Graphics & Performance

A controlled PC tuning and fault-isolation ladder for image quality, frame pacing, crashes and current Version 2.00.02 status.

Evidence
Official source
Verified
2026-09-01
Spoilers
No spoilers

Patch 2.00.00 PC language support

Section titled “Patch 2.00.00 PC language support”

On Steam, select the preferred language under Library → Crimson Desert → Properties → Language, start the game to download the data, then choose the game and voice language in-game. Epic Games Store uses the title’s Options menu before Apply.

The GTX 1060 FSR-plus-Frame-Generation white screen and FSR 4 rainy-scene defects remain active Known Issues.

Version 2.00.01 fixes frame-rate drops in unspecified situations. Pearl Abyss did not publish an affected scene, hardware class, setting or target frame rate, so this is a regression marker rather than a performance guarantee. Re-test the same route and settings on Version 2.00.02 before changing unrelated options.

Use this page to make one measured change at a time. It does not promise a universal frame rate: Pearl Abyss states that published performance results are internal tests, and real results depend on hardware, drivers, resolution, scene and settings.

Patch 1.18.02 stability history

Section titled “Patch 1.18.02 stability history”

Patch 1.18.02 fixes player movement animation stuttering or appearing unnatural and characters becoming unresponsive after using a shop. Reproduce any recurrence once on a confirmed 2.00.02 build, preserve saves and record the exact movement state or shop interaction before changing unrelated settings.

Patch 1.18.01 previously fixed unexpected closure after launch. Patch 1.18.00 remains the graphics baseline: it corrected indoor lighting instability, camera jitter or shake at low frame rates, and corrupted output from FSR/XeSS Frame Generation on some lower-end GPUs.

Sources: Official Patch 1.18.02 · Official Patch 1.18.01 · Official Patch 1.18.00 · Current Known Issues

Establish the baseline

Section titled “Establish the baseline”

Record:

  • CPU, GPU and RAM;
  • Windows version;
  • launcher and game version;
  • GPU driver;
  • display resolution and refresh rate;
  • graphics preset;
  • upscaler and quality mode;
  • frame generation state;
  • ray tracing, Ray Reconstruction or Ray Regeneration state;
  • HDR state;
  • the exact scene and action used for testing.

Confirm the system meets Pearl Abyss’s current requirements before diagnosing settings.

Supported technologies

Section titled “Supported technologies”

Pearl Abyss officially lists:

  • AMD FSR 3 and 4;
  • NVIDIA DLSS 4 and 4.5;
  • Intel XeSS 3;
  • AMD FSR Ray Regeneration;
  • NVIDIA DLSS Ray Reconstruction;
  • frame generation on PC.

Patch 1.16.00 implemented AMD FSR SDK 2.3.0, added FSR Upscaling 4.1 support for Radeon RX 7000-series GPUs and updated Ray Regeneration to 1.2.0.

Tuning ladder

Section titled “Tuning ladder”
  1. Start from a stable preset.
  2. Set the intended output resolution and refresh rate.
  3. Choose one upscaler and disable competing reconstruction options.
  4. Test without frame generation to establish real render performance.
  5. Reduce the settings with the greatest visible scene cost.
  6. Retest the same route for several minutes.
  7. Enable frame generation only after base frame pacing is stable.
  8. Add HDR and advanced ray features one at a time.
  9. Keep the final settings only if a save-and-reload test remains stable.

Stutter diagnosis

Section titled “Stutter diagnosis”
  • repeat the same route to separate shader or asset warm-up from persistent stutter;
  • close overlays and capture tools one at a time;
  • confirm the game is on the intended GPU;
  • check temperature and clock behaviour without changing overclock settings;
  • compare frame pacing before comparing average frame rate;
  • test a capped frame rate below the unstable peak;
  • record whether the fault begins after a menu, cutscene, fast travel or character switch.

Crash diagnosis

Section titled “Crash diagnosis”
  1. Preserve saves.
  2. Return CPU, GPU and memory tuning to known-good settings.
  3. Verify game files through the installed launcher.
  4. Record the current driver before changing it.
  5. test with overlays disabled;
  6. test the exact failing action once;
  7. collect the crash time, location and action;
  8. check the current patch notes and Current Known Issues;
  9. submit a reproducible report if the fault remains.

Do not delete saves or configuration folders as a first response.

Image-quality diagnosis

Section titled “Image-quality diagnosis”

For blur, ghosting, flicker or unstable edges:

  • compare native output with one upscaler;
  • disable frame generation temporarily;
  • test depth of field, motion blur and sharpening separately;
  • confirm dynamic resolution is not changing the test;
  • verify the display is using the intended resolution and HDR mode;
  • capture the same frame with settings and patch recorded.

Official sources

Section titled “Official sources”