FrameReady guide

Cyberpunk 2077 Patch 2.31: Pink Screen, Path Tracing, AutoDrive, and PC Fixes

Patch 2.31 is Cyberpunk 2077's current official patch page as checked July 17, 2026. It is not a new July 2026 release. Its useful PC fixes cover a pink screen caused by disabled NVIDIA Reflex with DLSS Frame Generation, Path Tracing failing to activate in some scenes, and ray-traced reflections not appearing correctly under some conditions.

Check Cyberpunk 2077 readiness All guides

Bottom line

If Cyberpunk 2077 shows a pink screen with DLSS Frame Generation, install Patch 2.31 and retest before changing config files. If Path Tracing does not activate or ray-traced reflections look wrong, update first and test a controlled scene. Do not stack random tweaks until you know whether your symptom is one CD Projekt Red specifically fixed.

Use your current hardware for a readiness check before assuming a patch needs an upgrade.

Check Cyberpunk 2077 readiness

Evidence status

official: FrameReady uses this label so predictions, official claims, and unknowns do not get mixed together.

What Patch 2.31 officially fixes on PC

CD Projekt Red lists three PC-facing graphics fixes that are useful for symptom matching. The notes do not say every pink screen, frame-generation issue, or ray-tracing problem has one cause.

The patch fixes a pink screen that could appear when NVIDIA Reflex was disabled while DLSS Frame Generation was enabled.
It fixes Path Tracing not activating in some cases.
It fixes ray-traced reflections not rendering correctly in some situations on PC and Mac.
These are patch-note fixes, not official performance benchmarks or new PC requirements.

Test the change without hiding the cause

A controlled retest is more useful than changing every graphics option at once. It makes a remaining bug easier to describe and avoids mistaking a different setting for a fix.

Confirm that the installed game is on Patch 2.31 or later.
Write down the display mode, upscaler, frame-generation setting, NVIDIA Reflex setting, and ray-tracing preset before changing anything.
Use the same save, location, and short route for before-and-after checks.
If the pink screen was tied to DLSS Frame Generation, retest that combination after updating before editing files or reinstalling drivers.
If the symptom remains, report the exact setting combination and scene rather than claiming Patch 2.31 failed for every system.

AutoDrive and quest fixes

Patch 2.31 is not only a graphics patch. Its gameplay fixes are specific enough that a player can verify them directly instead of treating every driving or quest problem as unresolved.

AutoDrive improves overtaking and is less likely to stop at traffic lights when it does not need to.
Free Roam AutoDrive follows traffic rules more reliably.
The patch addresses progression issues in Freedom, Motorbreath, and Nitro (Youth Energy).
It also addresses a crash that could happen after leaving the Yaiba showroom in Nitro (Youth Energy).

Mac fixes have their own scope

The patch notes include Mac-specific fixes. They should not be treated as proof of the same cause on Windows or another platform.

CD Projekt Red lists a white screen during braindance when frame generation was enabled on Mac.
It also lists Mac fixes for HDR defaults and an incorrect Screen Space Reflections preset.
Mac players should match their exact symptom to the official note before borrowing a PC-only graphics workaround.

Questions players are searching

Direct answers with the patch date and scope kept clear.

Q: Is Cyberpunk 2077 Patch 2.31 a new 2026 patch? A: No. The official Patch 2.31 page is dated 2025. It was the current official patch page checked for this guide on July 17, 2026.
Q: Does Patch 2.31 fix every Cyberpunk pink screen? A: No. CD Projekt Red specifically names a pink screen when NVIDIA Reflex is disabled while DLSS Frame Generation is enabled.
Q: Do I need a new GPU for Patch 2.31? A: The notes do not announce new PC requirements. Update and retest the named symptom first.
Q: Why is Path Tracing still not working? A: Confirm the patch version and retest a controlled scene. The note says it fixes activation in some cases, not every possible graphics issue.