Changes
Jump to navigation
Jump to search
→Issues: Reword a few things due to them being outdated or not present anywlmore in recent versions, add a bunch of other stuff
===Major graphical glitches===
Whenever a game has graphical problems such as garbage texture, missing effects, light sources visible through 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
===Poor performance in software mode===
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).
The process described above is partially automated in recent development versions of PCSX2 but you might still need to tweak it to get optimal performance levels
===Multi-threaded microVU===
Multi-threaded microVU (MTVU), while generally a very useful speed-hack, might sometime cause minor problem 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.
===Crashes===
Crashes could be the results of several things.
If the log warns you one or several time 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].
If your GPU drivers also crash simultaneously (or you get massive graphical corruption on your desktop and/or a BSOD while trying to run a game) this means you're either using outdated drivers or you're trying to use an AMD card with the OGL renderer and Blending Accuracy set to none, in which case either set it to basic or higher or use the DX11 renderer instead.
If the log warns you about TLB miss you are either:
* Playing the game directly from your DVD drive, in which case you should [[Ripping Games|rip the game]] and play using the .iso instead (it's not advised to play directly from your DVD drive).
* Trying to play a game that isn't supported by the emulator, in which case you cannot do anything except trying another version of the game (PAL or NTSC-J for example).
* Trying to play a game with a massive or in some cases any EE overclock applied, in which case turn it back down the speedhack menu
If PCSX2 still crashes after doing all of the above, check that you aren't using any speed-hacks and that your system is stable and not overheating especially if you are overclocking.
===Extreme fluctuation emulation speed===
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
* Using large internal resolution multiplier on a lower end GPU, even if the game runs mostly fine some effect can cause the emulator to suddenly have to do a lot of very heavy operation on the VRAM, lower GPU tend to have much lower VRAM bandwidth and will get absolutely crushed by what PCSX2 tries to do, especially true when using Large framebuffer and even more so when using the OGL renderer, obviously the only real fix is turning the resolution down and disabling Large Framebuffer if possible
* Playing the game directly from the original DVD using a disc drive, in which case you should [[Ripping Games|rip the game]] and play using the .iso instead
* Having the Blending accuracy set too high in the OGL renderer (Full and Ultra mostly)
* Using EE overclock in some games
===Intermittent warped audio===
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 audio can be heard occasionally or even frequently, there are however a few ways to work around that issue..
* Set the audio syncing method to Async Mix (can cause A/V sync issue, not recommended with rhythm games), do not set it to None as it basically does the same thing as Async Mix but has more issues
* Unlock the PCSX2 framerate limiter and use an external one such as MSI Afterburner
===Blurry===
===Black lines===
Black lines are caused by scaling to a non-integer internal resolution (anything other than Yx Native), texture filtering (turn off or to half at mostTry 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.
==Special hardware==
