Setting up Windows version: Difference between revisions

Jump to navigation Jump to search
This is already a helpful guide in its current form; it just needs more work. It's far more useful than whatever woefully outdated, unmaintained crap that was here before. I'll continue to work on it now that I have some free time.
m (Restored the original until a new version is finished)
(This is already a helpful guide in its current form; it just needs more work. It's far more useful than whatever woefully outdated, unmaintained crap that was here before. I'll continue to work on it now that I have some free time.)
Line 1: Line 1:
{{FloatingTOC|side=right}}
{{FloatingTOC|side=right}}
=Introduction=


This guide explains how to download, install and properly configure '''PCSX2''' on '''Windows'''. It will also give some tips on how to use PCSX2 more efficiently. Keep in mind that the guide was written for PCSX2 '''v1.2.1''' but can still be used for other versions of the emulator.
==Introduction==
This guide explains how to download, install and properly configure '''PCSX2''' on '''Windows'''. It will also give some tips on how to use PCSX2 more efficiently. Keep in mind that the guide was written for PCSX2 '''v1.6.0''' and '''v1.7.0''' but can still be used for other versions of the emulator. If something in this guide seems confusing, please feel free to ask for help in [https://discord.com/channels/309643527816609793/315544036184293386 the official PCSX2 Discord.]


There are also [[Setting up Linux version|Linux]] and [[Setting up Mac version|Mac]] versions of this guide.
There is a [[Setting up Linux version|Linux]] version of this guide.


=Overview=
==Overview==
[[PCSX2]] is a [https://en.wikipedia.org/wiki/PlayStation_2 PlayStation®2] emulator capable of running commercial games. It's an open source project that runs on Windows, Mac and Linux. Like its predecessor project [https://en.wikipedia.org/wiki/PCSX-Reloaded PCSX] (a PlayStation®One emulator), it is based on a [https://en.wikipedia.org/wiki/PSEmu_Pro PSEmu Pro] spec plug-in architecture, separating several functions from the core emulator. PCSX2 requires a copy of the PS2 BIOS, which is not available for download from the developers, due to the copyright concerns and legal issues associated with it.
[[PCSX2]] is a [https://en.wikipedia.org/wiki/PlayStation_2 PlayStation®2] emulator capable of running commercial games. It is a free and open-source project that runs on Windows and Linux. A Mac version ceased development in 2012, but with the introduction of Apple's M1 SoC, [https://forums.pcsx2.net/Thread-Native-Mac-Testing-Build development of a new macOS version] is now ongoing, spearheaded by developer TellowKrinkle.


=Prerequisites=
Like its predecessor project [https://en.wikipedia.org/wiki/PCSX-Reloaded PCSX] (a PlayStation®One emulator), it is based on a [https://en.wikipedia.org/wiki/PSEmu_Pro PSEmu Pro] spec plug-in architecture, separating several functions from the core emulator. However, as of v1.7.1420, plug-in functionality has been merged into the core emulator. PCSX2 requires a copy of the PS2 BIOS, which is not available for download from the developers due to the copyright concerns and legal issues associated with it.
===Concerning BIOS===
 
You will need the BIOS files from '''your own''' PlayStation®2 console. They are not included with PCSX2 since they are copyrighted by Sony. Without them you won't be able to use the emulator at all, since PCSX2 requires these binaries to work. You'll find more information on how to dump\download the BIOS from your PS2 console [[#BIOS|later in this guide]].
===Release cycle===
PCSX2 operates on a hybrid rolling–stable release cycle. Rolling releases are odd-numbered (for example, 1.7.0), while stable releases are even-numbered (for example, 1.6.0). The stable release is not subject to change, while the rolling releases (known as nightlies) receive optional updates on a daily or – often – more-than-daily basis. The nightlies are the bleeding edge of what PCSX2 has to offer and are therefore often faster, more accurate, and more feature-rich. However, while updates to the nightlies are tested, they sometimes introduce small regressions – issues that weren't present before. Moreover, the location of settings is sometimes moved between rolling release versions. Some users may therefore find it more preferable to remain on the stable version.
 
==Requirements==
===BIOS===
You will need the BIOS files from '''''your own''''' PlayStation®2 console. They are not included with PCSX2 since they are copyrighted by Sony. Without them you won't be able to use the emulator at all, since PCSX2 requires these binaries to work. You'll find more information on how to dump/download the BIOS from your PS2 console [[#BIOS|later in this guide]].


===Minimum requirements===
===Minimum requirements===
These are the minimum system requirements to run PCSX2, bear in mind however that most games will be unplayable or slow with these low-end specs:
These are the minimum system requirements to run PCSX2. Bear in mind, however, that most games will be slow or even unplayable with these specs:
*CPU: Any that supports SSE2 (Pentium 4 and up, Athlon64 and up)
<spoiler show="Expand Settings" hide="Collapse Settings">
*GPU: Any that supports Pixel Shader model 2.0, except Nvidia FX series (broken SM2.0, too slow anyway)
* OS:
*512MB RAM (note Vista needs at least 2GB to run reliably)
:* Windows 7 or newer (32-bit or 64-bit; as of 1.7, Windows 7 is no longer supported)
 
*CPU:
Note that Windows XP will no longer be able to run PCSX2 compiled under modern MS Visual Studio by default (unless Windows XP is specified as a target [http://blogs.msdn.com/b/vcblog/archive/2012/06/15/10320645.aspx before building]).
:* SSE2 support (Pentium 4 and up, Athlon64 and up; as of 1.7, this has changed to any that supports SSE4)
:* [https://www.cpubenchmark.net/singleThread.html PassMark Single Thread Performance] rating near or greater than 1600
:* Two physical cores, with hyperthreading
*GPU:
:* Direct3D10 support
:* OpenGL 3.x support
:* PassMark G3D Mark rating around 3000 (GTX 750)
:* 2 GB of video memory
* RAM:
:* 4 GB of memory
</spoiler>


<!--Note that Windows XP will no longer be able to run PCSX2 compiled under modern MS Visual Studio by default (unless Windows XP is specified as a target [http://blogs.msdn.com/b/vcblog/archive/2012/06/15/10320645.aspx before building]).-->
===Recommended requirements===
===Recommended requirements===
These are the recommended system requirements to run PCSX2:
These are the recommended system requirements to run PCSX2:
*Windows Vista / Windows 7 (32bit or 64bit) with the latest DirectX
<spoiler show="Expand Settings" hide="Collapse Settings">
*CPU: Intel Core 2 Duo @ 3.2 GHz or better OR i3/i5/i7 @ 2,8 GHz or better OR AMD Phenom II @ 3,2 GHz or better
* OS:
*GPU: 8800gt or better (for Direct3D10 support)
:* Windows 10 (64-bit) or Windows 11
*RAM: 1GB on Linux, 2GB or more on Vista / Windows 7
* CPU:
:* [https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX2 AVX2 support]
:* [https://www.cpubenchmark.net/singleThread.html PassMark Single Thread Performance] rating near or greater than 2100
:* Four physical cores, with or without hyperthreading
*GPU:
:* Direct3D11 support
:* OpenGL 4.5 support
:* Vulkan 1.1 support (Vulkan renderer is currently only available in 1.7.2208 and up)
:* PassMark G3D Mark rating around 6000 (GeForce GTX 1050 Ti)
:* 4 GB of video memory
* RAM:
:* 8 GB of DDR3, DDR4, or DDR5 memory
</spoiler>
 
 
{{Tip|Because of the complex nature of emulation, even if you meet the recommended requirements there will be games that will '''NOT''' run at full speed due to emulation imperfection, floating point emulation differences, issues with emulator itself or other problems.}}
{{Tip|Because of the complex nature of emulation, even if you meet the recommended requirements there will be games that will '''NOT''' run at full speed due to emulation imperfection, floating point emulation differences, issues with emulator itself or other problems.}}
<br />


=Getting PCSX2=
==Getting PCSX2==
You can get PCSX2 for Windows [https://pcsx2.net/download/releases/windows/viewcategory/6-windows.html here]. There are 3 versions available for download: standalone installer, Windows binaries and Orphis' dev builds.
There are two versions of PCSX2 1.6.0 available for download: standalone installer and Windows binaries. There are also nightly builds (1.7.x).
 
* '''[https://pcsx2.net/download/releases/windows.html Standalone installer and Windows binaries can be found here.]'''
* '''[https://pcsx2.github.io/downloads.html Nightlies can be found here.]'''
 
===Standalone Installer===
===Standalone Installer===
This is the default option for most users. The installer will contain the latest stable version of PCSX2. After opening it, you will be able to select the installation options.
[[image:160_setup_1.png|400px|thumb|right|The first screen in the installation menu for PCSX2 1.6.0.]]
This is the default option for most stable build users. The installer will contain the latest stable version of PCSX2. After opening it, you will be able to select the installation options.


First of all you will be asked to provide the location for PCSX2 to install. The following image illustrates the default installation path:
First, you will be asked to provide the location for PCSX2 to install. 'Normal Installation' will install itself in your Program Files or another specified destination folder while storing user files (such as memory cards, save states, etc.) in a folder called 'PCSX2' in your 'Documents'. 'Portable Installation' will consolidate PCSX2 to one folder which you designate. Regardless of which you pick, you can also elect to create a start menu shortcut and a desktop shortcut; these are selected by default. After that, you will be able to customize which folder PCSX2 will install to. When you are satisfied with your selection, click 'Install', and the emulator will be installed to the chosen location.


[[image:PCSX2 Installer 2.png|400px|thumb|left|Click to enlarge]]
<!--The installer will also create the following folders under the user's ''My Documents'' folder (Those folders can be changed to a different location anytime you want. See [[#Folders|'''Folders''']] section of this guide for more information).
{{Clear new paragraph}}After clicking the ''Install'' button, the emulator will be installed to the chosen location. The installer will also create the following folders under the user's ''My Documents'' folder (Those folders can be changed to a different location anytime you want. See [[#Folders|'''Folders''']] section of this guide for more information).
*''bios'': This is where you should place your BIOS files. By default PCSX2 will look for BIOS in this folder.
*''bios'': This is where you should place your BIOS files. By default PCSX2 will look for BIOS in this folder.
*''cheats'': Cheats will be stored and read from here. Cheats are the files with .pnach extension.
*''cheats'': Cheats will be stored and read from here. Cheats are the files with .pnach extension.
Line 44: Line 77:
*''logs'': Emulator logs are going to be stored here.
*''logs'': Emulator logs are going to be stored here.
*''snaps'': Screenshots are stored into this folder (use ''F8'' to take a screenshot in game).
*''snaps'': Screenshots are stored into this folder (use ''F8'' to take a screenshot in game).
*''sstates'': [[Savestate]]s are stored here.
*''sstates'': [[Savestate]]s are stored here.-->
<br />
{{Warning|Remember that savestates made with a certain version of PSCX2 won't be compatible with other versions of the emulator.
{{Warning|Remember that savestates made with a certain version of PSCX2 won't be compatible with other versions of the emulator.
'''Save your game's progress on your memory card before updating PCSX2!'''.}}
'''Save your game's progress on your memory card before updating PCSX2!'''.}}
<br />
[[image:PCSX2 Installer 1.png|400px|thumb|left|Click to enlarge]]
{{Clear new paragraph}}


===Windows binaries===
===Windows binaries===
This option is recommended for advanced users. You will download the archive containing the Windows binaries. You should then unpack it in a desired location and run '''pscx2.exe'''. Start menu entries or a desktop shortcut will not be created automatically.
This option is recommended for advanced users. You will download the archive containing the Windows binaries. You should then unpack it in a desired location and run '''pscx2.exe'''. Start menu entries or a desktop shortcut will not be created automatically. This is the ideal solution if you want to keep the application portable. You will need [https://www.7-zip.org/ 7-Zip] to decompress the files and the [https://aka.ms/vs/17/release/vc_redist.x86.exe Visual C++ 2015–2019 x86 Redistributable package] for this version to work.
<br />
This is the ideal solution if you want to keep the application portable. You will need [https://www.7-zip.org/ 7-Zip] to decompress the files and the [https://download.microsoft.com/download/2/E/6/2E61CFA4-993B-4DD4-91DA-3737CD5CD6E3/vcredist_x86.exe Visual Studio 2013 redistributable package] for this version to work.
<br />
On its first run the emulator is going to create the previously mentioned folders.


===Orphis' Dev Builds===
===Nightly builds===
These "bleeding edge" builds are considered unstable but are perfect for those who wish to try out new PCSX2 features before they are released in an official stable build. Dev builds can be downloaded [https://buildbot.orphis.net/pcsx2 here]
These "bleeding edge" builds are considered unstable but are perfect for those who wish to try out new PCSX2 features before they are released in an official stable build. Nightly builds can be downloaded [https://pcsx2.github.io/downloads.html here]. They do not need to be installed.


=Running PCSX2 for the first time=
==Running PCSX2 for the first time==
PCSX2 has the first run configuration wizard to help you with configuration. The emulator will automatically store all settings, memcards and any new configuration related files in your ''My Documents'' folder if you used the installer, or in the same folder where ''pcsx2.exe'' is located if you downloaded the binary version.
PCSX2 has the first run configuration wizard to help you with configuration. The emulator will automatically store all settings, memcards and any new configuration related files in your ''My Documents'' folder if you used the installer, or in the same folder where ''pcsx2.exe'' is located if you downloaded the binary version.


[[image:PCSX2_Wizard_1.png|400px|thumb|left|Click to enlarge]]
After installation, if you run PCSX2 for the first time, it will initiate a first-time configuration. The first step of this short process is selecting your preferred language. This can be changed at any time after setup.
{{Clear new paragraph}}The first option is the language your wizard – and later PCSX2 – will be using. You will be able to change language anytime from PCSX2 main menu.
 
{{Clear new paragraph}}[[image:PCSX2_Wizard_2.png|400px|thumb|left|Click to enlarge]]
[[image:First Time Configuration 1.png|400px|thumb|center|The language selection screen in the setup menu for PCSX2 1.6.0.]]
 
{{Clear new paragraph}}In the next screen you will be able change the plugins you want to use. The plugins selected by default are the most compatible ones and will usually perform better. Do not change anything here if you are not yet familiar with PCSX2.
{{Clear new paragraph}}In the next screen you will be able change the plugins you want to use. The plugins selected by default are the most compatible ones and will usually perform better. Do not change anything here if you are not yet familiar with PCSX2.
You can also specify a different folder for your plugins if you want, by unchecking the ''use default setting'' checkbox and selecting a folder of your choice by clicking ''Browse''. ''Open in Explorer'' button will simply open a file explorer window in the folder you have specified.
You can also specify a different folder for your plugins if you want, by unchecking the ''use default setting'' checkbox and selecting a folder of your choice by clicking ''Browse''. ''Open in Explorer'' button will simply open a file explorer window in the folder you have specified.
{{Clear new paragraph}}[[image:PCSX2_Wizard_3.png|400px|thumb|left|Click to enlarge]]
 
[[image:PCSX2_Wizard_2.png|400px|thumb|center|Click to enlarge]]
 
{{Clear new paragraph}}[[image:PCSX2_Wizard_3.png|400px|thumb|center|Click to enlarge]]
{{Clear new paragraph}}In the third screen, you will be prompted to select one of your BIOS images from the list. If you can't see anything in this list, you need to either copy your BIOS files in the folder shown below, or change that folder to point to a location where BIOS images are saved. For more information about the BIOS, check the [[#BIOS|BIOS configuration section]] of this guide. Note that you will not be able to use PCSX2 without a proper BIOS image.  
{{Clear new paragraph}}In the third screen, you will be prompted to select one of your BIOS images from the list. If you can't see anything in this list, you need to either copy your BIOS files in the folder shown below, or change that folder to point to a location where BIOS images are saved. For more information about the BIOS, check the [[#BIOS|BIOS configuration section]] of this guide. Note that you will not be able to use PCSX2 without a proper BIOS image.  


To finish the configuration process press ''Finish'' button. You will be taken to the main GUI (Graphical User Interface) of PCSX2:
To finish the configuration process press ''Finish'' button. You will be taken to the main GUI (Graphical User Interface) of PCSX2:


[[File:NewGUI.png]]
[[File:NewGUI.png|center]]
 


From ''Config'' menu using ''Plugin/BIOS'' item, you can review and change the above settings or plugins used by PCSX2 at any time. More information about plugins will be given in the following section of the guide.
From ''Config'' menu using ''Plugin/BIOS'' item, you can review and change the above settings or plugins used by PCSX2 at any time. More information about plugins will be given in the following section of the guide.
Line 85: Line 113:


==Plugins configuration==
==Plugins configuration==
[[File:ConfigMenu.png|400px|thumb|left|Click to enlarge.]]
'''''Plugins have been merged into the core emulator as of 1.7.1420. Settings are similar between 1.6.0 and non-plugin versions, but you will not need to select plugins if you are running 1.7.1420 or above.'''


PCSX2 is a plugin oriented program. Your ''pcsx2.exe'' is the main processor that can emulate the real PS2 on the PC but it does not work alone. It needs a graphics plugin to display the game graphics and a sound plugin to play the game sounds and music, and it also needs a pad plugin to allow you to play using your keyboard, mouse or gamepad. Moreover there may be more than one plugin of each type so you can choose the one which is better suited for a particular game. All plugins are stored (by default) in the ''plugins'' folder of your main PCSX2 folder. Some plugins like ''GSdx'' for example can be updated quite often so you may want update only a chosen plugin from time to time. In order to do it you'll need to download the updated version and extract it by using the archiver into your plugins folder. Selecting your new plugin and changing its configuration may also be required.
[[File:ConfigMenu.png|400px|thumb|right|Click to enlarge.]]
{{Clear new paragraph}}PCSX2 1.6.0 is a plugin-oriented program. Your ''pcsx2.exe'' is the main processor that can emulate the real PS2 on the PC, but it does not work alone. It needs a graphics plugin to display the game graphics and a sound plugin to play the game sounds and music, and it also needs a pad plugin to allow you to play using your keyboard, mouse or gamepad. All plugins are stored (by default) in the ''plugins'' folder of your main PCSX2 folder.


'''Warning: If you select a plugin you will not be able to configure it until you press ''apply'' button!'''<br/>
'''Warning: If you select a plugin you will not be able to configure it until you press ''apply'' button!'''<br/>
Line 94: Line 124:
{{Clear new paragraph}}
{{Clear new paragraph}}
===Graphics (GS) plugins===
===Graphics (GS) plugins===
GS plugins are used by PCSX2 to provide the graphical output on the screen (i.e. to render the picture). Before choosing the plugin you will need to know if your video card is pixel shaders 2.0 capable (only the very old cards before Radeon 9xxx series or the Geforce 5xxx series does not support this standard).
[[image:GSDx2.png|thumb|right|GSdx]]
<br />
The default PCSX2 1.2.1 installation has three different GS plugins for you to select from (only two of the three are useful):
<br />
*GSdx v0.1.16
*ZeroGS v0.97.1
*GSnull driver v0.1.0
GSdx v0.1.16 is a DirectX 9 and DirectX 10/11 plugin by '''Gabest''' which is the most compatible and in most instances the fastest GS plugin for PCSX2. It requires at least pixel shaders 2 and SSE2 to work and Windows Vista/7/8 with a DirectX 10 compliant graphics card for DirectX10/11 mode. ZeroGS is a very old plugin which has not been updated in years. Still a very small number of games works better with this plugin, so you have an option to try it as a ''last resort''. GSnull is a null graphics plugin which will not output any kind of video. It is used for debugging purposes.


====GSdx====
GS plugins are used by PCSX2 to provide the graphical output on the screen (i.e. to render the picture). The default PCSX2 1.6.0 installation has three different GS plugins for you to select from:
[[image:GSDx2.png|thumb|GSdx]]
 
The default PCSX2 installation has GSdx in 5 versions: SSE2, SSSE3, SSE4.1, AVX and AVX2. They are in fact the same plugin compiled using different optimization instructions sets.<br />
* GSdx 1.2.0 (AVX2)
You must use only the versions supported by your CPU otherwise the emulator may crash. The difference between these versions speed-wise is in fact minuscule and only some games are showing any improvements in speed when using more optimized version. So if you are unsure, your safe choice is the SSE2 version. Here's the order from the "slowest" version to the "fastest" one for reference:
* GSdx 1.2.0 (SSE4/AVX)
#SSE2
* GSdx 1.2.0 (SSE2/AVX)
#SSSE3
 
#SSE4.1
These are in fact the same plugin compiled using different optimization instructions sets. You must use only the versions supported by your CPU otherwise the emulator may crash. The difference between these versions speed-wise is in fact minuscule and only some games are showing any improvements in speed when using more optimized version. So if you are unsure, your safe choice is the SSE2 version. The three above are listed in order from fastest to slowest.
#AVX
 
#AVX2
These are in fact the same plugin compiled using different optimization instructions sets. You must use only the versions supported by your CPU otherwise the emulator may crash. The difference between these versions speed-wise is in fact minuscule and only some games are showing any improvements in speed when using more optimized version. So if you are unsure, your safe choice is the SSE2 version. The three above are listed in order from fastest to slowest.


The new AVX and AVX2 instructions give a minor speed-up '''only when GSdx works in software mode'''. These versions will not improve the speed in hardware mode.<br />
Note to AMD users: please do '''NOT''' confuse SSE3 with SSSE3 (1 extra S) and SSE4A with SSE4.1, they are totally different and are '''NOT''' supported on AMD systems before Bulldozer/Bobcat. Please fall back to the SSE2 plugin instead in case your system has an older CPU.
Note to AMD users: please do '''NOT''' confuse SSE3 with SSSE3 (1 extra S) and SSE4A with SSE4.1, they are totally different and are '''NOT''' supported on AMD systems before Bulldozer/Bobcat. Please fall back to the SSE2 plugin instead in case your system has an older CPU.
{{Tip|
{{Tip|
Line 132: Line 154:


'''Renderer'''<br />
'''Renderer'''<br />
This option allows you choose the interface through which the graphics will be rendered.
This option allows you choose the interface through which the graphics will be rendered. In 1.6.0, the renderer options are as follows:
 
<spoiler show="Expand Renderers" hide="Collapse Renderers">
* ''Direct3D 11 (Hardware)'': GSdx will use Direct3D10/11 mode which is often faster and usually more compatible as well. It is '''recommended''' to use this option if your system supports it.
* ''Direct3D 11 (Software)'': GSdx will use its built-in software renderer which will not utilize your graphics card at all. The image will be rendered solely by your CPU. This will greatly reduce the rendering speed, but this is the most compatible mode. This option is recommended if you encounter graphics bugs with the hardware renderer.
* ''"OpenGL (hardware)"'': GSdx will use the OpenGL interface to render the image. This option is generally slower than Direct3D 11, but it often provides more accuracy.
* ''"OpenGL (software)"'': GSdx will use the OpenGL backend in software mode. Similar to Direct3D 11.
* ''None (Core Benchmark): The plugin will not render anything in these modes, thus not giving any output on the screen. It's useful for debugging purposes only.
</spoiler>


*''"Direct3D9 (Hardware)"'': GSdx will use the Direct3D capabilities of your graphics card.
In the latest 1.7.x builds, the renderer options are:
*''"Direct3D10 (Hardware)"'' or ''"Direct3D11 (Hardware)"'' '''(only selectable with DX10/11 graphics card)''': GSdx will use Direct3D10/11 mode which is often faster and usually more compatible as well. It is '''recommended''' to use this option if your system supports it.
<spoiler show="Expand Renderers" hide="Collapse Renderers">
*''"Direct3D9 (Software)"'', ''"Direct3D10 (Software)"'' or ''"Direct3D11 (Software)"'': GSdx will use its built-in software renderer which will not utilize your graphics card at all. The image will be rendered solely by your CPU. This will greatly reduce the rendering speed but unfortunately this is the most compatible mode. This option is recommended if you encounter graphics bugs with the hardware renderer.
* ''Direct3D11'': This option is generally the fastest but the least accurate.
*''"OpenGL (hardware)"'': GSdx will use the OpenGL interface to render the image. Currently this mode is a slower and less compatible equivalent of the DirectX renderers but it's the only option for Linux users.
* ''OpenGL'': This option is generally slower than Direct3D 11, but it often provides more accuracy.
*''"OpenGL (software)"'': GSdx will use the OpenGL backend in software mode.
* ''Vulkan'': This option is about as accurate as OpenGL while being generally faster. It is sometimes slower than Direct3D11, however.
*''"Direct3D9 (null)"'', Direct3D10/11 (null)", "Null (software)" or "Null (null)": The plugin will not render anything in these modes, thus not giving any output on the screen. It's useful for debugging purposes only.
* ''Software'': This option is intended to provide the most hardware-accurate experience. It can be slower than the hardware renderers, but you can increase the number of rendering threads (should your CPU have enough threads to support it) in order to reduce the performance hit.
</spoiler>


'''Interlacing'''<br />
'''Interlacing'''<br />
Line 153: Line 184:


'''Shaders section'''<br />
'''Shaders section'''<br />
[[image:GSdx_Shade_Boost_Settings.png|thumb|left|Shade boost]]
[[image:GSdx_Shade_Boost_Settings.png|thumb|right|Shade boost]]
*''Enable Shade Boost'': This option will help you to adjust saturation, brightness and contrast to your liking. Press ''Settings..'' button to configure. The ''Reset'' button allows you to set the sliders to their initial positions.
*''Enable Shade Boost'': This option will help you to adjust saturation, brightness and contrast to your liking. Press ''Settings..'' button to configure. The ''Reset'' button allows you to set the sliders to their initial positions.


Line 204: Line 235:


You can find some additional information on GSdx plugin [[GSdx|here]].
You can find some additional information on GSdx plugin [[GSdx|here]].
====ZeroGS====
[[image:ZeroGS_Settings.png|thumb|ZeroGS]]
ZeroGS is a DirectX 9 plugin developed by '''ZeroFrog'''. It is aimed for graphics cards supporting pixel shaders 2.0 or higher (if you select ZeroGS and your card does not have pixel shaders 2.0 you will get a "Error opening gs plugin" message and PCSX2 will close).
The following options are supported by ZeroGS plugin:
*''Interlace Enable'': This option will try to resolve some undesired interlacing effects (like screen "shaking"). Those games do not have interlacing issues will look better with this option disabled. You can toggle it while ingame by using ''F5'' key.
*''Bilinear Filtering'': This option will filter the textures when rendering them. Filtering may decrease your FPS unless you have a good graphics card. You can toggle it while ingame by pressing ''Shift+F5''. ZeroGS supports two bilinear filtering modes: '''normal bf''' and '''forced bf'''. For some games that will specifically ask for nearest-neighbor interpolation (no filtering mode)  ZeroGS will disable filtering in ''normal bf'' mode. In ''forced bf'' mode, on the other hand, bilinear interpolation (filtering) will be forced in any game. It should be noted that ''forced bf'' mode can introduce unwanted artifacts at the edges of textures in some games, however, in most cases, it will produce smoother looking picture.
*''Anti-aliasing'': This option will select the level of anti-aliasing will be used for rendering. Anti-aliasing will make edges look smoother but may introduce a performance hit. You can toggle this while in game by using ''F6'' key. There are four modes to select from:
**''None'': Will disable anti-aliasing
**''2x'': Will use 2X anti-aliasing
**''8x'': Will use 8X anti-aliasing
**''16x'': Will use 16X anti-aliasing
*''Wireframe rendering'': This mode will only render lines between vertices of 3D objects making them look like wire-frame models. You can toggle it while ingame by pressing ''F7''.
*''Capture avi'': This option will allow to capture video output in a file (see also ''Movie Capture'' for GSdx plugin). Press ''F12'' while in game and you will be asked to select a codec. Currently you can only select XviD as a codec (the plugin will crash with any other choice). Press ''F12'' the second time to finish capturing. The plugin saves file ''zerogs.avi'' in your PCSX2 folder.
*''Save snapshots as BMPs (default is JPG)'': ZeroGS captures screenshots and save them in ''snaps'' when you press ''F8'' ingame. By default screenshots are saved in JPG format. This option allows you changing the format to BMP to make the pictures lossless (note that they will require mode disk space).
*''Fullscreen'': This option will instruct the plugin to perform the output in fullscreen mode instead of default windowed mode. You can use ''Alt-Enter'' combination to enter fullscreen mode while ingame.
*''Widescreen'': This option will force ZeroGS to render in 16:9 resolution. Some games support wide screen mode natively, some require patching to make them work in widescreen mode and some will not support it at all. Look up to your specific game card to find more information.
*''Default Window Size'': This will specify the default size of ZeroGS window. The size of GS window will not affect ZeroGS performance.
{{Tip|While in game pressing ''Shift+F7'' will toggle on and off the Frames Per Second (FPS) indicator.}}
'''ZeroGS Advanced Options''':
These additional options can be used to tweak ZeroGS some more. Some games may benefit greatly from this set of options while others can be broken.
*If a particular set of options works very well for a particular game, then these options can be saved in the game's patch file which will be applied every time the game is loaded. This is useful when you want these options to be enabled only for that particular game and not to for other games.
*Each set of options in ZeroGS has a unique ID-number. To find this number click on the ''Compute'' OR ''IDS'' button in ZeroGS configuration dialog box. Insert the generated number into the game's corresponding [[Converting codes for PNACH use|pnach file]] (usually ''game CRC''.pnach) in a form '''zerogs=xxxxxxxx''' (where '''xxxxxxxx'''' is the mentioned number).
====GSnull Plugin====
This plugin will not render anything on screen. Its configuration consists only of ''enable logging'' checkbox useful solely for debugging purposes.


===Pad (input) plugins===
===Pad (input) plugins===
Default PCSX2 installation allows you to select one of three PAD plugins:
[[image:LilyPad_Settings.png|200px|thumb|right|Lilypad]]
#LilyPad v0.11.0
The default PCSX2 1.6.0 installation allows you to select the following PAD plugin:
#Pokopom 2.1.0
#LilyPad v0.12.1
#SSSPSX Pad v1.7.1


====LilyPad====
[[image:LilyPad_Settings.png|200px|thumb|left|Lilypad]]
This is arguably the most advanced PAD plugin for PCSX2. Use ''configure'' button to open LilyPad configuration dialog.<br />
This is arguably the most advanced PAD plugin for PCSX2. Use ''configure'' button to open LilyPad configuration dialog.<br />
You'll see a configuration dialog (pictured, click to enlarge).
You'll see a configuration dialog (pictured, click to enlarge).
Line 256: Line 246:
*LilyPad downside is that you '''will''' need to configure the plugin fully at least once before playing any game and it may take quite some time if you are not familiar with it.
*LilyPad downside is that you '''will''' need to configure the plugin fully at least once before playing any game and it may take quite some time if you are not familiar with it.
*For a very detailed description about what each setting does and how to properly configure it visit [[LilyPad]] article and/or the official [http://forums.pcsx2.net/Thread-LilyPad-0-10-0 thread of the plugin].
*For a very detailed description about what each setting does and how to properly configure it visit [[LilyPad]] article and/or the official [http://forums.pcsx2.net/Thread-LilyPad-0-10-0 thread of the plugin].
{{Clear new paragraph}}
====Pokopom====
[[image:Pokopom_Settings.jpg|thumb|left|Pokopom]]
This plugin is much easier to handle for the new users whilst it still allows for a great options flexibility (and some of its options are not implemented in LilyPad) Use ''configure'' button to open Pokopom configuration dialog.<br />
You'll see a configuration dialog (pictured, click to enlarge).
*Pokopom is a relatively new input plugin developed by '''KrossX'''. Some of the unique features include pressure sensitivity support, rumble with a custom curve and more.
*For a very detailed description about what each setting does and how to properly configure the plugin, visit the [http://forums.pcsx2.net/Thread-Pokopom-KrossX-s-Pad-Plugin official thread of the plugin] and/or check the small [https://github.com/KrossX/Pokopom/wiki/Pokopom Pokopom Wiki].
{{Clear new paragraph}}
====SSSPSX====
[[image:SSSPSX_Settings.png|thumb|left|SSSPSX]]
This plugin is the oldest of the three and does not require much fiddling but somewhat lacks in the options department. But there are still some very picky games that refuse to work with any other plugin except for SSSPSX (for instance [[Warriors of Might and Magic]]). Use configure button to open SSSPSX configuration dialog.<br />
You'll see a configuration dialog (pictured, click to enlarge).
*The dialog will allow you to configure keyboard keys to emulate PS2 controller input. If you want to clear a key assignment you can click on the respective button and wait until the ''Timeout'' timer reaches zero.
*The plugin can emulate up to two DualShock2 controllers (use dialog tabs to switch between them).
*SSSPSX Pad supports analog input emulation. Use ''LX'', ''LY'', ''RX'', ''RY'' buttons to assign keys to analog axis. ''LX'' is for Left analog X-Axis, ''LY'' is for Left analog Y-Axis, ''RX'' is for Right analog X-Axis and ''RY'' is for Right analog Y-Axis.
*''R3'' and ''L3'' emulate buttons on the analog stick of the PS2 controller.


===Sound plugins===
===Sound plugins===
====SPU2-X====
[[image:SPU2-X_Settings.png|200px|thumb|right|SPU2-X]]
[[image:SPU2-X_Settings.png|200px|thumb|left|SPU2-X]]
SPU2-X is the most advanced, compatible and up-to-date sound plugin for PCSX2. It was first based on '''Gigaherz's''' SPU2ghz and later modified by '''Jake Stine (Air)'''. This is the only SPU2 plugin that supports audio processing effects (like reverberation and Dolby Pro Logic (if your sound card is able to decode it)). Many games only work correctly with SPU2-X.
SPU2-X is the most advanced, compatible and up-to-date sound plugin for PCSX2. It was first based on '''Gigaherz's''' SPU2ghz and later modified by '''Jake Stine (Air)'''. This is the only SPU2 plugin that supports audio processing effects (like reverberation and Dolby Pro Logic (if your sound card is able to decode it)). Many games only work correctly with SPU2-X.
*''Interpolation'': Specifies the interpolation algorithm (smoothing low frequency sounds not unlike anti-aliasing algorithms for graphics):
*''Interpolation'': Specifies the interpolation algorithm (smoothing low frequency sounds not unlike anti-aliasing algorithms for graphics):
Line 319: Line 288:


*''Enable debug options'': This option is only useful for developers (it will allow for extensive logging and dumps).
*''Enable debug options'': This option is only useful for developers (it will allow for extensive logging and dumps).
====ZeroSPU2====
[[image:ZeroSPU_Settings.png|200px|thumb|left|ZeroSPU2]]
ZeroSPU is an older cousin of SPU2-X which was developed by '''zerofrog'''. The plugin has the following features:
*''Time Scaling'': This option will use time stretching akin to ''TimeStretch'' mode of SPU2-X. The time-scaling feature works best under Windows, but is also implemented in Linux.
*''Real time mode'': This is a tighter time stretching mode for games that need additional accuracy and lower latency.
*''Audio/video recording'': This option will let you record sound in ''zerospu2.wav'' each time you start playing a game.
*''Mute'': This option will mute sound giving a bit of extra speed.
{{Clear new paragraph}}


===CDVD plugins===
===CDVD plugins===
[[image:Cdvd_Gigaherz_Settings.png|right|thumb|Gigaherz's CDVD]]
In most cases you will only need to use the PCSX2 built-in ''ISO loader'' ('''ISO''' option in the ''CDVD'' menu, then use '''ISO Selector''' to select actual game image from the ''image history list'' or choose ''Browse...'' to select the image from disk.<br />
In most cases you will only need to use the PCSX2 built-in ''ISO loader'' ('''ISO''' option in the ''CDVD'' menu, then use '''ISO Selector''' to select actual game image from the ''image history list'' or choose ''Browse...'' to select the image from disk.<br />
However, if you want to play a game from the actual DVD disk or to create a dump of an ISO file use '''Plugin''' option in the ''CDVD'' menu. It will let you use one of the PCSX2 CDVD plugins instead of ''ISO loader''.<br />
However, if you want to play a game from the actual DVD disk or to create a dump of an ISO file use '''Plugin''' option in the ''CDVD'' menu. It will let you use one of the PCSX2 CDVD plugins instead of ''ISO loader''.<br />
Default PCSX2 installation has three CDVD plugins:  
The default PCSX2 1.6.0 installation has one CDVD plugin:  
#Gigaherz's CDVD v0.8.0
#Gigaherz's CDVD v0.8.0
#Linuz ISO CDVD v0.9.0
#CDVDnull v0.6.0.


====cdvdGigaherz====
[[image:Cdvd_Gigaherz_Settings.png|left|thumb|Gigaherz's CDVD]]
*Configuration allows you to select your DVD-ROM drive letter. This option will allow you to play directly from your PS2 DVD without dumping it to an ISO image. Put your PS2 DVD disk in the selected drive before starting emulation.  
*Configuration allows you to select your DVD-ROM drive letter. This option will allow you to play directly from your PS2 DVD without dumping it to an ISO image. Put your PS2 DVD disk in the selected drive before starting emulation.  
{{Tip|This is the only plugin that at least partially supports disk changing. Some games may wait for the next disk to advance; this plugin is the only choice for such games!}}
{{Clear new paragraph}}
====Linuz ISO CDVD====
[[image:LinuzIso_Config.png|left|thumb|Linuz ISO CDVD]]
*The unique feature of this plugin is that it allows you to compress and to use compressed ISO images in order to save your HDD space. It can also decompress compressed earlier ISO images.
*To compress, decompress or use an already existing ISO image click ''Select ISO'' button. Once you've selected an image you can compress or decompress it by using the corresponding button. The selected image will also be used automatically when you start emulation.
**Note that plugin has two compression modes: ''.Z'' (faster compression, bigger result size) and ''.BZ'' (slower compression, smaller result size).
*The ''Enable Block Dump=>ISO name.dump'' checkbox is used manly for debugging purposes. When checked, the plugin creates '''''ISO name'''.dump'' file in the PCSX2 folder. This file will contain every sector read during the emulation of the game. You can select this file using ''Select ISO'' button afterwards and run like any other ISO image but if the game will attempt to read a sector that was not included in the file, you will experience a hang or the emulator will crash.
{{Clear new paragraph}}
====CDVD Null====
This is a null plugin, meaning it simply does nothing.


===Dev9 (HDD and ethernet) plugins===
===Dev9 (HDD and ethernet) plugins===
Line 395: Line 335:
{{Clear new paragraph}}
{{Clear new paragraph}}


=Emulation Settings (Core configuration)=
==Emulation Settings (Core configuration)==
''Emulation Settings'' config window is the collection of main PCSX2 settings to tune the behavior of PCSX2 itself (not unlike the plugins separate configurations can tune the behavior of a particular plugin). You can access the window from ''Config'' => ''Emulation settings'' menu. There are 6 tabs, ''EE/IOP'', ''VUs'', ''GS'', ''GS Window'', ''Speedhacks'' and ''Gamefixes'' each of which has its own set of settings.
''Emulation Settings'' config window is the collection of main PCSX2 settings to tune the behavior of PCSX2 itself (not unlike the plugins separate configurations can tune the behavior of a particular plugin). You can access the window from ''Config'' => ''Emulation settings'' menu. There are 6 tabs, ''EE/IOP'', ''VUs'', ''GS'', ''GS Window'', ''Speedhacks'' and ''Gamefixes'' each of which has its own set of settings.


==EE/IOP==
===EE/IOP===
[[file:EE-IOP.png|300px|thumb|right]]
EE/IOP tab stands for ''Emotion Engine / Input Output Processor'' which are the core components of the PlayStation®2. The tab contains 4 settings.
EE/IOP tab stands for ''Emotion Engine / Input Output Processor'' which are the core components of the PlayStation®2. The tab contains 4 settings.
[[file:EE-IOP.png|300px|thumb|right]]


*''Emotion Engine'': Enables or disables ''recompiler'' (i.e. the program that translates the native PS2 code into the native x86 code, instead of slowly interpret each PS2 command) for PS2 ''Emotion Engine'' (EE) processor emulation. ''Interpreter'' mode disables the recompiler making the emulation painfully slow. ''Recompiler'' mode is extremely compatible, so the ''interpreter'' mode shouldn't be used for anything but debugging purposes.
*''Emotion Engine'': Enables or disables ''recompiler'' (i.e. the program that translates the native PS2 code into the native x86 code, instead of slowly interpret each PS2 command) for PS2 ''Emotion Engine'' (EE) processor emulation. ''Interpreter'' mode disables the recompiler making the emulation painfully slow. ''Recompiler'' mode is extremely compatible, so the ''interpreter'' mode shouldn't be used for anything but debugging purposes.
Line 411: Line 351:
{{Clear new paragraph}}
{{Clear new paragraph}}


==VUs==
===VUs===
[[image:VUs.png|300px|thumb|right]]
VUs stand for ''Vector Unit''s which are the PlayStation®2 co-processors working in parallel with the EE and IOP CPUs. The PlayStation®2 has two VUs called ''VU0'' and ''VU1''.  
VUs stand for ''Vector Unit''s which are the PlayStation®2 co-processors working in parallel with the EE and IOP CPUs. The PlayStation®2 has two VUs called ''VU0'' and ''VU1''.  
[[image:VUs.png|300px|thumb|right]]


* You can change VUs compilation modes independently for VU0 and VU1 (although it makes sense to set them to the same value). As with ''EE'' and ''IOP'' CPUs there is an old and very slow ''interpreter'' mode which is useful only for debugging. VUs however have two different ''recomplilers'' -- ''microVU'' (more compatible default recompiler) and ''superVU'' (legacy less compatible recompiler used mainly for debugging, but it can be slightly faster). It is recommended to leave both settings at their default ''microVU Recompiler'' value.
* You can change VUs compilation modes independently for VU0 and VU1 (although it makes sense to set them to the same value). As with ''EE'' and ''IOP'' CPUs there is an old and very slow ''interpreter'' mode which is useful only for debugging. VUs however have two different ''recomplilers'' -- ''microVU'' (more compatible default recompiler) and ''superVU'' (legacy less compatible recompiler used mainly for debugging, but it can be slightly faster). It is recommended to leave both settings at their default ''microVU Recompiler'' value.
Line 425: Line 364:
{{Clear new paragraph}}
{{Clear new paragraph}}


==GS==
===GS===
[[image:GS.png|300px||thumb|right]]
GS stands for ''Graphics Synthesizer'' PlayStation®2 co-processor responsible for rendering the graphics (but is also used by some games for additional calculations and other purposes). The PCSX2 will work in conjunction with the selected GS plugin (like for ex. [[#GSdx|GSdx]] plugin) to emulate PS2 graphical co-processor and convert its output into input understood by the PC video cards.
GS stands for ''Graphics Synthesizer'' PlayStation®2 co-processor responsible for rendering the graphics (but is also used by some games for additional calculations and other purposes). The PCSX2 will work in conjunction with the selected GS plugin (like for ex. [[#GSdx|GSdx]] plugin) to emulate PS2 graphical co-processor and convert its output into input understood by the PC video cards.
[[image:GS.png|300px||thumb|right]]


*''Framelimiter'': The options in this group can be used to control the frame rate of your games in various ways.
*''Framelimiter'': The options in this group can be used to control the frame rate of your games in various ways.
Line 448: Line 385:
{{Clear new paragraph}}
{{Clear new paragraph}}


==GS Window==
===GS Window===
[[image:GSWindow.png|300px|thumb|right]]
This tab will allow you to control the PCSX2 GUI game window (video output window) behavior:
This tab will allow you to control the PCSX2 GUI game window (video output window) behavior:
[[image:GSWindow.png|300px|thumb|right]]


*''Aspect Ratio'': You can select the window aspect ratio (shape) here. If you have a widescreen (16:9) monitor you may want to remove the left and right black bars to get a better experience. Unfortunately many games do not natively support wide screen aspect ratio and selecting it here will cause the image to stretch which may not be a desirable side effect. Some games however may be helped to support 16:9 resolution by special ''widescreen patches'' made by the community. If the game neither have the native 16:9 support nor the patch to overcome this your only options are to play it with 4:3 aspect ratio with black bars or bear with image stretching whichever option is the best for you. You can choose ''Standard (4:3)'', ''Widescreen (16:9)'' or ''Fit to Window/Screen'' here. In the latter case image will always be stretched.
*''Aspect Ratio'': You can select the window aspect ratio (shape) here. If you have a widescreen (16:9) monitor you may want to remove the left and right black bars to get a better experience. Unfortunately many games do not natively support wide screen aspect ratio and selecting it here will cause the image to stretch which may not be a desirable side effect. Some games however may be helped to support 16:9 resolution by special ''widescreen patches'' made by the community. If the game neither have the native 16:9 support nor the patch to overcome this your only options are to play it with 4:3 aspect ratio with black bars or bear with image stretching whichever option is the best for you. You can choose ''Standard (4:3)'', ''Widescreen (16:9)'' or ''Fit to Window/Screen'' here. In the latter case image will always be stretched.
Line 473: Line 409:
{{Clear new paragraph}}
{{Clear new paragraph}}


==Speed Hacks==
===Speed Hacks===
[[image:Speedhacks.png|300px|thumb|right]]
Speed hacks are various techniques used to speed up emulation at the cost of emulating accuracy. All of these options '''can cause severe bugs, crashes and other abnormal behavior''' so use them with caution! Some games may benefit from these settings immensely while others can be slowed down or broken. Read the on-screen hints and messages to get more information (especially if you're new to this) they will help you not to break anything.<br />
Speed hacks are various techniques used to speed up emulation at the cost of emulating accuracy. All of these options '''can cause severe bugs, crashes and other abnormal behavior''' so use them with caution! Some games may benefit from these settings immensely while others can be slowed down or broken. Read the on-screen hints and messages to get more information (especially if you're new to this) they will help you not to break anything.<br />
If your system is '''powerful enough''' to emulate your game in full speed '''you do not need to enable anything here''' because none of these options can improve compatibility.
If your system is '''powerful enough''' to emulate your game in full speed '''you do not need to enable anything here''' because none of these options can improve compatibility.
[[image:Speedhacks.png|300px|thumb|right]]


<spoiler show="Expand Speed Hacks" hide="Collapse Speed Hacks">
*''Enable speedhacks'': You can disable all speed hacks in one click by unchecking this box. This may be useful if your game is unstable and you are narrowing down the possible cause of this.
*''Enable speedhacks'': You can disable all speed hacks in one click by unchecking this box. This may be useful if your game is unstable and you are narrowing down the possible cause of this.
*''Emotion Engine (EE) Cyclerate'': This hack will increase the time required for one EE operation to complete (essentially down-clocking ''[[#EE/IOP|Emotion Engine]]''). Your CPU will get additional cycles to spend on emulation of other PS2 processors. This will speed up those game that do not utilize EE processor fully (VUs and GS will get additional CPU power). In contrast, the games that use EE fully will appear slowed and may start skipping frames.  
*''Emotion Engine (EE) Cyclerate'': This hack will increase the time required for one EE operation to complete (essentially down-clocking ''[[#EE/IOP|Emotion Engine]]''). Your CPU will get additional cycles to spend on emulation of other PS2 processors. This will speed up those game that do not utilize EE processor fully (VUs and GS will get additional CPU power). In contrast, the games that use EE fully will appear slowed and may start skipping frames.  
Line 493: Line 429:
*''microVU Hacks'': These hacks are only applied when microVU is selected as the VUs recompiler. If superVU is selected, these hacks do not apply.
*''microVU Hacks'': These hacks are only applied when microVU is selected as the VUs recompiler. If superVU is selected, these hacks do not apply.
**''mVU Flag Hack'': This hack will skip some VUs flag updates by detecting the program blocks that will not read VUs flags, saving CPU time. SuperVU recompiler is said to have this hack built-in by default. The hack is set by default and is very compatible (but still may cause bad graphics in case the detection algorithm fails).
**''mVU Flag Hack'': This hack will skip some VUs flag updates by detecting the program blocks that will not read VUs flags, saving CPU time. SuperVU recompiler is said to have this hack built-in by default. The hack is set by default and is very compatible (but still may cause bad graphics in case the detection algorithm fails).
**''MTVU (Multi-Threaded microVU1)'': This option will isolate [[#VUs|VU1]] emulation to a separate CPU thread, making it a huge speed up for CPUs with 3 or more cores. The option is highly compatible (except for some possible synchronization errors or timing issues that may cause problems in a handful of games). If you have a dual core CPU you may still want to try this option (there are some reports of speed increase even on these CPUs).
**''MTVU (Multi-Threaded microVU1)'': This option will isolate [[#VUs|VU1]] emulation to a separate CPU thread, making it a huge speed up for CPUs with 3 or more cores. The option is highly compatible (except for some possible synchronization errors or timing issues that may cause problems in a handful of games). If you have a dual-core CPU you may still want to try this option (there are some reports of speed increase even on these CPUs).


*''Restore defaults'': Click this to restore all settings to their default values.
*''Restore defaults'': Click this to restore all settings to their default values.
</spoiler>


{{Clear new paragraph}}
{{Clear new paragraph}}


==Game fixes==
===Game fixes===
[[image:GameFixes.png|300px|thumb|right]]
This tab contains some game-specific hacks and fixes. These fixes are disabled by default but enabled automatically if the game in question is detected to be running. The ''Automatic Gamefixes'' option can be also switched off (although it is not recommended) in ''System'' sub-menu of PCSX2 main menu. You should not enable these hacks unless you have a game that somehow was not detected by PCSX2 automatically (note also that some of these fixes are not applied automatically).  
This tab contains some game-specific hacks and fixes. These fixes are disabled by default but enabled automatically if the game in question is detected to be running. The ''Automatic Gamefixes'' option can be also switched off (although it is not recommended) in ''System'' sub-menu of PCSX2 main menu. You should not enable these hacks unless you have a game that somehow was not detected by PCSX2 automatically (note also that some of these fixes are not applied automatically).  


The game-specific fixes are temporal solutions to some unresolved emulation issues. PCSX2 developers provided them to increase compatibility levels so some games, otherwise broken, can still be enjoyed. As the emulation compatibility will continue to improve some of these options may become obsolete and will be removed.  
The game-specific fixes are temporal solutions to some unresolved emulation issues. PCSX2 developers provided them to increase compatibility levels so some games, otherwise broken, can still be enjoyed. As the emulation compatibility will continue to improve some of these options may become obsolete and will be removed.  
[[image:GameFixes.png|300px|thumb|right]]


Most of these hacks are needed because the PS2 has different float arithmetic than x86 CPUs. Some of these differences do not lead to any problems, others however may cause serious issues in certain games. You can read hacks descriptions and hints to get more information.
Most of these hacks are needed because the PS2 has different float arithmetic than x86 CPUs. Some of these differences do not lead to any problems, others however may cause serious issues in certain games. You can read hacks descriptions and hints to get more information.


*''VU Add hack'': Enable it only for [[Star Ocean: Till the End of Time]],[[Valkyrie Profile 2: Silmeria]] and [[Radiata Stories]].
<spoiler show="Expand Fixes List" hide="Collapse Fixes List">
*''VU Clip Flag Hack'': This hack is only needed when ''superVU'' is selected as [[#VUs|VUs]] recompiler. Needed for [[Template:Megami_Tensei_series|Persona]] games.
* ''VU Add hack'': Enable it only for [[Star Ocean: Till the End of Time]],[[Valkyrie Profile 2: Silmeria]] and [[Radiata Stories]].
*''FPU Compare Hack'': Enable it only for [[Digimon Rumble Arena 2]].
* ''VU Clip Flag Hack'': This hack is only needed when ''superVU'' is selected as [[#VUs|VUs]] recompiler. Needed for [[Template:Megami_Tensei_series|Persona]] games.
*''FPU Multiply Hack'': Needed only for [[Tales of Destiny]].
* ''FPU Compare Hack'': Enable it only for [[Digimon Rumble Arena 2]].
*''FPU Negative Div Hack'': Needed for [[Mobile Suit Gundam: Encounters in Space|Gundam]] games, fixes the camera view.
* ''FPU Multiply Hack'': Needed only for [[Tales of Destiny]].
*''VU XGkick Hack'': Adds more delay to ''VU XGkick'' instructions. Needed for [[Elemental Gerad: Matoe, Suifu no Ken|Elemental Gerad]].
* ''FPU Negative Div Hack'': Needed for [[Mobile Suit Gundam: Encounters in Space|Gundam]] games, fixes the camera view.
*''FFX videos fix'': Fixes gray overlay garbage in the videos of [[Final Fantasy X]].
* ''VU XGkick Hack'': Adds more delay to ''VU XGkick'' instructions. Needed for [[Elemental Gerad: Matoe, Suifu no Ken|Elemental Gerad]].
*''EE timing Hack'': Known to help [[Shin Megami Tensei: Digital Devil Saga|Digital Devil Saga]], [[SSX]], [[Resident Evil: Dead Aim]].
* ''FFX videos fix'': Fixes gray overlay garbage in the videos of [[Final Fantasy X]].
*''Skip MPEG Hack'': Use this to skip freezing intro videos to avoid hanging.
* ''EE timing Hack'': Known to help [[Shin Megami Tensei: Digital Devil Saga|Digital Devil Saga]], [[SSX]], [[Resident Evil: Dead Aim]].
*''OPH flag Hack'': Needed for [[Bleach: Blade Battlers]], Growlancers [[Growlanser II: The Sense of Justice|II]] and [[Growlanser III: The Dual Darkness|III]] and [[Wizardry: Tale of the Forsaken Land|Wizardry]].
* ''Skip MPEG Hack'': Use this to skip freezing intro videos to avoid hanging.
*''Ignore DMAC writes when it's busy'': Needed for [[Mana Khemia: Alchemists of Al-Revis]] and [[Metal Saga]].
* ''OPH flag Hack'': Needed for [[Bleach: Blade Battlers]], Growlancers [[Growlanser II: The Sense of Justice|II]] and [[Growlanser III: The Dual Darkness|III]] and [[Wizardry: Tale of the Forsaken Land|Wizardry]].
*''Simulate VIF1 FIF read ahead'': Can help games which load slow (for ex. [[Test Drive Unlimited]] or [[Transformers]])
* ''Ignore DMAC writes when it's busy'': Needed for [[Mana Khemia: Alchemists of Al-Revis]] and [[Metal Saga]].
* ''Simulate VIF1 FIF read ahead'': Can help games which load slow (for ex. [[Test Drive Unlimited]] or [[Transformers]])
*''Delay VIF1 stalls (VIF1 FIFO)'': Fixes [[SOCOM II: U.S. Navy SEALs]] HUD.
*''Delay VIF1 stalls (VIF1 FIFO)'': Fixes [[SOCOM II: U.S. Navy SEALs]] HUD.
*''Ignore Bus Direction on Path 3 Transfer'': Fixes [[Hot Wheels: Beat That!|Hot Wheels]].
* ''Enable the GIF FIFO'': Needed for Hotwheels, Wallace and Grommit, and DJ Hero.
*''Switch to GSdx software rendering when an FMV plays'': This will allow [[GSdx]] to automatically switch to a software renderer when FMV starts to play and back to hardware renderer when the video is finished. This option is very useful considering the number of games that have issues with videos in GSdx hardware mode.
* ''Switch to GSdx software rendering when an FMV plays'': This will allow [[GSdx]] to automatically switch to a software renderer when FMV starts to play and back to hardware renderer when the video is finished. This option is very useful considering the number of games that have issues with videos in GSdx hardware mode.
*''Preload TLB hack to avoid TLB miss on Goemon'': Helps to fix [[Bouken Jidai Katsugeki Goemon]] TLB miss issue.
* ''Preload TLB hack to avoid TLB miss on Goemon'': Helps to fix [[Bouken Jidai Katsugeki Goemon]] TLB miss issue.
* ''VU I bit Hack avoid constant recompilation (Scarface: The World is Yours)''
* ''VU I bit Hack avoid constant recompilation (Crash Tag Team Racing)''
</spoiler>


{{Clear new paragraph}}
{{Clear new paragraph}}


==Presets==
==Presets==
For those users do not want to spend the time fiddling with all the hacks, fixes and speed-ups described above and especially for the new users who wants to start playing games right away the system of options sets or ''presets'' was introduced. This system will restrict you to only 6 slider positions instead of myriad options and PCSX2 will automatically assume using specific options, game fixes and speed-ups according to the ''presets'' level you choose. Check ''Preset'' checkbox on the botton of settings window to enable using presets. This will disable most of the options on many tabs (because they will now be controlled by PCSX2 automatically). Presets go from the safest (but also the slowest) to the most unsafe (but the fastest one). You should start with level '''1''' or '''2''' if you have a powerful machine. Level '''3''' and '''4''' are for those who do not have a good machine or have a very demanding game to emulate. Level '''5''' or '''6''' are not recommended and should only be used as a last resort (note that some game can even be ''slowed down'' by those levels).
For those users do not want to spend the time fiddling with all the hacks, fixes and speed-ups described above and especially for the new users who wants to start playing games right away the system of options sets or ''presets'' was introduced. This system will restrict you to only 6 slider positions instead of myriad options and PCSX2 will automatically assume using specific options, game fixes and speed-ups according to the ''presets'' level you choose. Check ''Preset'' checkbox on the botton of settings window to enable using presets. This will disable most of the options on many tabs (because they will now be controlled by PCSX2 automatically). Presets go from the safest (but also the slowest) to the most unsafe (but the fastest one). You should start with level '''1''' or '''2''' if you have a powerful machine. Level '''3''' and '''4''' are for those who do not have a good machine or have a very demanding game to emulate. Level '''5''' or '''6''' are not recommended and should only be used as a last resort (some game can even be ''slowed down'' by those levels).
<br/>
 
<br/>
In 1.7, presets 4–6 have been removed.


=PCSX2 main menu=
=PCSX2 main menu=
Line 575: Line 515:
*'''Debug menu''': This item will only appear in case you're using debug build. It will allow developers to use built-in debugger to trace code and see the contents of emulated PS2 registers and memory. It has little to no use for the ordinary users.
*'''Debug menu''': This item will only appear in case you're using debug build. It will allow developers to use built-in debugger to trace code and see the contents of emulated PS2 registers and memory. It has little to no use for the ordinary users.


<br />
==Shortcuts/hotkeys==
=PCSX2 Shortcuts/hotkeys=
For a full list of currently supported keyboard shortcuts, you can refer to [[Hotkeys|this article]] or check page 4 of the PCSX2 readme.
For a full list of currently supported keyboard shortcuts, you can refer to [[Hotkeys|this article]] or check page 4 of the PCSX2 readme.


PCSX2 also supports overriding the hotkeys set by using a custom made ini file (''PCSX2_keys.ini''). For instructions on how to create it please also refer to [[Hotkeys#Editing Keyboard shortcuts|this article]].
PCSX2 also supports overriding the hotkeys set by using a custom made ini file (''PCSX2_keys.ini''). For instructions on how to create it please also refer to [[Hotkeys#Editing Keyboard shortcuts|this article]].


<br />
<!--=Further reading, links and credits=
 
=Further reading, links and credits=
This guide is based on the original [http://pcsx2.net/config-guide.html Official English PCSX2 configuration guide v1.2.1] written by '''Bositman'''.
This guide is based on the original [http://pcsx2.net/config-guide.html Official English PCSX2 configuration guide v1.2.1] written by '''Bositman'''.


Line 602: Line 539:
*The official video configuration guide (for PCSX v1.0.0) can be found [https://www.youtube.com/embed/plo8rMytBNg?wmode=transparent&rel=0&autoplay=1&fs=1&start=0 here].
*The official video configuration guide (for PCSX v1.0.0) can be found [https://www.youtube.com/embed/plo8rMytBNg?wmode=transparent&rel=0&autoplay=1&fs=1&start=0 here].
*The translations of the official PCSX2 configuration guide v1.2.1 on different '''languages''' can be found [http://pcsx2.net/config-guide/guide-translations.html here].  
*The translations of the official PCSX2 configuration guide v1.2.1 on different '''languages''' can be found [http://pcsx2.net/config-guide/guide-translations.html here].  
*The shorter version of the official PCSX2 configuration guide v1.2.1 made by [http://forums.pcsx2.net/User-avih avih] can be found [http://forums.pcsx2.net/Thread-Quick-Start-PCSX2-Configuration-Guide-v1-0-0 here].
*The shorter version of the official PCSX2 configuration guide v1.2.1 made by [http://forums.pcsx2.net/User-avih avih] can be found [http://forums.pcsx2.net/Thread-Quick-Start-PCSX2-Configuration-Guide-v1-0-0 here].-->




{{General articles}}
{{General articles}}
[[Category:Guides]]
[[Category:Guides]]
ninja
770

edits

Navigation menu