PS2 emulator setup problem Let the CPU occupy less and be faster How to set up

The first point is that the PS2 emulator is different from the PC game calculations, so the graphics used in the PS2 emulator actually do not share the amount of data processed. The CPU usage running on the PCSX2 emulator must be higher than that of the most average PC games.

Sets can reduce occupancy, but not much different.

Here are three speed settings you can try to see if they don't work.

Choose the Linuz ISO C*** plugin, the last one is the audio plugin, some games SPU2-X will be faster some faster games ZEROSPU2 plugin, you can change both plugins.

In the configuration -**-plugin settings, turn off the GSDX plugin alpha correction (FBA), point to black the reasonable selection Z (logaeithmic z) after the original (native) is selected in the D3D structure, if they feel that the picture is very bad, you can try to select 2x native

3。Click on "Configure" - Analog amount set point speed for cracking, select the crack startup speed, then select EE cycle, vu cycle appropriation select 1, click on the following options, in addition to making a fast c*** game, see if there is a serious break, sound or other analog issues raised ee cycle reduction vu cycle appropriation off.

First of all, it should be noted that the PS2 emulator is different from the calculation method of PC games, so the graphics card does not actually share much data processing when the PS2 emulator is used. Therefore, the CPU usage of the PCSX2 emulator must be higher than that of most ordinary PC games.

Although it can reduce the occupancy rate if it is set up, it will not make much of a difference.

You can try the following 3 ways to speed up and see if it works.

Plug-in selection linuz iso c***,Finally, there is the audio plug-in,Some games will be faster with SPU2-X,Some games with zeroSPU2 plug-in is faster.,You switch between these 2 plug-ins.。

Let's try it 2In Configuration - > ** - > Plugin Settings, turn off the Alpha Correction (FBA) of the GSDX plug-in, click on the Logaeithmic Z option, and then select the original (Native) in D3D. If you think the picture is really too bad, you can try to choose 2X Native

3.Click on the configuration - > the simulation settings, click the speed hack, select the start speed hack, and then select 3 for the EE cycle, select 1 for the vu cycle appropriation, click all the options below, except for enabling fast c***, take a look at the game, if there is a serious sound break or other simulation problems, reduce the EE cycle to 2, and turn off the vu cycle appropriation.

In general, the simulation difficulties lie in both hardware and software.

First of all, since it is "simulation", it works by first using software to virtualize a hardware and software environment, and then run programs on this virtual environment.

For example, a processor is called a, and the way it executes a program is: "program a".

The other processor is called B, and its hardware, system bottom, and working mode are different from A, so if you want to use B to run A's program, you first need to use B to virtualize A, and then use virtual A to run the program: "B A program".

As you can see here, simulation requires more computationally required steps than natively. In addition, due to the different hardware structures, this virtual process is more complex, so the consumption of functions is relatively large (the main machine performance is actually used in this step).

In addition, the developers of the simulator (referring to unofficial simulators) do not have the design drawings and sources of the original machine**, and they need to guess the processing of some parts, and then write an algorithm that can achieve the purpose by themselves. In this way, it is possible to make a mistake or take a detour. The consequence of writing mistakes is simulator bugs, and the consequences of detours are inefficiencies.

In fact, it is impossible not to make mistakes or take detours.

And the official emulator (such as using PSP to simulate PS1), because it is its own machine, the complete design drawings and sources are available, and the developers of the emulator can write the most efficient algorithm, so the performance of the official emulator is much higher than that of the folk emulator, and it only needs to be slightly higher than the original machine.

The greater the difference in the hardware of the machine, the more difficult the simulation becomes, and even if it is successful, the simulation efficiency will not be too high. This is obvious, because the large differences in the hardware of the machines mean that there are many virtual places that need to be virtual, and these will reduce performance or be prone to errors. The representative is PS2, PS2 is notoriously difficult to simulate, as a popular model, it took more than ten years after it was launched to have a more reliable simulator, which shows its difficulty.

The main reason for this is that the hardware of PS2 and X86 PCs is too different.

And Xbox,Actually, it's not too difficult to simulate.,Its hardware is basically the same as PC.,It's not simulated because it's not too popular.。

The difficulty of the simulation is also related to the operating system, for example, it is easy to emulate iOS on an OSX system, but it is very difficult to emulate iOS on a Windows system.

You don't have the underlying hardware driver of PS2**No PS2 system source**I don't know what kind of workflow hardware process it is, so I can only run it with low efficiency, and the official emulator is very efficient, because they clearly know the underlying data and know how to simulate, so it is efficient. PSV handheld, the 2011 flagship mobile phone configuration, can run the PS2 emulator perfectly.