RPCS3 Just Found 37% More Performance. If You Play on a Handheld, You Get None of It.

Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.

2026-09-19 · News and analysis

Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.

Ninety lines of code went into RPCS3 last week. Gran Turismo 5 went from 107 fps to 147 fps, and its VRAM use dropped by 2.3GB at the same time.

Now the part the headlines are skipping. If you play PS3 games on a Steam Deck, a ROG Ally, a Legion Go, or an MSI Claw, you get none of this. Not a smaller version of it. None.

That is not a disappointment, it is the whole story. Here is what actually happened.

What the Patch Does

The PS3's graphics chip, the RSX, does something modern GPUs find awkward. It reuses the same block of memory with different formats and different sizes from one frame to the next. RPCS3 handles this with an operation called surface splitting.

Until last week, RPCS3 would throw away the old render target every time it split a surface, then ask the driver for a fresh one. Allocate, discard, allocate, discard, thousands of times a second.

AMD's driver shrugged at that. NVIDIA's driver charged a toll for it every single time.

The patch simply recycles the discarded targets instead of handing them back. That is it. The title in the commit log is "RSX: Reuse discarded render targets during surface splitting," and it is 90 lines added across three files.

The Numbers

These are the figures the RPCS3 team published. We have not run any of these tests ourselves.

Game and scene	Hardware	Result
Gran Turismo 5	RTX 5070 + Ryzen 7 9850X3D	107 fps to 147 fps, up 37%
Red Dead Redemption boat scene	RTX 5090 + Ryzen 7 9800X3D	Up about 25%
Red Dead Redemption boat scene	RTX 3080 + Core i9-13900K	Up about 20%
Saints Row IV	GTX 1060 + Core i7-7700HQ	Up about 20%
Saints Row: The Third	GTX 1060 + Core i7-7700HQ	Up about 10%
Any of the above	Any Radeon GPU	No change

The Saints Row row is the one worth pausing on. That is a 2017 laptop with a GTX 1060 in it, and it gained roughly as much as an RTX 5090 did. This was never a bug that only hurt new cards.

The VRAM Drop Is the Underrated Half

Gran Turismo 5 went from using 7.1GB of video memory to 4.8GB. Same game, same settings, 2.3GB freed.

If you own an RTX 3070, a 4060, or any other 8GB card, that number matters more to you than the frame rate does. Running out of VRAM is not a gentle slowdown. It is stutter, texture pop-in, and hitching that no amount of CPU headroom fixes.

It makes sense once you know what the patch does. All those discarded render targets were not vanishing instantly. Recycling them means RPCS3 stops accumulating memory it was never going to use again.

Why Your Handheld Gets Nothing

Because there is no handheld with an NVIDIA GPU in it.

Go down the list. The Steam Deck and Steam Deck OLED are AMD. The ROG Ally and Ally X are AMD. The Legion Go and Go S are AMD. The OneXPlayer 3 is AMD. The AYANEO NEXT 2 ships with either discrete Intel Arc or Radeon 6000 graphics. The MSI Claw line is Intel. Everything from Anbernic, Retroid, AYN and MagicX is ARM, and does not run RPCS3 in the first place.

AMD's driver never had this bug. So on the handhelds that can run RPCS3 at all, the emulator was already doing the efficient thing, and there was nothing to win back.

We want to be careful with how we say this next bit. No handheld you can buy today has an NVIDIA GPU. That is a statement about today. NVIDIA has ARM based N1 and N1X chips in development with MediaTek that pair ARM cores with RTX graphics, and we are no longer willing to tell you that a handheld will never have a GeForce GPU in it. It just does not have one now.

Where Handheld Owners Do Get It

One route, and it is a real one. If you already run RPCS3 on a desktop with a GeForce card and stream it to your handheld, you get the full benefit, because the rendering happens on the desktop.

A 20% uplift on the host machine is 20% more headroom for the encoder, and encoding overhead is the thing that usually decides whether streamed PS3 emulation feels right. Our cloud and local streaming guide covers the setup.

That is genuinely the only way this patch reaches a handheld screen.

Two Things the Coverage Got Wrong

It is not Vulkan only. Several write ups framed this as a Vulkan fix. The patch touches three files, and two of them are render target headers: one for Vulkan and one for OpenGL. So our standing advice in the RPCS3 setup guide to use the Vulkan renderer is unchanged, and OpenGL users are not left out.

It is in no released build. RPCS3 is rolling release and does not do stable versions. The most recent tag, v0.0.42, is from 31 July 2026, which is six weeks before this patch existed. Downloading "the latest release" from a tag list will not get you this.

Get a current master build from the official download page instead. There is no setting to enable. The fix is always on.

The NVIDIA Subplot

Worth a short mention. The RPCS3 team said they had raised this and other driver issues through NVIDIA's developer forums without much luck, and that they would like a more direct line of communication.

That is the whole of it. A volunteer emulator project found a bottleneck in a commercial driver, could not get anyone's attention, and eventually coded around it. We are not going to read more into it than the team said.

Check Steam Deck OLED Price on Amazon

The Bottom Line

A 90 line patch stopped RPCS3 from churning render targets, which stopped NVIDIA's driver from charging for the churn. Gains run from 10% on an old GTX 1060 to 37% in Gran Turismo 5, plus a 2.3GB VRAM saving that probably helps 8GB card owners more than the frame rate does.

AMD never had the bug, every handheld that runs RPCS3 is AMD or Intel, and so every handheld gets nothing. Grab a master build if you have a GeForce card in a desktop. Otherwise this one is somebody else's good news.

Frequently Asked Questions

Will this speed up RPCS3 on my Steam Deck?

No. The bug was in NVIDIA's driver and the Steam Deck uses an AMD GPU, which never had the problem. Your Deck was already getting the efficient behaviour, so there is nothing for the patch to recover. The same applies to the ROG Ally, Legion Go, and OneXPlayer.

How much faster is RPCS3 on NVIDIA now?

Between roughly 10% and 37%, depending on the game and the scene. The published figures are 37% in Gran Turismo 5 on an RTX 5070, around 25% on an RTX 5090 and 20% on an RTX 3080 in a Red Dead Redemption scene, and 10% to 20% in the Saints Row games on a GTX 1060 laptop.

Do I need to change a setting to get the improvement?

No. There is no toggle. The fix is part of the emulator's render target handling and applies automatically. You only need a build made after 16 September 2026.

Is the fix in the latest RPCS3 release?

Not in any tagged release. RPCS3 is rolling release software, and the most recent tag, v0.0.42, dates from 31 July 2026. You need a current master build from the official download page.

Does this only work with the Vulkan renderer?

No. The patch modifies the shared surface store plus both the Vulkan and the OpenGL render target headers, so both backends benefit. Vulkan is still the renderer we recommend for other reasons.

Does the patch help Intel Arc GPUs?

Nobody has published a test, so we do not know. The bug was specific to NVIDIA's driver behaviour and AMD was confirmed unaffected, but Intel was not mentioned by the developers or in any coverage we could find.

Why does the patch reduce VRAM use?

Because RPCS3 was discarding render targets and allocating replacements instead of reusing what it already had. Recycling them means the emulator stops holding on to memory it will never touch again. In Gran Turismo 5 that cut usage from 7.1GB to 4.8GB.

Can I benefit from this if I play on a handheld?

Only by streaming. If RPCS3 runs on a desktop with a GeForce card and you stream to your handheld, the host machine gets the full gain. There is no way to get it on the handheld's own GPU.

Written 19 September 2026. The pull request number, author, merge time and line count come from the RPCS3 GitHub repository, retrieved 19 September 2026. Performance figures are the developers' own, published by the RPCS3 project and by Hardware Busters. We ran no benchmarks for this article and tested no hardware, and we make no claim about Intel Arc because nobody has published one.