GitHub Issue
[Bug]: 007 First Light — Washed-out/blown-out white image with NR enabled, upscaling fails with 0xbad00005
### Environment
* **Game:** 007 First Light (Steam, Retail)
* **Graphics API:** DirectX 12
* **DLSS 5 Swapper:** v2.1.1
* **Add-on:** RenoDX DLSS5 Generic v4.6 (build Aug 31 2026 / ReShade API v18)
* **GPU:** NVIDIA GeForce RTX 5070 Ti Laptop GPU
* **Driver:** 616.56
* **Display:** 3840×2160 @ 120 Hz, 8-bit RGB, SDR (`ColorSpace = 0` / Rec.709)
* **HDR:** Disabled in Windows 11 and disabled in game
---
### Description
Immediately after patching the game with DLSS 5 Swapper v2.1.1, the entire in-game image becomes severely washed-out / blown out white.
* Toggling Neural Rendering **OFF** via `F6` immediately restores standard, correct rendering.
* Toggling NR back **ON** instantly reintroduces the washed-out white clipping.
* Adjusting RenoDX / ReShade overlay parameters (`NR Intensity`, `Color Strength`, `Transfer`, `Paper White`) does not alleviate the white washout.
---
### Log Analysis & Key Findings
1. **Upscaling Failure (`0xbad00005`):**
When attempting low-resolution contract upscaling (`1280x720 -> 3840x2160`), the runtime explicitly rejects the color contract:
```text
[DLSS 5 Neural Rendering] DLSS5 Generic: created inline NR resources 1280x720 -> 3840x2160 (upscaling) format=10
[DLSS 5 Neural Rendering] DLSS5 Generic: feature 18 created via the signed snippet after DLSS/DLAA for NR input 1280x720 -> output 3840x2160 with guides 1280x720
[DLSS 5 Neural Rendering] DLSS5 Generic: feature 18 evaluate failed with 0xbad00005; the game DLSS output was retained (th...
View Raw Thread
SaaS Metrics