REDscope

REDscope

Crash reports you can actually read

▍ WHAT REDSCOPE DOES

When Cyberpunk 2077 crashes, REDscope saves what it can see into a plain-text .crash report. It also creates a matching .crash.json file with extra details for the person investigating the crash.

The report gives you a place to start. It can show which plugin or part of the game was active, what scripts were running, whether the same crash has happened before, what changed since your last launch, and whether memory or graphics problems were present.

REDscope does not upload anything. The files stay on your PC until you choose to share them.

READ THE CRASH REPORT GUIDE

Start here after your first report. The guide explains what each clue means, what it does not prove, and what to test next.

▍ AFTER A CRASH

• []Open the newest .crash file in red4ext/plugins/REDscope/crashes. Mod Organizer 2 users will find it under Overwrite.[/]

  []Read the LIKELY CULPRIT line and its confidence level. Treat it as the best lead, not proof.[/]

  []Check the CRASH ID. If another report has the same ID, you are probably looking at the same failure again.[/]

  []Use the crash-report guide before removing a large part of your modlist.[/]

  []When asking for help, attach the matching .crash and .crash.json. Say what you were doing, whether it repeats, and what changed before it began. Other matching files can be supplied if the person investigating asks for them.[/]

  ---

  ▍ THINGS REDSCOPE ALREADY RECOGNIZES

  REDscope includes known crash patterns. Here are a few examples:

  []Running out of memory. It can tell the difference between the GPU running out of video memory and Windows reaching its total memory limit. Low headroom by itself is shown as pressure, not automatically called an out-of-memory crash.[/]

  []Graphics driver and upscaler crashes. It recognizes GPU resets and faults inside common driver, DLSS, Frame Generation, FSR, and XeSS files. The report also records the graphics settings and driver version that were active.[/]