Phantom Blade Zero Stuttering, Low FPS, and PS5 Freezes: The Launch Troubleshooting Order

Start with the five official setup rules

S-GAME published a short FAQ on launch day, and its order doubles as the first troubleshooting pass. Work through it before you touch anything else:

1. The first launch compiles shaders. Loading takes noticeably longer the first time. Let it finish instead of force-closing during those first minutes.
2. Use the in-game recommended preset. It is the studio's own balance point, and it gets you to a playable baseline faster than walking down from the highest settings one by one.
3. On PC with a controller, use a cable. The official advice does not promise wireless behaviour; plugging in is the first way to rule out "my inputs do nothing".
4. Install the game on an SSD. Mechanical drives are outside the supported configuration, and slow loads, mushy textures and stutter can all come from that.
5. On NVIDIA, prefer driver 617.42. That is the version the official FAQ calls the current best fit. More on why below.

If everything above is done and something still breaks, that is the point to contact the official customer support on the game's website — not before, because most launch-day problems live inside these five items.

The day-one patch: what the studio said, what players still report

S-GAME posted its day-one patch notes as a Steam news item in the early hours of October 30 (Beijing time). The notes cover improvements to ray tracing along with a batch of bug fixes. No full changelist was published, and the wording leaves room on whether the patch had actually finished going out.

Over the same stretch, players kept reporting long loads, crashes on launch and slow shader compilation; the October 30 Reddit threads include titles like "Stuck" and "Controller Issue".

So the practical position is this: the patch is out, individual cases remain. The troubleshooting order does not change — work through the five rules above first, then the FPS and driver sections below.

Low FPS: change things in this order

The order matters more than the individual toggles:

1. Confirm the day-one patch is installed. PC gets roughly 5 GB; PS5 has a separate ~2 GB download, version 1.301.524. The patch contains ray tracing, path tracing and rasterisation changes, so FPS measured before it and after it are not comparable. Details are in our day-one patch breakdown.
2. Return to the recommended preset and measure again. Get the studio's baseline before deciding what to cut.
3. Turn on upscaling. The official system requirements say it plainly: 1080p/30 and 1440p/60 are targets with upscaling enabled. Complaining about FPS with upscaling off is measuring a configuration the requirements never promised.
4. Switch off path tracing. It is the most expensive graphics option in the build, and per the official material it is not the same thing as ordinary ray tracing — it solves a wider set of light behaviour. If the goal is stable frames, this is the first thing to go. For the technical difference, see the PC launch tech notes.
5. Then look at frame generation. DLSS 4.5's dynamic multi-frame generation is driven by RTX 50-series cards and their fifth-generation Tensor Cores. Those are additional frames, not a free upgrade; make sure the first four steps are done before enabling it.

If your GPU is below the minimum, this section cannot rescue you. The official minimum is a GTX 1660 6GB or RX 5500 XT 8GB, with an RTX 3060 Ti or RX 6700 XT recommended. The full requirements and the four graphics tiers are on the system requirements page.

One note on Intel Arc. The A750 does not appear in the official GPU lists — minimum and recommended both name only NVIDIA and AMD parts. The report we received was an A750 with a Ryzen 5 5600 and 32 GB of RAM running at clearly low frames. What is available for that configuration: update to Intel's latest game-ready driver, enable the upscaler the game exposes, turn path tracing off and drop the overall preset a tier, and confirm the install is on an SSD. If it still misses, send the spec and a capture to official support.

Which NVIDIA driver: 617.42 or 621.01

This is the launch window's real dilemma, because both statements are true:

• 621.01 is the Game Ready driver NVIDIA published on October 20. Phantom Blade Zero is the first game named in that announcement, which states the game ships with the "full suite of DLSS 4.5 technologies".
• 617.42 is the version S-GAME's own FAQ calls the current best fit, for a blunt reason: 621.01 costs performance on some machines, and multiple launch-week reports describe the studio recommending a rollback.

So the trade-off is: stay on 617.42 for stability, move to 621.01 only if you want the newer DLSS features, and roll back if frames drop. When you roll back, do a clean install (uninstall, then install 617.42) rather than installing over the top; leftovers from the previous package are a common source of weird results. If you have tried both and performance is equally bad, the driver is not your problem — go back to the graphics order above.

PS5 freezes and unresponsive buttons: what we know

Be clear about the evidence: we could find exactly one public report. A player wrote in on launch day describing a few minutes of play followed by the character becoming uncontrollable, every button except Share and the PS5 system menu going dead, an on-screen prompt with no matching button to press, and the same state returning after restarting the game. They included a screenshot. The official FAQ does not list this issue, and we could not find a second public report in the community.

Until more cases appear, treat it as an individual report plus general troubleshooting, not a widespread bug. Try, in order:

1. Check the version. The PS5 day-one patch is 1.301.524; update if you are behind.
2. Reload the last checkpoint. If the freeze follows a specific prompt or cutscene, loading the nearest checkpoint often steps around it.
3. Fully close and relaunch. Not back to the main menu — close the application and start it again.
4. Rebuild the database from Safe Mode as a last resort. It is a built-in PS5 maintenance function, and it is a system-level operation, so make sure nothing is mid-download first.

If the freeze still reproduces, send three things to official support: a capture, the last action before it happened, and the save timestamp. Those three turn a vague report into something reproducible.

If none of that works: where to report

The official FAQ points to customer support on the game's website (pbz.s-game.com), not the Steam comments section and not social media DMs. Include platform, version number, hardware, the exact steps that trigger the problem, and a capture — that set is what makes a report actionable.

One boundary worth stating: this site is a fan guide. We do not run official support and we do not forward cases on your behalf (see our contact page). What we can do is keep the troubleshooting order and the known issues in one place, so you are not guessing in circles.

FAQ

• Phantom Blade Zero is stuttering — what do I change first? Install the day-one patch, switch the graphics preset to the game's recommended setting, and confirm the game is on an SSD. The official system requirements list both 1080p/30 and 1440p/60 as targets with upscaling enabled, so turning on upscaling and switching off path tracing is usually faster than hand-tuning individual settings.
• Should I use NVIDIA driver 617.42 or 621.01? The official FAQ names 617.42 as the current best-fit driver. 621.01 is the Game Ready driver NVIDIA released for the game with the full DLSS 4.5 suite, but S-GAME's own guidance and multiple launch-week reports point to 621.01 costing performance on some machines. Stay on 617.42 for stability; try 621.01 only if you want the newer DLSS features, and roll back if it drops.
• My PS5 froze and no button works — what do I do? We could only verify one public report: after a few minutes of play the character stops responding, every button except Share and the PS5 system menu goes dead, the on-screen prompt has no matching button, and restarting the game does not help. Try updating to 1.301.524, reloading the last checkpoint, fully closing the game, and as a last resort rebuilding the database from Safe Mode.
• The first load is very long — is that normal? Yes. The official FAQ says the game compiles shaders the first time you launch it, and that takes noticeably longer than later loads. Let it finish; forcing it closed usually means starting over.
• How big is the day-one patch? About 5 GB on PC. PS5 has a separate download of roughly 2 GB, version 1.301.524. The patch carries ray tracing, path tracing and rasterisation changes, so measure performance after installing it rather than before.