|Original developer(s)||DH, Hykem|
|Current developer(s)||RPCS3 Team|
|Latest version||0.0.15 Alpha[N 1]|
|Platform(s)||Windows, Linux, BSD|
|Emulates||PlayStation 3, PlayStation Classics (PSN versions)|
RPCS3 is a very promising open-source, multi-platform PlayStation 3 (PS3) emulator/debugger written in C++. RPCS3 can run over 1,800 commercial titles without major glitches (see the compatibility list). It also emulates the PSN versions of the PlayStation Classics. The emulator is making huge progress, improving every month. (See the progress reports)
- 1 Download
- 2 Overview
- 3 Special features
- 4 Setting up
- 5 Basic troubleshooting
- 6 Notes
- 7 References
- 8 External links
Official Firmware and Fonts needed
RPCS3 was started by programmers 'DH' and 'Hykem' (Who began beta-testing and coding for JPCSP in 2008) in May 23, 2011. The developers initially hosted the project on Google Code and eventually moved it to GitHub later in its development. The emulator was first able to successfully boot and run simple homebrew projects and was then later publicly released in June of 2012. Then-Orbital founder, Alex Altea, even joined these two developers in the late summer of 2013, and worked on a number of aspects and maintained the project up till early 2015. DH left the project in mid 2016 and started doing PlayStation 4 related research. Hykem was forced to leave the emulation scene in mid 2016 for a number of legitimate reasons.
Three years into its development, it could load the intros to some games with sound, as well as play some portions of Disgaea 3 and The Guided Fate Paradox, but with heavy graphical glitches and no sprites. Today RPCS3 is dubbed one of the most complex video game console emulators of all time with an endless goal to effectively emulate the Sony PlayStation 3 and all of its aspects. The goal of this project is for its programmers to experiment, research, and educate on the topic of PlayStation 3 emulation that can be performed on compatible devices and operating systems.
Developer Nekotekina opened a Patreon campaign in 2017, with kd-11 joining not long after.
As of April 2020, RPCS3 has been able to play over 50% of the PS3 library from start to finish. The emulator is capable of running over 1,000 games at a playable speed with no major glitches, though it requires very demanding hardware on most games. On June 2018 after a few improvements and fixes, at least most PlayStation 1 Classic titles became playable. Currently, only the PSN versions work (No PS1 discs are able to be loaded in-game yet).
Since the emulator started getting funded on Patreon, development has been progressing quickly, so more games are expected to be playable in the near future.
- Source code for original RPCS3 code from 2011-2013.
- Asynchronous Shader Recompilation
- Makes games run virtually stutter free at the cost of some new shaders/textures popping into existence. Note: It only gives a tiny performance boost - a powerful computer and further optimizations from the emulator will be needed to get the more demanding titles to run at full frame rate speeds, i.e. 30 FPS or 60 FPS. Many demanding games may utilize multiple secondary cores plus the primary core of the PS3's CPU so parallelization techniques will be needed, perhaps running on a user's GPU or 8-core and better CPU. This recompilation mode only simulates the shaders coming through the RSX graphics processor.
- Third-party suite. Makes many games appear more vibrant or saturated, particularly more pronounced in those with dull textures like the Tales of series, Naruto series, and other anime-based titles.
Installing the firmware
RPCS3 does not work without firmware. This firmware contains libraries used to interface with the games in different ways, like Bluetooth, PlayStation Eye, and so on. For a long time, it was commonly thought that these libraries could only be extracted from a modded PS3, which would have greatly increased the barrier to entry, however one of the developers discovered all the libraries were actually bundled with each system update, and that Sony also supplies these updates through their website. This is the preferred method of installing the firmware; download the latest update from Sony, then in RPCS3 go to File -> Install Firmware, and select the downloaded update file.
Installing games and updates
The game's serial should be present in the folder or archive name, the download page, and/or the PARAM.SFO file. If it's a retail game, it has the ID on the bottom side edge of the game's case. An internet search for
InsertGameNameHere + Region ID should turn it out. It's also important that each game's files and folders are all placed under a single folder named as the correct region ID.
For Blu-ray Disc games, i.e. retail games:
- File layout: PS3_GAME folder, PS3_DISC.sfb, PS3_UPDATE folder (not required)
- Game ID starts with a
B. First-party Sony games use
BC, while third-party games use
BL. For example:
BCAS20071(Demon's Souls Asia retail),
BLUS31197(Drakengard 3 USA retail).
- May be dumped through a CFW-enabled PS3, using select compatible Blu-ray drives on PC, or acquired from someone else.
- Game folders for retail games can be put under the
\dev_hdd0\discor anywhere really... except the folder used for digital games (
\dev_hdd0\game) because some games write there causing really bad conflicts. To open games, use File/Boot Game.
For PSN games, i.e. digital versions downloaded from the PlayStation Store:
- File layout: TROPDIR folder, USRDIR folder, ICON0.png, PARAM.sfo, etc.
- Game ID starts with a
N, for example
NPEB02436(Persona 5 EUR digital)
- May be dumped through a CFW-enabled PS3, Sony's own poorely secured servers (PSNdl then psnpkgdecryptor-extractor), or acquired from someone else.
- May come as a PKG file. RPCS3 has an Install .PKG option to install these.
- Game folders for digital games must be placed under
\dev_hdd0\game, as intended by design on real hardware. Using the Install .pkg option does that automatically for you.
Paid digital releases require a .RAP license file to decrypt a few important files before they can be booted.
- Maybe dumped from the
\dev_hdd0\home\00000001\exdatadirectory of a CFW-enabled PS3, or included alongside the download you got from someone else. That someone else might not include the .RAP file, and instead give a "fix" with the pre-decrypted files. In that case, you might have to install the PKG file first (or all of them, if there are multiple ones) and then copy and overwrite the "fix" files to your game folder.
- If your source doesn't include a RAP or crack instructions, either it's replaced beforehand or it's actually useless. The last resort can be to try searching for a fix for the specific release.
- Must be placed under
Game and software updates are handled exactly like PSN games.
- Installed using the Install .PKG option
- The update will be placed in the game or software folder that corresponds to the correct region ID.
- Take care to use the same region for the base game and the update, otherwise there's a potential risk of irreversible damage to your installed game dumps.
Files under the
.66600x extensions are split files that accommodate for the 4-gigabyte file size limit on volumes formatted as FAT32; the PS3 does not support other types of filesystems that pass this limit, such as NTFS or the ext family. Use a tool like PS3merge to recombine these files.
Note that RPCS3's official Discord server can also be a good resource for bringing up issues or learning about major breakthroughs or updates if any further information is required.
RPCS3 is compiled to 7z files using Azure. To update RPCS3, download the latest build, and replace the necessary files.
For most minor updates, you only need to extract and replace the
RPCS3.exe executable for them to take effect, but it's recommended that you backup old builds so that you can revert to the older ones if new problems crop up, or you can extract the whole 7z archive file and replace files to their respective folders.
RPCS3 is compiled to AppImages using Azure. To update RPCS3, download the latest build, and replace your previous AppImage with the new one. Reenable executable permissions if they were disabled during the update. Most file managers can let you change it from their properties window.
Issues are to be expected since the emulator is still early (even though the project was started in 2011).
Cannot be completely eliminated in most cases, but you can at least try to mitigate it by playing around with the "Preferred SPU Thread" setting as well as the "lower SPU thread priority" and "Bind SPU thread" to secondary core settings.
In addition, manually adjusting the priority and affinity of the RPCS3 process can affect it independently of the other internal settings. On Windows, this is done via the Task Manager. On Linux, CLI and GUI tools exist like System Monitor and Task Manager that can change the priority. It varies by distribution. This can influence audio stutter and performance in general but especially for Ryzen users.
If you can't find a specific setting in RPCS3, you could be using an old build, and should probably update it.
Locked PSN demos
Some PSN titles use an .EDAT file to differentiate between "trial" and "full version" states rather than a .RAP file; these games are often referred to as "c00" games, stemming from the c00 folder in their installation which contains parameters for the full version. This can cause issues with unlocking certain titles, with a notorious example being Castlevania: Harmony of Despair. If a title utilizing an .EDAT file will not unlock its full version, renaming the .EDAT to .RAP will usually unlock as intended.
- The developers are currently treating version increments as milestones, not as stable builds.
- [IMPORTANT Hykem says goodbye] (August 18, 2016)
- Rpcs3 Update Quality Sound - Intro Video - The Guided Fate Paradox (Mar 26, 2014)
- RPCS3 WIP - Disgaea 3 - Ingame! (Mar 22, 2014)
- RPCS3: About Us page