The Witcher IV’s first gameplay reveal traded cinematic promises for something more useful: a working vertical slice. CD Projekt Red showed Ciri hunting a contract in a living region, and the demo gave a concrete look at how the studio’s first Unreal EngineUnreal Engine. A widely-used commercial game engine from Epic Games; powers many large-studio (AAA) games. UE5 is the current generation. 5 project actually moves, fights, and renders. Here is what the footage tells us about the systems underneath.

What it covers: What the vertical-slice demo shows about Ciri’s mechanics, combat, and UE5 rendering. Why it matters: A working slice beats cinematic promises — it shows how CDPR’s first UE5 project actually moves. Who should pick this: Witcher fans and RPGRPG. Role-Playing Game — a game built around character progression, story, and player choices. watchers tracking the release window.

Ciri as the Protagonist: New Mechanics, New Identity

The most consequential reveal is structural, not narrative. Ciri replaces Geralt as the player character, and that decision reshapes the moment-to-moment play.

What changes with Ciri

  • Mobility toolkit. The demo showed traversal options that go beyond Geralt’s dodge-and-roll dance. Ciri’s Elder Blood heritage from the books and Wild Hunt suggests a faster, more vertical combat style — repositioning and mobility options Geralt never had. How the final game frames these abilities remains to be seen.
  • No fixed witcher school identity yet. Geralt carried the Wolf School’s sign-and-sword loadout. Ciri’s build path is less prescribed, which suggests CDPR is opening up skill-tree choices rather than committing to a canonical kit.
  • Signs and melee balance. The demo mixed sword work with magic use, but the exact sign lineup and resource mechanics were not fully legible from the footage. Combat appears to reward aggression and repositioning over the parry-heavy rhythm of The Witcher 3.

The risk and the opportunity

Swapping protagonists is the cleanest way to justify a redesign of combat without alienating players who memorized Geralt’s animations. The downside: Ciri’s power level in the books and Wild Hunt was extraordinary, so CDPR has to flatten that fantasy into a leveling curve without making her feel nerfed. The demo’s early-game pacing suggests they’re starting her relatively grounded and letting the player grow into the flashier abilities.

Combat: Reading the Demo Frame by Frame

The combat sequence — a contract against a large creature — is the demo’s most data-rich segment.

Core loop

  1. Preparation. The player gathered information, brewed oils, and selected gear before the fight. The preparation phase from The Witcher 3 survives and is foregrounded again.
  2. Engagement. Light/heavy attack chains, dodges, and sign casts wove together. Animation commitment looked shorter than Geralt’s — attacks appeared more cancellable, which fits a faster character.
  3. Monster-specific tools. Oils and signs had visible effect reactions, suggesting the elemental weakness system is intact and still meaningful rather than cosmetic.

What the footage implies about feel

The camera and lock-on framing looked closer to an action-RPG than the older third-person combat. Hit reactions on the target were pronounced, and stagger appeared tied to specific attacks rather than a global poise bar. If that holds in the final game, it means the player reads individual moves rather than spamming a safe combo — a design direction more in line with modern action combat than Wild Hunt’s weightier model.

One caveat: demos are scripted to look good. Whether the final AI reacts this responsively under live conditions remains unverified.

The Open World: Contracts, Ecology, and Pacing

The demo took place in a single region, and the world systems shown were more interesting than the skyline.

Reactive ecology

  • The monster hunt opened with environmental investigation — tracks, kills, NPC testimony. This is the Witcher contract formula refined, not reinvented.
  • The creature’s behavior in the world (pacing, territory, reaction to the player’s approach) suggested a predator-prey simulation layer rather than a scripted boss arena. CDPR has spoken about systemic creature and world behavior in past development discussions; the demo is the first time it looked legible on screen.

Density vs. sprawl

The Wild Hunt drew criticism for map bloat and question-mark fatigue. The demo did not show the full map, so we can’t confirm CDPR has tightened the content distribution. What we did see — a focused contract with a clear beginning, middle, and payout — implies the team is privileging authored beats over radiant filler, at least for headline quests.

Unreal Engine 5: Why the Switch Matters

The Witcher IV is CD Projekt Red’s first major title on Unreal Engine 5, replacing the proprietary REDengine that powered Cyberpunk 2077 and the prior Witcher games.

What the engine change buys

  • Asset pipeline and hiring. UE5 is the most widely taught commercial engine in the industry. CDPR can hire faster and onboard contractors without a months-long REDengine course. For a studio scaling to a new trilogy, that is a pragmatic decision before it is a creative one.
  • Nanite and Lumen. The demo’s terrain detail and dynamic lighting are consistent with Nanite (virtualized geometry) and Lumen (real-time GI) being active. The forest floor and interior lighting held up under camera scrutiny in a way REDengine titles typically achieved only in tighter scenes.
  • World Partition. UE5’s streaming system supports large open worlds without manual level slicing. This aligns with CDPR’s stated goal of a seamless open world and should reduce the pop-in and streaming hitches that marred Cyberpunk 2077 at launch.

What it costs

  • REDengine’s bespoke systems are gone. The dialogue and quest tooling CDPR built over a decade was REDengine-native. Rebuilding equivalent authoring tools in UE5 is non-trivial and a likely source of schedule risk.
  • Optimization is now shared with Epic. Performance ceilings on base consoles depend on UE5’s rendering pipeline as much as CDPR’s art direction. The demo ran on a base PS5 at 60fps with ray tracingray tracing. A rendering technique that simulates how light bounces, for realistic shadows, reflections, and lighting — costly to compute., which is a good signal, but a tech demo is not a shipping open world.

Hardware and Platform Read

The platforms are confirmed for PC, PS5, and Xbox Series X|S. No Switch 2 version has been announced.

Console baseline

With the demo running on a base PS5, CDPR is targeting the current-gen floor rather than gating the game behind a Pro refresh. That is the right call for an RPG aiming at mass adoption, but it means PC players shouldn’t expect the demo’s fidelity to be the console default — console settings will trade geometry and shadow quality to hold frame rate.

PC expectations

  • UE5 titles scale heavily with VRAMVRAM. Video RAM — memory on the graphics card used for textures and frames; more of it lets you run higher settings.. A 12GB card is a reasonable floor for high settings at 1440p; 16GB is safer for longevity over a long RPG campaign. Final requirements have not been announced, so these are estimates based on UE5’s typical scaling.
  • Frame generation and upscaling (DLSS/FSR/XeSS) will almost certainly be supported given the engine. Whether CDPR ships a native frame-rate target above 60 on PC depends on final CPU-side simulation load, which the demo can’t fully reveal.

The Unanswered Questions

The demo answered the “does it run and does it move well” question. It did not answer the harder ones:

  • How long is the campaign, and how does side content scale? A reveal demo can’t show pacing across 80 hours.
  • How deep is the skill tree? We saw abilities in action, not the full progression graph.
  • How does choice and consequence work? The Witcher series’ reputation rests on branching outcomes, none of which a combat demo can demonstrate.
  • Release timing. CDPR has not committed to a window. Industry reporting has pointed to a release no earlier than 2027, but nothing in the demo confirms a ship date.

Sources & further reading

Next read