Cyberpunk 2077 Path Tracing on PC Explained: RT Overdrive, Ray Reconstruction, Upscaling, Frame Generation, and Hardware

Cyberpunk 2077 introduced Ray Tracing: Overdrive Mode in Patch 1.62 as a technology preview and later removed the preview label in Update 2.1. CD PROJEKT RED describes Overdrive as a fully ray-traced, or path-traced, rendering mode rather than the game’s conventional rasterized or hybrid ray-tracing presets. Instead of enabling a smaller collection of ray-traced effects on top of rasterization, the mode uses path tracing for a much larger share of direct and indirect lighting, reflections, shadows, and global illumination.

That distinction matters when comparing settings or hardware. “Ray tracing on” is not one workload: RT Medium, RT Ultra, and RT Overdrive exercise different rendering paths and different amounts of ray-traced work. A result measured with a hybrid RT preset should not be presented as evidence for path-traced Overdrive performance, and a screenshot rendered with path tracing does not prove that the same GPU can sustain interactive frame rates in gameplay.

Real-time path tracing cannot trace an unlimited number of light paths per pixel. The game therefore works with sparse ray samples, temporal information from previous frames, motion data, and reconstruction or denoising stages to estimate a stable final image. Cyberpunk 2077’s Update 2.1 added ReSTIR GI to improve path-traced lighting quality in darker areas while keeping the Overdrive rendering path practical for real-time use.

The practical consequence is that image quality is the product of the path tracer and the reconstruction pipeline together. Raw ray count alone does not describe the final image. Motion vectors, temporal history, denoising/reconstruction, render resolution, camera movement, disocclusion, and the content of the scene can all affect stability. That is also why a reconstruction update can change path-traced image quality without changing the underlying game geometry or material assets.

DLSS Ray Reconstruction was introduced into Cyberpunk 2077 with DLSS 3.5. NVIDIA describes it as a learned reconstruction system that replaces multiple hand-tuned ray-tracing denoisers with one model that uses engine data to reconstruct ray-traced lighting. In Cyberpunk 2077 it is especially relevant to RT Overdrive because the path-traced image begins with sparse ray information that must be reconstructed into a stable displayed result.

Ray Reconstruction and DLSS Super Resolution solve different problems. Super Resolution reconstructs a higher output resolution from a lower internal render resolution. Ray Reconstruction reconstructs ray-traced lighting information. They can operate together, but turning on Ray Reconstruction does not mean the game is necessarily rendering fewer pixels, and choosing a Super Resolution quality mode does not by itself describe which ray-reconstruction model is active. Patch 2.21 added DLSS 4 support and lets GeForce RTX users choose between CNN and newer Transformer models for Ray Reconstruction, Super Resolution, and DLAA.

Temporal upscalers such as DLSS Super Resolution, AMD FidelityFX Super Resolution, and Intel XeSS can reduce the internal resolution used for parts of the rendering workload and reconstruct the image to the requested output resolution. That can reduce GPU work substantially in a path-traced mode, but the result depends on the selected quality mode, output resolution, scene content, and the implementation in the current game version. Native-resolution rendering, DLAA, and upscaling should therefore be treated as different test conditions rather than interchangeable labels.

Frame generation is a separate stage. It inserts generated frames between conventionally rendered frames; it does not make the CPU simulation, input sampling, or base rendered-frame stream run at the generated display-frame rate. Patch 2.21 added DLSS 4 Multi Frame Generation for GeForce RTX 50 Series and faster single Frame Generation for RTX 40/50 Series. Update 2.3 added AMD FSR 3.1 Frame Generation that can be combined with any upscaler, plus Intel XeSS 2.0 with XeSS Frame Generation on compatible hardware.

Because frame generation occurs after a traditionally rendered frame stream already exists, a higher displayed FPS counter is not equivalent to the engine producing that many new simulation and input-response updates. The base render rate still matters for responsiveness, animation sampling, temporal reconstruction input, and how much motion exists between generated frames. That is why vendor performance multipliers that include frame generation should not be read as equivalent increases in CPU simulation rate or reductions in input latency.

For the same reason, compare like with like. A benchmark using Multi Frame Generation, one using single-frame generation, and one measuring only traditionally rendered frames answer different questions. Core Tech Tips should not invent a latency number or declare a universal minimum base FPS. The useful interpretation is structural: generated frames can raise presentation cadence, while the latency and responsiveness of the underlying game remain tied to the real render/input pipeline and any latency-reduction technology in use.

The path-tracing renderer is a game rendering mode, while DLSS, FSR, and XeSS are separate reconstruction and frame-generation technologies layered around the rendered workload. Update 2.3 added support for AMD FSR 4 on compatible AMD GPUs when the required driver is present, FSR 3.1 Frame Generation that can be paired with any upscaler, and Intel XeSS 2.0 with XeSS Frame Generation on compatible hardware. Earlier updates also added FSR 3 Frame Generation and successive XeSS versions.

Feature availability therefore depends on both the game build and the GPU/vendor path being used. NVIDIA-specific Ray Reconstruction is only part of the DLSS path, while FSR and XeSS provide alternative scaling or frame-generation options. Do not infer equal image quality, latency, or performance between them from the fact that they occupy similar menu categories; those are empirical comparisons that require controlled evidence rather than feature-name equivalence.

CD PROJEKT RED’s current support documentation still lists RT Overdrive as an extremely GPU-intensive mode and publishes an Overdrive system-requirement target that includes a GeForce RTX 4080, 16 GB of VRAM, 24 GB of system RAM, and an NVMe SSD for its stated 4K/60 target. The same requirement table explicitly says its RT Overdrive result was measured with DLSS Frame Generation enabled. That is a vendor requirement/target, not an independent benchmark and not proof that every scene will behave identically.

The older Path Tracing support page also documents a Photo Mode path-tracing option for other ray-tracing-capable GPUs, with VRAM thresholds that rise with resolution. Do not turn those Photo Mode thresholds into universal gameplay requirements: rendering one path-traced still image over seconds or minutes is fundamentally different from sustaining interactive gameplay. For a current GPU decision, verify the game version, driver support, available reconstruction/frame-generation path, VRAM capacity, and independent measurements for the exact settings you intend to use.

A useful Cyberpunk 2077 path-tracing result needs enough context to reproduce what was measured: game version, RT Overdrive/path tracing state, output resolution, internal render scale or upscaler mode, Ray Reconstruction state/model, frame-generation mode, GPU and VRAM capacity, CPU, driver version, and the scene or built-in benchmark path. Without that context, two “4K Overdrive” results can represent materially different rendering workloads.

If performance is poor, separate sustained GPU cost from other symptoms. Lowering internal render resolution or disabling expensive path-traced effects can reveal GPU pressure; VRAM exhaustion can create residency problems that are not the same as raw shader/ray-tracing throughput; shader compilation can produce isolated hitches; a CPU limit can cap the base frame stream even when frame generation raises displayed FPS. The existing VRAM, shader-compilation, and CPU-vs-GPU bottleneck guides cover those branches. Avoid a universal “best settings” preset unless it is backed by a defined hardware target and explicit human editorial judgment.