PCSX2 is an open source, plugin-based PlayStation 2 emulator. Its purpose is to mimic the PS2 hardware using a combination MIPS CPU interpreters, recompilers and a virtual machine which manages hardware states and PS2 system memory.
- F1: Save state
- F2: Change slots
- F3: Load state
- F4: Turn On/Off Framelimiter
- F5: Switch deinterlacing modes
- F6: Switch Aspect Ratios
- F7: Switch TV Shaders
- F8: Take screenshot
- F9: Switch between Hardware and Software mode
- F10: Enable/disable logging
- F12: Video Recording
- Tab: Turbo Mode
- Shift+Tab: Slow Mode
- Esc: Pause emulation and return to GUI
- Insert(Software mode): Turn/Off mipmapping
- Delete(Software mode): Turn On/Off Edge Anti-Aliasing
- Home: Turn/Off external FX Shader
- Page Up: Turn/Off FXAA
- Windows Vista / Windows 7 32-bit/64-bit or later
- CPU: Intel Core 2 Duo @ 3.2 GHz or better
- GPU: 8600 GT or better
- 1GB RAM (2GB if on Vista / Windows 7)
For those with DualShock 3 controllers, use the new SCP Driver Package.
GamepadEditNative DS3 controls with Lilypad-SCP - Import this with the 'Load Bindings' button in Lilypad's config.
Either that, or you can use the Pokopom XInput Plugin. If you use a DualShock controller running under an XInput wrapper such as SCP Server, then this plugin is a no-brainer. It's very customizable, and you don't have to configure it beforehand. All of the buttons are bound at startup.
Now, most of the video options are very straight-forward. However, there is one that probably bears explaining: The interlacing modes. Now, many games can run fine without interlacing modes. You can just select "None" and everything will be fine. However, some games will have a "jitter" effect if you don't have interlacing modes enabled. The "Sawtooth" interlacing method is not recommended at all. Artifacting is far too heavy to be usable. The "Bob" interlacing method has the least artifacts out of all of them, but it can still let some jittering pass through. The "Blend" interlacing method has the least amount of jitter. However, that comes with a pretty hefty side-effect: blurriness. Yes, the Blend interlacer does frame-blending. This is also known, more colloquially, as motion blur. This means that if there is heavy jitter, the video output will be extremely blurry since the two jittering frames will blend together. Only use this interlacing method as a last resort.
It's either interlacing or a filter in the game itself. For the former, switching the de-interlacing mode with F5 may help, and may cause flicker or screen shaking. For the latter, hacks are required. Either Aggressive-CRC if the game is listed there, or skipdraw (toy with the number, 1-100) might work otherwise.
Black lines Edit
Those lines are caused by scaling to a non-integer internal resolution (anything other than XxNative), texture filtering (if it cause issues try to set it to half at most or check it off), improperly offset textures(TC offset hack, Wild Arms hack), or improperly handled texture edges(Sprite hack). Native resolution for the most part fixes those. But software rendering may be required for particularly buggy games.