Changes

{{Infoboxemulator|image logo = PCSX2-Logo.png|imagewidth logowidth = 265|first version = 1.4.0|second active = Yes|third platform = Windows, Linux, OS XmacOS|fourth target = [[PlayStation 2 emulators|PlayStation 2]]|developer = [http://pcsx2.net/meet-the-team.html PCSX2 Team]|fifth website = [http://pcsx2.net/ PCSX2.net]|sixth source = [https://github.com/PCSX2/pcsx2 GitHub]|license = GNU GPL v2}} [['''PCSX2]] ''' is an open-source, plugin-based [[PlayStation 2 emulators|PlayStation 2 emulator]]. Its purpose is to mimic the PS2 hardware using a combination of MIPS CPU [https[wikipedia://en.wikipedia.org/wiki/Interpreter_%28computing%29 |interpreters]], [https[wikipedia://en.wikipedia.org/wiki/Dynamic_recompilation |recompilers]] and a [https[wikipedia://en.wikipedia.org/wiki/Virtual_machine |virtual machine]] which manages hardware states and PS2 system memory. RecentlyIn 2016, preliminary work was started on [[PlayStation emulators|PS1]] support.<ref>https://github.com/PCSX2/pcsx2/pull/1571</ref>

* [http://pcsx2mac.net/ Mac macOS version]

These are recommended specs for using PCSX2.,<ref>http://pcsx2.net/support/links/faq.html#S2Q1</ref> But but depending on the game you want to play, your mileage may vary. Some games need [http://forums.pcsx2.net/Thread-LIST-The-Most-CPU-Intensive-Games high-end, possibly overclocked CPUs] or [http://forums.pcsx2.net/Thread-LIST-The-Most-GPU-Intensive-Games powerful GPUs], whereas some games run even on [http://forums.pcsx2.net/Thread-LIST-Games-that-don-t-need-a-strong-CPU-to-emulate weak processors].

For those with [[DualShock 3 ]] controllers, use the new [[SCP Driver Package]].

Either that, or you can use [http://forums.pcsx2.net/Thread-Pokopom-KrossX-s-Pad-Plugin the Pokopom XInput Plugin.] If you use a DualShock controller running under an a 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 Most of the video options are very straight-forward. Howevershould be straightforward, there is one that probably bears explaining: The with the possible exception of interlacing modes. Now, many Many games can will run fine without interlacing modes. You can just select "with 'None" and everything will be fine. However, some games, such as Gran Turismo 3 and Dark Cloud', will have a "while others may experience artifacting or 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 reduced artifacts out of all of them, but it jitter can still let some jittering pass throughoccur. The * "Blend" interlacing method has the least amount of jitter. However, that comes with a pretty hefty side-effect: it can cause blurriness. Yes, the 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.

Whenever you encounter any kind of bug that isn't graphical in nature, objects going through other objects, untargetable objects that should be targetable or A.I. freezing , for example, make sure that the automatic game fixes option from the system menu is activated.

Whenever a game has graphical problems such as garbage texture, missing effects, light sources visible through a wall, burn -in or transparent objects being opaque, the easiest fix is generally to switch to software mode either by pressing F9 in-game or via the configuration panel of the GSdx plugin.If using the DX11 renderer another option is to try the OGL one which is generally more up to date and more accurate.If you're using version 1.4.0 of the emulator or earlier, try using the most recent development build of the emulator. Newer development builds of the emulator have fixes in the hardware rendering which may remove graphical errors such as red or green bars appearing on the screen. The newest development build can be found at https://pcsx2.net/download/development/dev-windows.html, click the download link of the revision closest to the top of the page.

Many games will require you to switch to software mode to fix various issues, albeit at the cost of a significant performance loss. However, an easily overlooked setting in the graphical plugin configuration panel, extra rendering threads, might help lessen the performance loss if you have a quad-core or higher CPU. It is recommended to set it to the number of cores in your CPU minus one if you aren't using the the MTVU speed-hack, or minus two if you are (ex: if you are using a quad core CPU you should set this number to 3 without MTVU and 2 with MTVU).

Multi-threaded microVU (MTVU), while generally a very useful speed-hack, might sometime cause minor problem problems like hanging and absence of performance gain or more severe ones like massive performance hits, save-states corruption (PCSX2 keeps a backup you can load with Shift+F3 in case any issues arise) and crashes to desktop.

Switching between hardware and software rendering rapidly is likely to cause the emulator to lock up. This can be easily avoided by waiting a few seconds after switching between hardware and software rendering before switching again.If the log warns you one or several time times about being out of memory or the emulator crashes without warning several times in a row after playing for around the same amount of time you will need to apply a patch to make the executable large address aware, its more commonly referred to as the [http://www.ntcore.com/files/4gb_patch.zip 4GB patch].

* Using a bad dump of a game, in which case you'll need to [[Ripping Games|re-rip your disc]] or [[Need_Games%3F|re-download the game]] you are trying to play.

Large The large fluctuation in emulation generally are caused by the games themselves and cannot be avoided but there is a handful of cases where this is caused by specific configuration issues

Due to how the synchronizing function of the audio plugin works, even when running games on a computer that is capable of going way above 100% speed in a stable fashion, random bits of timestretched time-stretched audio can be heard occasionally or even frequently, there are however a few ways to work around that issue..

Black lines are caused by scaling to a non-integer internal resolution (anything other than Yx Native), texture filtering (Try anything that isn't bilinear (Forced), improperly offset textures (TC Offset, Wild Arms Offset hacks, Half-Pixel Offset), or improperly handled texture edges (Merge Sprite hack, Sprite/Round Sprite combobox). Native resolution , for the most part , fixes these issues, however , software rendering may be required as well.

The solution would be to either buy an official DualShock 2 3 controller and use an adapterappropriate 3rd party driver such as [[SCP Driver Package]], or mapping the button to a rarely used trigger/stick in LilyPad this way:

An additional button needs to be mapped to circle as well but configured to deliver "light" pressure. This is done by opening the gamepad plugin configuration and choosing a rarely used key - for example , the lower shoulder button L2 - and remapping it to the circle button, and setting the sensitivity to 0.500 or thereabouts. In the game, merely use the remapped L2@circle button to deliver "light" tap/hold tunes while the regular circle button can be used normally to deliver "hard" tap/hold tunes.

* [[How To Play PCSX2 Online|How to play PCSX2 online]]* [[Online PS2 Gamesgames]]

[[Category:OS X macOS emulation software]]