Imagine launching your game and, in the same breath, asking players to uninstall part of their graphics driver. That is roughly what happened around Phantom Blade Zero's release this week, and it is a handy case study even for teams that will never ship a game this big.

What S-Game said about the patch

According to Wccftech, Notebookcheck and TwistedVoxel, developer S-Game prepared a day-one patch of about 5 GB on PC (roughly 2 GB on PS5, per one of the reports). The studio says it should noticeably improve ray-tracing and path-tracing performance and fix some bugs, and coverage also mentions loading times and rendering performance. Players who pre-downloaded get it automatically, and new downloads already include it. No frame-rate figures have been published yet.

A driver the studio would rather you skip

The more unusual part is the advice attached to the patch. As reported by Wccftech and Tbreak, S-Game says Nvidia's latest driver, 621.01, "exhibits unstable performance in certain situations," and that its own testing found version 617.42 gives the best compatibility with the game. Players who want to roll back are pointed to Nvidia's driver archive and a clean installation.

Worth noting: that recommendation comes from S-Game's testing alone, and we found no independent verification of it. Tbreak's coverage adds that Nvidia's own guidance names 621.01 as the driver to install for this game, so the two sides currently disagree.

Why this matters at indie scale

Most indie teams don't have a path-tracing pipeline, but the pattern repeats at every size. A build can pass every internal check and still wobble on a driver version released days before launch, or on a GPU nobody on the team owns. Players don't separate "the game" from "the driver" when it stutters on their screen.

Three habits cover most of it. Test on the newest driver and one or two older ones before launch. Keep a short list of known-problem configurations you can publish on your store page. Plan the day-one patch as part of the schedule, not as an apology.

The reception suggests this did not sink the game: Notebookcheck reports a Metacritic score of 88 across PC and PS5. Being open about a known issue seems to cost less than leaving players to find it alone.


Want a second pair of eyes on your build across more hardware than you own? IndieBug can help you find the configuration that breaks before launch day does.