4d66818746
* recording: Only stop the current recording once the menuing hasnt been cancelled * recording: Avoid changing menu option's state if the recording couldn't be played * recording: Don't play a recording that uses a savestate, if no game is running * recording: Don't modify `frameAdvance` flag when explicitly [un]pausing These functions are only called when creating/playing a recording, and modifying the frameAdvance flag leads to unexpected behaviour (such as the game starting paused if the recording was made from "power-on") * recording: Refactor and simplify `InputRecordingFile` InputRecordingFile will no longer be concerned with loading the save-state when playing back an existing recording. This makes it much easier to only load the save-state if the file is valid and manipulate the emulation state correctly. * recording: Update play logic with new refactor, resume emulation in the event of a failure * recording/lint: spaces to tabs * recording: Properly only examine controller 1A & 2A The previous controller port checks in place never actually succeeded in their designated task. A new slot check in sio.cpp will perform this task instead. * recording: Save the savestate in OpenNew() instead of open() Ensures that the savesate could be saved before trying to create the actual input recording file. It will overwrite any previous backup savestate. Also, allows for a simplified & easier to read code struture of open(). * Refactor and simplify `InputRecording` Changes the return type of Play/Create from void to bool. Optimizes Stop(), Pause(), and Unpause() call placements Improved handling of emulation pause state, the recording menu on failures, and the conditioning of when a recording file should actually be unloaded. For example, a currently loaded recording should not get unloaded if a user presses Play *but* chooses cancel in the file browser. However, the emulation should be paused during the duration of this action. On the flipside, a loaded recording *should* get unloaded if the tools get disabled in settings AND emulation should resume if not already playing. * recording: Simplify VirtualPad_Open_Click Co-authored-by: Tyler Wilding <xtvaser@gmail.com> |
||
|---|---|---|
| 3rdparty | ||
| bin | ||
| cmake | ||
| common | ||
| debian-packager | ||
| linux_various | ||
| locales | ||
| nsis | ||
| pcsx2 | ||
| plugins | ||
| tests | ||
| tools | ||
| .clang-format | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| COPYING.GPLv2 | ||
| COPYING.GPLv3 | ||
| COPYING.LGPLv2.1 | ||
| COPYING.LGPLv3 | ||
| ISSUE_TEMPLATE.md | ||
| PCSX2_suite.sln | ||
| README.md | ||
| appveyor.yml | ||
| build.sh | ||
| buildbot.xml | ||
| mscompile.cmd | ||
| old_plugins.sln | ||
| travis.sh | ||
README.md
PCSX2
PCSX2 is a free and open-source PlayStation 2 (PS2) emulator. Its purpose is to emulate the PS2's hardware, using a combination of MIPS CPU Interpreters, Recompilers and a Virtual Machine which manages hardware states and PS2 system memory. This allows you to play PS2 games on your PC, with many additional features and benefits.
Project Details
The PCSX2 project has been running for more than ten years. Past versions could only run a few public domain game demos, but newer versions can run most games at full speed, including popular titles such as Final Fantasy X and Devil May Cry 3. Visit the PCSX2 compatibility list to check the latest compatibility status of games (with more than 2500 titles tested), or ask for help in the official forums.
The latest officially released stable version is version 1.6.0.
Installers and binaries for both Windows and Linux are available from our website.
Development builds are also available from our website.
System Requirements
Minimum
| Operating System | CPU | GPU | RAM |
|---|---|---|---|
| - Windows 8.1 or newer (32 or 64 bit) - Ubuntu 18.04/Debian or newer, Arch Linux, or other distro (32 or 64 bit) |
- Supports SSE2 - PassMark Single Thread Performance rating near or greater than 1600 - Two physical cores, with hyperthreading |
- Direct3D10 support - OpenGL 3.x support - PassMark G3D Mark rating around 3000 (GeForce GTX 750) - 2 GB Video Memory |
4 GB |
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
Recommended
| Operating System | CPU | GPU | RAM |
|---|---|---|---|
| - Windows 10 (64 bit) - Ubuntu 19.04/Debian or newer, Arch Linux, or other distro (64 bit) |
- Supports AVX2 - PassMark Single Thread Performance rating near or greater than 2100 - Four physical cores, with or without hyperthreading |
- Direct3D11 support - OpenGL 4.5 support - PassMark G3D Mark rating around 6000 (GeForce GTX 1050 Ti) - 4 GB Video Memory |
8 GB |
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
Technical Notes
- You need the Visual C++ 2019 x86 Redistributables to run PCSX2.
- Windows XP and Direct3D9 support was dropped after stable release 1.4.0.
- Windows 7 and Windows 8 support was dropped after stable release 1.6.0.
- Make sure to update your operating system and drivers to ensure you have the best experience possible. Having a newer GPU is also recommended so you have the latest supported drivers.
- Because of copyright issues, and the complexity of trying to work around it, you need a BIOS dump extracted from a legitimately-owned PS2 console to use the emulator. For more information about the BIOS and how to get it from your console, visit this page.
- PCSX2 uses two CPU cores for emulation by default. A third core can be used via the MTVU speed hack, which is compatible with most games. This can be a significant speedup on CPUs with 3+ cores, but it may be a slowdown on GS-limited games (or on CPUs with fewer than 2 cores). Software renderers will then additionally use however many rendering threads it is set to and will need higher core counts to run efficiently.
- Requirements benchmarks are based on a statistic from the Passmark CPU bench marking software. When we say "STR", we are referring to Passmark's "Single Thread Rating" statistic. You can look up your CPU on Passmark's website for CPUs to see how it compares to PCSX2's requirements.
Screenshots
Want more? Check out the PCSX2 website.