Setting up Windows version (0.9.8): Difference between revisions

Jump to navigation Jump to search
Line 101: Line 101:
* '''EERec''' -- Should be ON. This will allow the emulator to use recompiler on EE (Emotion Engine) and IOP (I/O Processor) processors which is much faster with almost no compatibility problems (Recompilation is a process of generating the x86 machine code from PS2 machine code).
* '''EERec''' -- Should be ON. This will allow the emulator to use recompiler on EE (Emotion Engine) and IOP (I/O Processor) processors which is much faster with almost no compatibility problems (Recompilation is a process of generating the x86 machine code from PS2 machine code).
* '''VU0Rec'''/'''VU1Rec''' -- Should be both ON. This will allow the emulator to use recompiler on VU0/VU1 (Vector Units) processors. These two options will enable so-called SuperVU recompiler. The compatibility of such a recompilation is lower compared to EE/IOP but still is fairly high. There are games that may suffer from this recompilation having some weird graphical bugs. However you'll not be able to play without this options because of the lack of CPU power.
* '''VU0Rec'''/'''VU1Rec''' -- Should be both ON. This will allow the emulator to use recompiler on VU0/VU1 (Vector Units) processors. These two options will enable so-called SuperVU recompiler. The compatibility of such a recompilation is lower compared to EE/IOP but still is fairly high. There are games that may suffer from this recompilation having some weird graphical bugs. However you'll not be able to play without this options because of the lack of CPU power.
** '''microVU0'''/'''microVU1''' -- It's recommended to have them ON. These two options will tell the emulator to use '''cottonvibe's''' microVU recompiler instead of SuperVU. microVU is more compatible  although a bit slower and some games broken with SuperVU will be playable with microVU. To get more info use this [http://forums.pcsx2.net/thread-11210.html link]
** '''microVU0'''/'''microVU1''' -- It's recommended to have them ON. These two options will tell the emulator to use '''cottonvibe's''' microVU recompiler instead of SuperVU. microVU is more compatible  although a bit slower and some games that were broken with SuperVU will be playable with microVU. Use this [http://forums.pcsx2.net/thread-11210.html link] to get more info.
* '''Multi threaded GS mode (MTGS)''' -- Should be ON for double cores or hyper-threading CPUs. This option will spawn a separate thread for GS processing (i.e. for GSDX plugin). So if your CPU has at least two cores the main PCSX2 thread will run using the first core and GSDX will use the second. Without this option PCSX2 will only use one core and will be much slower.
* '''Multi threaded GS mode (MTGS)''' -- Should be ON for double cores or hyper-threading CPUs. This option will spawn a separate thread for GS processing (i.e. for GSDX plugin). So if your CPU has at least two cores the main PCSX2 thread will run using the first core and GSDX will use the second. Without this option PCSX2 only uses one core and is much slower.
* '''Frame Limiting''' option. This will allow you to limit the speed of emulation to the default PS2 speed if your CPU is fast enough to emulate the game faster than this default speed. PCSX2 is limiting speed by adjusting the number of frames (screen updates) per second. This number is 60fps for NTSC games and 50fps for PAL games. Thus it's easier to archive the playable speeds with PAL games (and they do not have interlaced frames) but NTSC games may look a little smoother. It is best to set this option to Limit allowing PCSX2 to slow down to the real PS2 speed or else your game will run too fast. On the other hand if your game is too slow and nothing else can help (see the section '''Speed Hacks''') you can try to ''skip'' some frames (do not compute them at all). Skipping frames is not a precise process because every game uses its own method to compute and generate visuals so for some of them this will not work and may make others run too "choppy" or cause some artifacts. Try to tune it only if your game is too slow to play without frame skipping. Some values advises:  
* '''Frame Limiting''' option. This will allow you to limit the speed of emulation to the default PS2 speed if your CPU is fast enough to emulate the game faster than this default speed. PCSX2 is limiting speed by adjusting the number of frames (screen updates) per second. This number is 60fps for NTSC games and 50fps for PAL games. Thus it's easier to archive the playable speeds with PAL games (and they often do not have interlace problems) but NTSC games may look a little smoother. It is best to set this option to Limit allowing PCSX2 to slow down to the real PS2 speed or else your game will run too fast. On the other hand if your game is too slow and nothing else can help (see the section '''Speed Hacks''') you can try to ''skip'' some frames (do not compute them at all). Skipping frames is not a precise process because every game uses its own method to compute and generate visuals so for some of them this will not work and may make others run too "choppy" or cause some artifacts. Try to tune it only if your game is too slow to play without frame skipping. Some values advises:  
# Set '''Custom FPS Limit''' to 0 (it can change default 50 or 60 fps for a game, though you will not need this option now).  
# Set '''Custom FPS Limit''' to 0 (it can change default 50 or 60 fps for a game, though you will not need this option now).  
# Set '''Skip Frames when slower than''' to a high enough value like 30 or 40. It will tell PCSX2 to start skipping only if your game runs slower than 30 or 40 FPS.  
# Set '''Skip Frames when slower than''' to a high enough value like 30 or 40. It will tell PCSX2 to start skipping only if your game runs slower than 30 or 40 FPS.  
67,563

edits

Navigation menu