pcsx2/Docs/PCSX2_FAQ.md
PCSX2 intends to emulate the PlayStation 2 console, allowing PS2 games to be played on a computer. This requires having an original PlayStation 2 console to supply a BIOS dump and the original games, either to be played directly off the disc or to be dumped and played as ISO/CSO images.
PCSX2 is free and open-source, licensed under the GNU General Public License v3.0+. Source code is kept on GitHub.
There are a number of ways to help the project, whether it be bug reporting, game patching, or even writing code for the emulator itself. Some examples:
No. First, you must dump your PlayStation 2 console's BIOS using the BIOS dumper. Instructions for the BIOS dumper are available on the PCSX2 website.
After dumping your PlayStation 2 console's BIOS and copying it to your computer, launch PCSX2, step through the first-time setup wizard, and then you may begin playing.
<div class="page"/> <!-- Because PDFs are terrible -->| Operating System | CPU | GPU | RAM |
|---|---|---|---|
| - Windows 10 Version 1809 or newer (64-bit) |
Note: Recommended Single Thread Performance is based on moderately complex games. Games that pushed the PS2 hardware to its limits will struggle on CPUs at this level. Some release titles and 2D games which underutilized the PS2 hardware may run on CPUs rated as low as 1200. A quick reference for CPU intensive games: Wiki, Forum and CPU light games: Forum
| Operating System | CPU | GPU | RAM |
|---|---|---|---|
| - Windows 10 Version 22H2 (64-bit) or newer |
Note: Recommended GPU is based on 3x Internal, ~1080p resolution requirements. Higher resolutions will require stronger cards; 6x Internal, ~4K resolution will require a PassMark G3D Mark rating around 12000 (GeForce GTX 1070 Ti). Just like CPU requirements, this is also highly game dependent. A quick reference for GPU intensive games: Wiki
| Operating System | CPU | GPU | RAM |
|---|---|---|---|
| - Windows 10 Version 22H2 (64-bit) or newer |
By default, PCSX2 uses two cores for emulation. Enabling the MTVU speedhack allows the PS2's VU1 coprocessor to run on a third core, which is safe for most games and is generally enabled by default if possible on your CPU.
Software rendering can be set to use as many or as few rendering threads as desired. We recommend using no more than 8, or the number of cores (or SMT threads) that your CPU has, whichever is the lower number.
<div class="page"/> <!-- Because PDFs are terrible -->The CPU load as reported in software such as Windows' Task Manager is usually a summation of CPU usage, across all cores. Software can only use the resources of the individual CPU cores it is actually running on, and cannot "borrow" CPU time from other cores.
No. PCSX2 does not use or require multi-GPU.
The PCSX2 website has a compatibility list with every game that has been tested.
No, they will not work without issues. Please use a proper PS1 emulator, such as DuckStation or Mednafen.
PS1 games may work on PCSX2, but compatibility is very limited. Specific settings are often required to get a game to boot, and there are other universal problems including missing/pitch-shifted audio and severe FMV corruption. A forum thread for PS1 compatibility is tracking some fixes and compatibility reports.
While we encourage discussion about PS1 games and improving compatibility, bug reports are NOT being accepted for PS1 games. Any reports for PS1 games will be closed immediately as invalid.
Any change to the emulator may fix one game, but cause problems for another. If the issue is severe and not fixable with different settings, you can always revert back to the last known PCSX2 version to work, and report the build number that broke the game. Development builds are very helpful for finding the exact change that caused a regression.
The PlayStation 2 is a complex console, and this substantially raises the PC requirements to emulate it at full speed accurately. This forum thread helps explain some of the technical reasons behind it, and our current guidelines for PC requirements are listed above.
You have to dump the BIOS files from your PlayStation 2 console. There is a BIOS dumper tool available on the PCSX2 website to do this. If you need a guide, check the bottom of this FAQ for links to BIOS guides.
<div class="page"/> <!-- Because PDFs are terrible -->You can use games from your personal collection of discs, purchase them from local stores that resell old games, or look online at sites like eBay or Amazon.
Yes. However, some games have speed problems, because unlike the PS2 which would constantly keep the disc spinning, PCSX2 will not do the same to your PC's disc drive. It is recommended to instead dump your games to ISO images. You can find a guide for this on the PCSX2 website.
If you are using an ISO image:
If you wish to have your ISO image(s) populate in the game list:
If you are using a disc:
Fast Boot, enabled by default, will directly mount and launch the game without first launching the PS2 BIOS. You may disable this in Settings > BIOS > Fast Boot if you wish to see the BIOS startup animation or if Fast Boot is causing an issue.
See the build guide.
It will be released when it is ready. Please don't waste your time and ours asking when.
<div class="page"/> <!-- Because PDFs are terrible -->Refer to the Configuration_Guide.pdf (located in the same folder as this FAQ) for an initial setup guide and resolutions or workarounds to some common known issues.
The framelimiter has a few options that allow you to alter the pacing of your games. This will directly affect the game's speed itself, NOT your framerate, and can be useful for speeding through sections of games, or slowing down for precision.
These framerates are what the PlayStation 2 console would push to a real TV through its video cable. A game itself, typically, internally generates only half of those frames, and repeats frames to fill the gaps. This is why a "full speed" game may not "feel like 60 FPS". The console's "speed" (meaning AI, sound, physics, everything) is tied to the playback framerate, which is what PCSX2 reports as its "FPS".
Gamefixes are specialized fixes built into PCSX2 for specific games. Gamefixes mostly fix core emulation problems that would crash or soft lock a game, rather than graphical or performance issues. By default, these are automatically enabled, meaning any games that need gamefixes will have them automatically applied, regardless of what gamefix settings you have enabled.
Most games will not need gamefixes, however if your game is having issues, you can try manually enabling them in Settings > Game Properties > Game Fixes.
Gamefixes are not FPS boosters; more often than not, they will degrade performance slightly.
<div class="page"/> <!-- Because PDFs are terrible -->The PS2 EE, IOP and VU processors are substantially different from a PC CPU and require different rounding and clamping modes to do math accurately. Most games work fine on the default options, but some games might need a different setting. You can check the PCSX2 Wiki to see if your game needs an alternate setting, or check the PCSX2 Forums to see if anyone else has posted about it there.
Older versions of PCSX2 used a plugin framework for various sections of the emulator. A plugin is a small, incomplete piece of software that, when plugged in to another piece of software, provides some sort of additional function. PCSX2 used to use plugins for:
In newer versions, these have been merged into the main emulator, and there is no longer a way to load external plugins.
Your device may simply be too slow to play the game. If you have changed settings, attempt to revert them to the default, as these are usually the fastest.
For Windows users, PCSX2 will ship with XInput bindings already created. This will automatically work with an Xbox One controller or any other XInput controller. Bindings can easily be made for DirectInput and XInput controllers, such as Xbox 360 controllers. PS3, PS4, or Switch Pro controllers should be set up using third party compatibility software, such as Steam's Big Picture mode.
For Linux and macOS users, PCSX2 will automatically detect and bind controls to any recognizable controller via SDL.
<div class="page"/> <!-- Because PDFs are terrible -->