Cyberpunk 2077 (PPSA03974 / PPSA04029)

[klosixgaming-arch]

Game Bring-up: Cyberpunk 2077 (PPSA03974 / PPSA04029)

• Platform / OS: Windows 11 (build 26200)
• GPU: NVIDIA GeForce RTX 5090, driver 617.42
• Status: reaches the main menu and the character customization screen, at 0.3 to 17 FPS depending on the scene. Needs PR fix(agc): support packed 16-bit storage images #6218 (packed 16-bit storage images, open). The clip stop is fixed on main by fix(agc): accept PA_CL_CLIP_CNTL CLIP_DISABLE without depth clamp #8046 (merged).

Stops and fixes

1. [gpu] driver failure: compute shader 0x1aa4f07500: AGC graphics: guest storage texture format 4 cannot be used as a storage image (about 160 s in, on main b13183e). Fixed by fix(agc): support packed 16-bit storage images #6218. With fix(agc): support packed 16-bit storage images #6218 merged onto main c70524a the title ran 440 s without this stop.
2. unsupported PA_CL_CLIP_CNTL flags is unsupported (register 0x204 = 0x00090000) (Cyberpunk 2077 (PPSA04029): draws refused for PA_CL_CLIP_CNTL CLIP_DISABLE (register 0x204 = 0x00090000) once #6218 accepts the packed storage format #6806). Fixed on main by fix(agc): accept PA_CL_CLIP_CNTL CLIP_DISABLE without depth clamp #8046; the 440 s run above was built before fix(agc): accept PA_CL_CLIP_CNTL CLIP_DISABLE without depth clamp #8046 and stopped here.
3. storing storage image results pending over memory outside the write watch without the guest bytes saved before them is not implemented: seen in earlier runs; open PR fix(agc): save the guest bytes of results that become pending over a surface that is no longer fully write-watched #7048 addresses it. The run with fix(agc): support packed 16-bit storage images #6218 alone did not hit it in 440 s. Not re-tested on current main.

Open PRs this title needs

• fix(agc): support packed 16-bit storage images #6218 (packed 16-bit storage images)
• fix(agc): save the guest bytes of results that become pending over a surface that is no longer fully write-watched #7048 only if stop 3 comes back

Current bottlenecks (10 s summaries, 3200x1800)

• Intro and early menus: 9 to 17 FPS. Queue worker 0 is about 98% busy, mostly compute dispatch resource setup.
• A middle stretch: about 2 FPS with the GPU busy about 60 ms per frame.
• Heaviest stretch: 0.2 to 0.6 FPS. Per frame about 1.5 s in Driver.Packet.memory_wait, 1.1 s in draw resource release, 1.0 s in Resources.Complete, 0.8 s in dispatch; draws spend about 6 ms each in resident render-target lookups. Both queue workers sit at about 100%.
• More than 7,700 synchronous batch.SubmitAndWait() calls from StorageTexture uploads while a scene is composed.
• Pink/magenta tiled pixels on the bottom UI letterbox panel (DCC / fast-clear mismatch), not investigated.

Next

Testing open performance PRs on this title with same-scene before/after summaries.

AI-assisted: yes. Written with AI assistance and reviewed by me.