1,809
edits
Changes
Jump to navigation
Jump to search
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
grammar
[[File:New_God_Hand_Config.jpg|thumb|Get God Hand running on a laptop]][http://www.mediafire.com/view/115130h5rc6qe6b/LilyPad-SCP.lily Native DS3 controls with LilyPad-SCP] - Import this with the 'Load Bindings' button in LilyPad's config.
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.
===Video===
==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===
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
===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 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.
===Crashes===
Crashes could be the results of several things.
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].
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:
===Extreme fluctuation emulation speed===
* 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
===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 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
===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). Native resolution , for the most part , fixes these issues, however , software rendering may be required as well.
==Special hardware==
The solution would be to either buy an official DualShock 3 controller and use an appropriate 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.
==See also==
