← Blog

How to Report a Bug in Crimson Desert (2026): Capture the Glitch or Crash on Video and Send It to Pearl Abyss

Official Crimson Desert screenshot: giant stone pillars breaking apart along glowing cracks in ancient ruins while Kliff, shield on his back, looks on
Image source: © Pearl Abyss · Crimson Desert Enhanced official Steam store screenshot
Key takeaways
  • Crimson Desert bugs are reported through Submit Feedback on Pearl Abyss Support, the page the official site links as Report an Issue. Check the Known Issues notice first (last updated September 21, 2026) to see whether your problem is already listed.
  • The form asks for your platform, game version (the number after “GameVersion:”), platform ID, PC specs, PERS Unique ID and mod use. Attachments are limited to 20MB image, document and log formats, so videos go in as a URL in the Details field.
  • On PC, DOR records Crimson Desert from launch to exit, so you can press F8 to save the last 30 seconds when a bug appears. After a crash, trim the end of that session's full gameplay video before you launch the game again, Like the trimmed clip to keep it, then share it as a link.

Spend enough time in Crimson Desert and something will eventually break: a quest that will not advance, an NPC you cannot interact with, a crash in the middle of a fight. The official way to tell Pearl Abyss is Submit Feedback on Pearl Abyss Support, the page the Crimson Desert website links from its Report an Issue menu. A report is only useful if the team can reproduce the problem, which means it has to show when it happened, where you were, what you did and what went wrong. Plenty of glitches are hard to put into words, so a short video is usually the clearest evidence you can send. The catch is that bugs never wait for you to hit record, and you only find out about a crash after the game has already closed. This guide is based on the Pearl Abyss Support form and help pages as checked on October 16, 2026. It covers what to check before reporting, which category to pick, required fields such as your game version and PERS Unique ID, why video has to go in as a link rather than an attachment, and how to keep the moment of a bug or crash on PC without missing it. The latest patch at the time of writing is hotfix 2.03.02 from September 23, and the Crimson Desert Enhanced: Charting the Unknown DLC is scheduled for October 29 at 15:00 PT (22:00 UTC), so it is worth knowing the process before a big update lands. For automatic recording settings, see Crimson Desert recording with DOR, and for release timing and preparation, see the Charting the Unknown DLC release date guide.

Bottom line: on PC, send files with PERS first, then add the scene to Submit Feedback as a video link

The reporting route depends on your platform. If you play on PC through Steam or the Epic Games Store, start with PERS, the Pearl Abyss Error Reporting System that sits in the game's bin64 folder. PERS automatically sends error dumps, logs, in-game screenshots, save data and your hardware specs, then copies a Unique ID to your clipboard. When you enter that ID in the Submit Feedback form, Pearl Abyss's help page says you do not need to retype your PC specs or attach game files again. On a PlayStation 5, an Xbox console or a Mac, where PERS is not available, you fill in the form by itself. Either way, you cannot attach a video file. The attachment field accepts files up to 20MB in .gif, .jpg, .jpeg, .png, .txt, .log, .doc, .docx, .pdf, .dmp, .erl, .dat, .evtx, .dll, .ini, .json, .heic and .heif formats, and the form asks you to include a URL link for videos instead. So you need three things ready: a video link of roughly 10 to 30 seconds that shows the problem, a note with your game version and reproduction steps, and on PC, your PERS Unique ID. You can create the link with an unlisted YouTube upload or a cloud drive share, and if you recorded with DOR on PC, you can trim the clip in My Clips and create a share link right there. The tool you use for the link matters less than not missing the moment. A bug you can reproduce can be recorded again, but a crash or a one-off glitch only ends up on video if recording was already running when it happened.

How to report a Crimson Desert bug, from checking notices to adding the video link

  1. 1Check Known Issues and the latest patch notes firstThe Known Issues notice under Announcements on the official site lists problems Pearl Abyss is already investigating. As of October 16, 2026, it was last updated on September 21 and includes interactions with NPCs, mounts and certain objects becoming unavailable in some situations (restarting the game is listed as a temporary fix), an issue tied to the Evasion Control setting, and rain disappearing or the screen turning blurry or distorted in rainy areas when FSR4 upscaling is on. Some items have been fixed since: hotfix 2.03.02 on September 23 fixed icons for newly discovered objects in certain regions not appearing on the map. If your problem is on the list, try the listed workaround first. If it is not listed, or keeps happening after the workaround, move on to a report. The notice warns that it may contain spoilers such as quest and boss names.
  2. 2Save the moment the bug appearsSave the scene while the symptom is still on screen. If you have a replay buffer running, a feature that keeps recording in the background and saves the last stretch of gameplay as a file when you press a key, press the save key right there. DOR records Crimson Desert from the moment you launch it, so pressing F8 saves the last 30 seconds as a clip. If you pressed too late or forgot, you can still find the moment in the full gameplay video after you quit, so note the time on your PC clock when the bug happens. If the bug is reproducible, record it once more so the video runs from normal behavior to the moment it breaks. That makes the report much easier to follow.
  3. 3After a crash, secure the footage before relaunching the gamePressing F8 after a crash will not capture the crash. DOR ends and saves the session's recording when the game process exits, so the moments right before the crash sit at the end of that session's full gameplay video. Open it in My Clips, use Trim Section to cut the last 10 to 30 seconds, and Like the trimmed clip, because it is saved in the same session folder as the original. Since the game closed abruptly, also check that the video plays all the way to the end. Do this before you launch the game again. Full gameplay videos are cleaned up by Automatic File Management: once they exceed their space allowance (5GB by default), older session folders, including the F8 clips and trimmed clips inside them, can be removed after your next session ends, and only videos you have Liked are kept. If you have no time to trim right away, Like the full gameplay video so it stays.
  4. 4Note your game version and reproduction detailsThe form asks for your game version. Check the number after “GameVersion:” on the title screen or at the top right of the [Other] → [Settings] menu (the form gives 1.00.XX as the format), and enter “-” if you cannot find it. Also write down your platform (PC - Steam, PC - Epic Store, PlayStation 5, Xbox Series X and so on), your platform ID (Steam ID, PSN ID, Xbox Gamertag, Epic Games Store ID or Apple ID), the region and quest name, what you did just before, and how many attempts reproduced the problem. If you play with mods, say so in the form, and if possible check whether the same problem happens with mods turned off.
  5. 5On PC, send error files with PERSFor the Steam version, right-click Crimson Desert in your Library, choose Manage > Browse local files and open the bin64 folder. For the Epic version, go to the Crimson Desert\bin64 folder inside C:\Program Files\Epic Games. Run PERS.exe, select the type of issue, write a short explanation of at least 10 characters and send it. The Unique ID is copied to your clipboard automatically, so paste it into a note right away. Pearl Abyss strongly recommends this method because it provides the most detailed information.
  6. 6Trim the video and turn it into a linkBecause the form does not take video files, you need a link. A clip that starts a few seconds before the problem and ends once the symptom is clearly visible, roughly 10 to 30 seconds, is quick for the team to review. You can upload it to YouTube as unlisted, share it from a cloud drive, or in DOR use Trim Section in My Clips and then Share to create a link (sign-in required). Sharing posts the video to DOR; visibility defaults to Public, and choosing Unlisted limits it to users who have the link. Open the link in a private browser window to make sure people who are not signed in can play it. If your mic or a Discord call was recorded too, listen before sharing and cut out anything that should not be there.
  7. 7Fill in Submit Feedback and send itOn the Crimson Desert page of Pearl Abyss Support, click Submit Feedback and choose a category. The top-level categories are Gameplay, Game Launch Issues, Technical Issues / Performance, Other and Cross-Save; a crash, for example, goes under Technical Issues / Performance > Game Crash. Fill in your platform, game version, platform ID, PC specs (optional if you used PERS), whether you used PERS and your Unique ID, and mod use, then agree to the collection and use of personal information. The form states that you cannot submit bug or error reports without that consent. Put the symptom in one line as the Subject, write the reproduction steps and the video URL in Details (at least 10 characters), and add screenshots or logs under Attach File(s). If the page asks you to log in, sign in with your Pearl Abyss ID. According to the confirmation message, Pearl Abyss replies only if it needs more information, so follow later patch notes and the Known Issues notice to see whether your bug was fixed.

Which category to pick and what evidence to send (checked October 16, 2026)

ProblemCategory to pickEvidence to include
A quest will not progress (an NPC does not appear, the objective does not update)Gameplay > Main Quest or Faction QuestVideo link starting just before you got stuck, quest name, screenshot of the quest step
Combat or controls behave strangely (an input does nothing or triggers the wrong action, and so on)Gameplay > Combat or MechanicsVideo link that shows both your input and the result, screenshot of your control settings
Abyss content cannot be progressedGameplay > Abyss ContentVideo link of the device or object that does not respond, a note of the location
UI or graphics break, the screen turns blurry or distortedGameplay > User Interface & VisualVideo link showing the symptom, screenshot of your upscaling and graphics settings
The game crashes during playTechnical Issues / Performance > Game CrashPERS Unique ID, video link cut from the end of the full gameplay video, the time of the crash
Frame drops, stutter or other performance problemsTechnical Issues / Performance > Technical Issues / PerformancePERS Unique ID or your CPU, GPU, RAM and display type, video link of the stuttering section
An install or update fails, or the game will not startGame Launch Issues > Installation / Download or Startup IssueScreenshot of the error message (.png and similar), plus a PERS Unique ID if you can run PERS

Before you click Submit

  • I checked the Known Issues notice and the latest patch notes for the same problem.
  • I noted my game version (the number after “GameVersion:”), platform and platform ID.
  • I wrote down the location, quest name, what I did just before and the reproduction steps.
  • On PC, I sent a report through PERS and saved the Unique ID.
  • I trimmed the video to roughly 10 to 30 seconds, made a link and confirmed it plays in a private browser window.
  • I checked that the video and attachments contain no Discord conversations or personal details such as phone numbers or addresses.
  • I answered the mod question honestly, and if I use mods, I checked whether the problem also happens without them.
Record reproductions so that “normal, then broken” is visible in one take. If the video only shows the screen after the problem appeared, the team has to guess what triggered it; if your last input and the result play back to back, it is much faster to confirm. Writing down the time on your PC clock when a bug happens also lets you jump straight to that point in the full gameplay video, even if you never pressed the clip key.

Saving Crimson Desert bug footage with DOR: automatic recording, F8 for the last 30 seconds, trimming the moments before a crash

DOR is a free Windows PC app. When you launch Crimson Desert on PC (the CrimsonDesert.exe executable), DOR detects it, starts recording automatically and keeps the whole session as one full gameplay video until you quit. On a personal PC this recording is on by default, and you can turn it off per game under Settings > Game > Full gameplay recording. Press F8 while recording to save the last 30 seconds as a separate clip while the full recording keeps going. You can choose 15, 30, 45 or 60 seconds under Settings > Highlight > Highlight Length and you can change the hotkey, but neither can be changed while recording, so set them before you launch Crimson Desert. Recording ends when the game process ends, so crash footage is at the end of that session's video. If the game was force-closed, check in My Clips that the video plays to the end. Trimmed clips can be exported in 16:9, 9:16 or 1:1 from Trim Section, and Share creates a link you can paste into your report. Mic Recording and Record All Sounds are on by default, which means everything playing on your PC, Discord included, goes into a single audio track. To keep only the game window's sound and your mic, turn off Record All Sounds under Settings > Audio. Check your free space as well: DOR warns you when free disk space drops below 30GB, and at 20GB or less it will not start recording and stops a recording in progress. For ways to free up space, see how to fix low disk space for game recording. With Automatic File Management (30GB by default) turned on, older videos are cleared first and Liked videos are kept, so Like any footage you plan to report. The same F8 habit also works for saving a clean boss kill, as covered in how to rematch bosses in Crimson Desert. There are limits to keep in mind. DOR does not detect bugs or crashes and create clips on its own, Crimson Desert has no automatic highlight clips, and DOR cannot record Crimson Desert played on PlayStation 5, Xbox consoles or Mac.

Recording that starts when your game does: free game recorder for PC →

FAQ

FAQ

Can I attach a video file to a Crimson Desert bug report?

Not in the Submit Feedback form as checked on October 16, 2026. Attachments are limited to 20MB and to image, document and log formats such as .gif, .jpg, .png, .txt, .log, .dmp and .pdf, and the form asks you to include a URL link for videos. Upload the video to YouTube as unlisted or to a cloud drive, or create a link with Share in DOR, confirm it opens in a private browser window, and paste it into Details.

If I press F8 right after Crimson Desert crashes, is the crash saved?

No. DOR ends the session's recording the moment the Crimson Desert process exits, so F8 cannot reach back to the game footage before the crash. The crash is at the end of that session's full gameplay video. Before you launch the game again, trim the end of it with Trim Section in My Clips and Like the trimmed clip, or, if you have no time, Like the full gameplay video to keep it. Also check that the video plays to the end.

How do I report a Crimson Desert bug on PS5 or Xbox?

Use the same Submit Feedback form, choose PlayStation 5, PlayStation 5 PRO, Xbox Series X or Xbox Series S as your platform and enter your PSN ID or Xbox Gamertag. PERS is for PC only, so answer that you did not use it. DOR is a Windows PC app and cannot record console gameplay, so capture the video with your console's own capture feature, turn it into a link and add it to Details.

Games

Related game guides

Read next

Related articles

Get started with DOR

After DOR detects the game, press one hotkey to save the moment you choose as a clip