Report / Published 2026-10-30

Phantom Blade Zero's day-one patch arrives with an Nvidia driver rollback warning

The 5 GB PC update sharpens ray tracing and path tracing and reworks rasterisation. S-Game also tells players on Nvidia's 621.01 driver to drop back to 617.42 and stay there.

A close view across the angled metal fins of a graphics card heatsink, with warm amber light glowing between the fins and a cool highlight along the top right edge.
Conceptual editorial illustration; not a photograph of a specific graphics card.

THE SHORT VERSION

  • S-Game marked Phantom Blade Zero's 29 October launch with a Steam post titled Reason and Madness, announcing a day-one patch of roughly 5 GB on PC and 2 GB on PS5, where it installs as version 1.301.524.
  • IGN reports the patch improves ray tracing and path tracing and reworks rasterisation so the art direction holds with ray tracing off; S-Game also encourages handheld and lower-end PC testing.
  • The studio says Nvidia's 621.01 driver has unstable performance in the game and recommends rolling back to 617.42 with a clean install until Nvidia ships its next driver, which PC Gamer notes has no announced date.

A 5 GB update that is mostly about light

Phantom Blade Zero released on 29 October 2026, and S-Game marked the day with a Steam post titled "Reason and Madness" that walks through the studio's earlier projects before arriving at three practical notices. The first is the day-one patch. S-Game puts it at roughly 5 GB on PC; IGN reports 2 GB on PlayStation 5, where it installs as version 1.301.524. Anyone who pre-loaded has to download it before launching, and anyone who did not pre-load receives the same build with the purchase.

The notes are narrow and rendering-focused. IGN says the update improves ray tracing and path tracing, and that it reworks rasterisation so the art direction still reads with ray tracing switched off; the studio's wording is that the rasterisation work keeps "the scene's art style perfectly conveyed, even with ray tracing disabled." That second half is the part that applies to most PCs, because ray tracing is the optional expensive path and rasterisation is what runs without it. Neither report publishes a frame-rate comparison for either path.

One driver version, named and avoided

The second notice is the one that travelled. IGN quotes S-Game saying, "We found that Nvidia's latest driver 621.01 has some unstable performance issues," and PC Gamer records the recommendation in full: "Based on our testing, version 617.42 currently offers the best experience in Phantom Blade Zero. If you've installed a driver newer than 617.42, we recommend rolling back to 617.42 and choosing the clean installation option. Please stay on this version until Nvidia releases its next driver update, which we expect to arrive soon."

Nvidia's 621.01 Game Ready Driver shipped on Wednesday 21 October, PC Gamer reports, and was presented partly as better support for DLSS and ray tracing in Phantom Blade Zero, Call of Duty: Modern Warfare 4 and NBA 2K27. The driver that was meant to help this game is therefore the one its developer now says to avoid. PC Gamer is explicit that S-Game does not explain what goes wrong, only that the older version gives a better experience, so the size of the problem is unknown.

Rolling back takes a few minutes

PC Gamer lays out both routes. Through the Nvidia App: open it, click Drivers, scroll down to the version you want, click the three dots beside that entry and install. Without the app: open Device Manager, expand Display Adapters, right-click the graphics card, choose Properties, go to the Driver tab and roll back from there. Neither route costs anything, and the version you want stays listed in the app's driver history.

The studio asks for a clean installation, which drops the previous driver's settings, and asks players to hold at 617.42 until Nvidia ships the next release. Neither source says when that is. PC Gamer reports there is no timeline yet and that S-Game expects one soon, which is the studio's expectation rather than an Nvidia commitment. Someone who is not playing this week can wait for the next driver instead of rolling back and then updating again.

The advice changed within days of launch

PC Gamer describes the reversal plainly: "Yes, that's the opposite of developer S-Game's pre-launch advice." Recommending the newest driver before a large release is the standard move, and S-Game made it, then pointed the other way on launch day. Changes of this kind are common when a launch build and a driver land in the same week, because neither the studio nor the driver team has finished testing one against the other. What is unusual is the placement, since the studio put the warning on the same Steam page as the patch rather than leaving it to players to find.

What the two reports do not contain is the mechanism. There is no frame-time capture, no list of affected GPUs, no note on whether the instability sits in ray tracing, DLSS frame generation or something else, and no comment from Nvidia. Without that, a reader cannot tell whether the problem is a stutter, a crash or a drop in one scene. The recommendation is still actionable, but it is advice without a diagnosis, and treating it as a verdict on the driver as a whole would go past what either outlet reports.

Handhelds: tested, but not yet Verified

The third notice is an invitation to try the game on handhelds and on lower-end and mid-range PCs, which IGN ties to the rasterisation work. IGN adds that Phantom Blade Zero is not yet Steam Deck Verified by Valve, and that S-Game says handheld devices were "extensively tested", which suggests the verification step is close without confirming it. IGN's own phrasing is that verification is likely just around the corner.

The distinction matters when you are deciding what to install on. "Extensively tested" is the developer's claim about its own build; Verified is Valve's label, awarded after Valve's own checks, and it covers input, text size and suspend behaviour as well as frame rate. A patch that improves rasterised lighting can make a handheld session better without moving that label. Neither report says whether a dedicated preset exists or which settings it uses.

What neither report answers

Several things a buyer would want are absent from both reports: how much faster 617.42 actually is, which scenes degrade on 621.01, whether the problem affects every RTX card or a subset, and what Nvidia says about it. There is also no word on whether the PlayStation 5 build has an equivalent issue, though a console has no driver layer for players to manage and its patch is the smaller of the two.

This site's earlier file covers the launch rather than the patch: the launch-day report handles concurrent players and the sales estimates, which is a separate event from this one. Valve's position on AI clones and Epic's account of AI-assisted engine work cover the platform and tooling side of PC development. The practical summary is short: install the 5 GB update, check the driver version, and roll back only if you are on 621.01 or newer.

Sources & reporting limits

  1. Phantom Blade Zero dev says don't get the latest Nvidia drivers
  2. Phantom Blade Zero Day-One Update Brings Performance Improvements, Nvidia Driver Warning
Keep the thread.

Follow PC games to find related stories on your next visit.

THE WEEKLY EDIT

The week, made clear.

Stories worth understanding, brought together in one weekly edition.

Share this page

Instagram, TikTok & other apps

Copy the page link, then paste it where your chosen app supports links. You choose whether to send or publish.