The First Witcher: The Technical Mess That Founded an RPG Legend

In May 2007, CD Projekt Red launched The Witcher on PC using an engine it didn't build: the Aurora Engine, licensed from BioWare and already outdated after its use on Neverwinter Nights in 2002. The Polish studio, which had never developed an RPG before, overhauled it extensively under tight deadlines, producing a technically unstable game packed with endless loading times and bugs. Nineteen years later, that same studio is preparing The Witcher 4 under Unreal Engine 5, and this botched genesis illuminates a tension that has never truly left the franchise: the clash between creative ambition and technical fragility.

A Recycled Engine, a Team Learning on the Job

CD Projekt was then merely a video game distributor in Poland before launching its development division. Unable to afford building an in-house engine, the team acquired BioWare's Aurora Engine and patched it superficially to integrate more sophisticated lighting, more physical combat, and a decidedly mature tone far removed from Western RPG standards of the era. The result was a game that ran poorly, with frequent stuttering on machines of that time and an artistic vision that vastly exceeded what the engine could handle. The studio improvised, literally: it adapted a tool designed for another game, with limited resources, no safety net.

Manufacturing Defects Become a Signature

What should have sunk the project ended up distinguishing it. Rather than strip down content to secure technical stability, CD Projekt Red chose to push further on writing: moral choices without right answers, unapologetic sexuality, complex local politics drawn from Andrzej Sapkowski's novels. The game imposed a tired, cynical witcher at a time when Western RPGs remained dominated by polished heroes from BioWare or Bethesda. This asymmetry—a fragile technical foundation carried by risk-taking writing—became the studio's trademark long before the company had the resources to match its ambitions.

A Method CDPR Never Really Corrected

The pattern repeated afterward, with varying degrees of severity. The Witcher 2: Assassins of Kings (2011) imposed its own in-house engine, Aurora rebuilt from the ground up under the name REDengine, but still emerged as a technically demanding game for PCs of that era. The Witcher 3: Wild Hunt (2015) finally streamlined the formula and became a genre benchmark, but it was Cyberpunk 2077 (2020) that brutally reminded everyone the tension between ambition and stability never vanished: released in critical condition on consoles of that time, the game required years of patches before reclaiming its reputation. The studio thus doesn't treat technical fragility as an isolated accident from its early days but as a structural risk it accepts on every new project to preserve creative freedom.

What This Means for the Franchise's Future

The shift to Unreal Engine 5 for The Witcher 4, confirmed by CD Projekt Red, changes the studio's technical game for the first time since its founding: no longer improvising with a inherited engine or maintaining a costly in-house REDengine, but relying on an industrial foundation shared with much of the industry. This mechanically reduces the risk of a broken launch like Cyberpunk 2077, but raises another question: part of the franchise's identity actually stemmed from that assumed fragility, that sense the studio pursued its ideas to their limit even at the cost of player comfort. A technically polished Witcher won't automatically be a better Witcher. The first game's history reminds us that CD Projekt Red often made its most radical decisions in instability, and it's that radicality worth recapturing, new engine or not.