Cyberpunk 2077 launch bugs and PlayStation Store removal
CD Projekt Red's Cyberpunk 2077 launched with extensive bugs, especially on last-generation consoles, prompting Sony to pull it from the PlayStation Store, mass refunds, and a sharp drop in the developer's stock price.
The damage was public. The root cause was preventable.
CD Projekt Red's Cyberpunk 2077 launched with extensive bugs, especially on last-generation consoles, prompting Sony to pull it from the PlayStation Store, mass refunds, and a sharp drop in the developer's stock price.
What the software actually got wrong
The game had not been adequately optimized or quality-tested for the older PlayStation 4 and Xbox One hardware it was still being sold for, and the studio released it on a fixed date despite known, serious performance and stability problems on that hardware.
The game had not been adequately optimized or quality-tested...
The game had not been adequately optimized or quality-tested for the older PlayStation 4 and Xbox One hardware it was still being sold for
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
The studio released it on a fixed date despite...
the studio released it on a fixed date despite known, serious performance and stability problems on that hardware
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.