|
|
| Line 81: |
Line 81: |
|
| |
|
| ==Issues== | | ==Issues== |
| :''Main thread: <span class="plainlinks">[https://forums.pcsx2.net/Thread-Sticky-PCSX2-General-Troubleshooting-FAQ PCSX2 General Troubleshooting FAQ]</span>''
| | {{Main|PlayStation 2 emulators#Emulation issues}} |
| | |
| ===Automatic game fixes===
| |
| 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.
| |
| | |
| ===Major graphical glitches===
| |
| Graphical problems such as corrupted textures, missing effects, clipping light sources, burn-in or transparent objects being opaque can usually be solved by switching to the software renderer by pressing F9 while the game is running or via GSdx's config panel. If using the Direct3D 11 renderer, try the OpenGL renderer, as it may be more accurate. If you're using a stable build, try switching to the most recent nightly or dev build. Newer development builds of the emulator may have fixes or other features added to the hardware renderers, which remove common glitches like red or green bars appearing on the screen.
| |
| | |
| ===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 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 problems like hanging and absence of performance gain, or more severe ones like massive performance hits, save-state corruption (PCSX2 keeps a backup you can load with Shift+F3 in case any issues arise), or just plain crashing.
| |
| | |
| ===Crashes===
| |
| Crashes could be the result of several things.
| |
| 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 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. 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:
| |
| | |
| * Using a bad dump of a game, in which case you'll need to [[Ripping games|re-rip your disc]] or re-download the game you are trying to play.
| |
| * 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 in the speed hack menu.
| |
| * You need to check the Wiki to see if the game requires any specific settings regarding the Clamping Mode of the EE/VU.
| |
| * Cheats used in the game's .pnach file are invalid.
| |
| | |
| 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're overclocking.
| |
| | |
| ===Extreme fluctuation in emulation speed===
| |
| The large fluctuation in emulation is often caused by the games themselves and cannot be avoided, but there are a handful of cases where this is caused by specific configuration issues.
| |
| | |
| * Using a large internal resolution multiplier on a low-end GPU, even if the game runs mostly fine, can cause the emulator to suddenly need to do a lot of cumbersome operations on the VRAM. Low-end GPUs tend to have much lower VRAM bandwidth and will get crushed by that. This is 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 games 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 capable of going way above 100% speed in a stable fashion, random bits of time-stretched 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
| |
| | |
| ===Blurriness===
| |
| It's either interlacing or a filter in the game itself. For the former, switching the de-interlacing mode with F5 may help and 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 numbers 1-100) might work otherwise.
| |
| | |
| ===Black lines===
| |
| 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). The native resolution, for the most part, fixes these issues. However, software rendering may be required as well.
| |
|
| |
|
| ==Special hardware== | | ==Special hardware== |