Editing PS2 Emulation

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 2: Line 2:
= Description =
= Description =


<pre>PlayStation 2 emulation on the PlayStation 4 is handled with little difference to the PlayStation 3,
<pre>PlayStation 2 emulation on the PlayStation 4 is handled with little difference to the PlayStation 3.
as some issues on the PlayStation 3 were not fixed on the PlayStation 4's emulator. As a result, the PS4 inherited some of PS3's emulation glitches, along with introducing new ones.
Some issues that the PlayStation 3 encountered have moved on to the PlayStation 4, along with a few new ones.
That came as a result of PS4's weakness towards emulation, which likely pressured Sony into trading accuracy for performance.


Each PS2ONPS4 package file (.pkg) includes the emulator itself. The ps4 does not have a native built-in emulator in its firmware, but it does a few PS2 emulator specific features, like the functions sceLncUtilIsPs2Emu, sceShellCoreUtilGetImposeMenuFlagForPs2Emu, sceSystemServiceAddLocalProcessForPs2Emu, and sceSystemServiceShowImposeMenuForPs2Emu.
The PS4 is too weak for emulation, therefore Sony had to sacrifice accuracy for performance.


Emulators are programmed to be accurate for the games they were designed to emulate. In turn, this makes accurate emulation challenging, as emulators include per title patches and different default settings. The Playstation 2 hardware is a complex system to emulate; any small change in configuration can make or break a game.
Each PS2ONPS4 package file (.pkg) includes the emulator itself. The ps4 does not have a native built-in emulator in its firmware, but it does have some PS2 emulator specific features. Like the functions sceLncUtilIsPs2Emu, sceShellCoreUtilGetImposeMenuFlagForPs2Emu, sceSystemServiceAddLocalProcessForPs2Emu, or sceSystemServiceShowImposeMenuForPs2Emu.
Currently the most commonly used emulator is Jakv2 as it is the most compatible one out there. When game crashes are concerned, RECVX is typically used, whereas for VU accuracy it is roguev1.


The PS2 BIOS is included in the game's pkg, the same one used on the ps2_netemu. The lack of encryption mechanism for PS2 game disc image file is also important. This time it is a plain ISO file, but the emulator still supports LIMG sector that allows the usage of non-2048 sector size discs. Moreover, memory cards are also decrypted, but the emulator checks the CRC of some of the regions to ensure that the memory card was not modified. This PS2 Emulator also supports LUA scripting by "Lua Bridge", which is a powerful interface that may prove exceptionally handy in fixing games.
Emulators are programmed to be accurate for the games that they were made for. And that alone is a challenge for accurate emulation. Since emulators include per title patches, and different default settings, and since the Playstation 2 hardware is a complex system to emulate, any small change in configuration can make or break a game.


This is first time that Sony has ever cared about floats in its emulators. Compared to the PS3 CPU, x86-64 is doing a worse job in mimicking FPU and VU floats calculation behavior. This is resolved by clamping, accurate math used per memory offset, and/or converting floats to double precision. The emulator uses openCL for GS, and likely other components as well.</pre>
Currently the most commonly used emulator is Jakv2 because it is the most compatible. For game crashes we use RECVX, and for VU accuracy we use roguev1.
 
The BIOS itself is included in the game's pkg and it is the exact same BIOS that was used in the ps2_netemu. Another important thing is the lack of encryption mechanism for PS2 game disc image file, this time it is just a plain ISO file. But the emulator still supports LIMG sector that allows the usage of non-2048 sector size discs. Memory card is also decrypted, but the emulator checks the CRC of some of the regions to ensure that the memory card was Not modified. The PS2 Emulator supports LUA scripting by "Lua Bridge", and it is an extremely powerful interface that provide many possibilities to improve compatibility.
 
This is first time that Sony has ever cared about floats in their emulators. Compared to the PS3 CPU, x86-64 is doing a worse job in mimicking FPU and VU floats calculation behavior. This is resolved by clamping, accurate math used per memory offset, and/or converting floats to double precision. The emulator uses openCL for GS, and likely other components as well.</pre>


= Emulator Configuration =
= Emulator Configuration =
The emulator can be configured through 4 files.


== Files ==
== Files ==
Emulator configuration is handled by 4 files:


* '''config-emu-ps4.txt''' - Stores paths, basic video/audio settings in official packages. But unofficially can be also used for advanced settings for global effect in multi disc .pkg with all commands originally used in cli.conf file.  
* '''config-emu-ps4.txt''' - Stores paths, basic video/audio settings in official packages. But unofficially can be also used for advanced settings for global effect in multi disc .pkg with all commands originally used in cli.conf file.  
Line 26: Line 29:


== Commands ==
== Commands ==
The rest of the CLI and LUA commands can all be found inside of any emulator's '''Eboot.bin''' file.
'''Known functions:''' Require cleanup.
<br>The rest of the CLI and LUA commands can all be found inside of any emulator's '''Eboot.bin''' file.
=== config-emu-ps4.txt commands ===
=== config-emu-ps4.txt commands ===


Line 120: Line 124:
| --boot-disc-id || 1-5  ||  sets boot disc for multi-disc pkg || --boot-disc-id=0
| --boot-disc-id || 1-5  ||  sets boot disc for multi-disc pkg || --boot-disc-id=0
|-
|-
| --switch-disc-reset ||  1 = Enables resetting the game upon disc swap, 0 = Disables resetting the game upon disc swap||  0 Can be used to prevent resetting the game when switching multiple discs. Useful for games like Samurai warriors 2 that include an import data feature. Sadly this command isn't supported by many emulators, but jakv2 is confirmed to support it || --switch-disc-reset=1
| --switch-disc-reset ||  1 = Enables resetting the game upon disc swap
0 = Disables resetting the game upon disc swap||  0 Can be used to prevent resetting the game when switching multiple discs. Useful for games like Samurai warriors 2 that include an Import data feature. Sadly this command isn't supported by many emulators, but jakv2 is confirmed to support it || --switch-disc-reset=1
|-
|-
| --cdvd-sector-read-cycles || 0.1 = Fastest, 80000 = Slowest|| Set DVD reading speed. Higher values are slower, lower values are faster. Kinetica uses 40000, Psychonauts 4000, Red dead revolver 5000, Rise of kasai 31000. Some games require moderate speed, too slow or too fast could cause audio problems.|| --cdvd-sector-read-cycles=40000
| --cdvd-sector-read-cycles || 0.1 = Fastest, 80000 = Slowest|| Set DVD reading speed. Higher values are slower, lower values are faster. Kinetica uses 40000, Psychonauts 4000, Red dead revolver 5000, Rise of kasai 31000. Some games require moderate speed, too slow or too fast could cause audio problems.|| --cdvd-sector-read-cycles=40000
Line 171: Line 176:
=== XXXX-YYYYY_cli.conf commands ===
=== XXXX-YYYYY_cli.conf commands ===


<pre>These commands work in config-emu-ps4.txt, but the official way to use them is through the CLI file (It is also needed for multi-disc packages). Additionally, some commands are still not discovered, and known commands might be missing their values. </pre>
<pre>Please note that the commands listed here also work in config-emu-ps4.txt. But the official way to use them is by CLI file. The CLI file way is also needed for multi-disc packages. Some of the commands are still not discovered, and some known commands are missing their values. </pre>
<pre>All commands are pre-made. Creating new CLI commands is impossible.
<pre>All CLI commands are pre-made. It's not possible to create CLI commands out of thin air.
The values of the commands are also pre-defined by Sony and/or have a set of possible values or ranges.
The values of the commands are also pre-defined by Sony and/or have a set of possible values or ranges.
Some CLI commands have no effect, as they were added to the eboot.bin without being programmed. Some useful commands were removed or added in or from different emu revisions, or their effects were changed. In some emulators, CLI configurations can be found in the ram at SceLibcHeap[0]-3-881004000.</pre>
Some CLI commands have no effect and were added to the eboot.bin without any programming. Some useful commands were removed or added in different emu revisions, or their effects changed. In some emultors, CLI configuration can be found in the ram at SceLibcHeap[0]-3-881004000.</pre>
====EmotionEngine (MIPS-IV)====
====EmotionEngine (MIPS-IV)====
=====[https://www.psdevwiki.com/ps2/Emotion_Engine EE]=====
=====[https://www.psdevwiki.com/ps2/Emotion_Engine EE]=====
<pre>Commands for the emulated Emotion Engine. These commands may improve performance, or allow for better sync.</pre>
<pre>Commands for the emulated Emotion Engine. These commands may help with performance gain, or better sync.</pre>
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
! Command !! Values !! Notes !! Usage
! Command !! Values !! Notes !! Usage
Line 183: Line 188:
|  || Speedhacks / Desync Fixes|| ||
|  || Speedhacks / Desync Fixes|| ||
|-
|-
| --ee-cycle-scalar || Accelerate EE cycles: (0.99 => 0.1)<br>Decelerate EE cycles: (1.1 => 5.0) ||  Accelerating can help improve EE-DMA sync at the cost of performance, whereas decelerating can help ensure EE is in sync with VU0-VU1 while improving performance (too much deceleration can cause stuttery fmvs.) The default value is 1.0 || --ee-cycle-scalar=1.0  
| --ee-cycle-scalar || Accelerate EE cycles: (0.99 => 0.1)<br>Decelerate EE cycles: (1.1 => 5.0) ||  Accelerating can help with improving EE-DMA sync at the cost of performance. Decelerating can help with improving EE's sync with VU0-VU1 while also improving performance; too much deceleration can cause stuttery fmvs. The default value is 1.0 || --ee-cycle-scalar=1.0  
|-
|-
| --ee-context-switch-cycles || Accelerate cycles (360 => 0) <br>Decelerate cycles (361 => ∞ ) || Its effects are mysterious, but likely affect COP0. Does not work on Jak emulators. Default value is 360, and its type is 4 bytes. Seems to be useful for Bee Movie and Metal Gear Solid 3.|| --ee-context-switch-cycles=2700?
| --ee-context-switch-cycles || [Overclocking(?)] (0.99 => 0.1) <br>[Cycle skipping(?)] (1.1 => ∞ ) || Similar effect to eecyclescalar, but it is still unknown what its effect truly is. Does not work on Jak emulators || --ee-context-switch-cycles=2700?
|-
|-
| [[--ee-hook|--ee-hook]] || AdvanceClock<br>FastForwardClock<br>Mfifodrain || Set a function to be applied every time the PC register reaches the selected offset in the EE memory. FastForwardClock stalls the EE for an unknown non-changeable number of cycles, while AdvanceClock stalls the EE for an allocated number of cycles to push other processing units to align with the EE's speed, and temporarily allocate higher cpu power for them, which is helpful when the vu1 requires higher juice for its performance, and when the vu0 and dma channels run slower than the ee. Mfifodrain is still unknown. [[--ee-hook|For more examples]] ||--ee-hook=0x0025A9F2,AdvanceClock,,500 <br>--ee-hook=0x0019F0AD,FastForwardClock
| [[--ee-hook|--ee-hook]] || AdvanceClock<br>FastForwardClock<br>Mfifodrain || Set a function to be applied every time the PC register reaches the selected offset in the EE memory. FastForwardClock is likely an overclocking function, while AdvanceClock stalls the EE for an allocated time to either improve sync, or performance. Mfifodrain is still unknown. [[--ee-hook|For more examples]] ||--ee-hook=0x0025A9F2,AdvanceClock,,500 <br>--ee-hook=0x0019F0AD,FastForwardClock
|-
|-
|-style="background-color:#D7EF54"
|-style="background-color:#D7EF54"
|  || Game fixes || ||
|  || Game fixes || ||
|-
|-
| --ee-jit-pagefault-threshold || 0-254 || Ignore JIT pagefaults, usually caused by data placed right after code. JIT try to recompile it, and obviously hit some bad opcodes. This command reduces the occurrence of crashes the higher it is. || --ee-jit-pagefault-threshold=40
| --ee-jit-pagefault-threshold || 0-254 || Ignore JIT pagefaults, usually caused by data placed right after code. JIT try to recompile it, and obviously hit some bad opcodes. Command reduces the occurrence of crashes the higher it is. || --ee-jit-pagefault-threshold=40
|-
|-
| --ee-block-validation || PageProt, PageProtection, Hash, Full, none || way of validating that block been modified, and require recompilation. [[https://github.com/PCSX2/pcsx2/blob/4db6b287cda817345f7ed4268a8a68f9fda76f26/pcsx2/Memory.cpp#L869| Some info about PageProt way]] || --ee-block-validation=None
| --ee-block-validation || PageProt, PageProtection, Hash, Full, none || way of validating that block been modified, and require recompilation. [[https://github.com/PCSX2/pcsx2/blob/4db6b287cda817345f7ed4268a8a68f9fda76f26/pcsx2/Memory.cpp#L869| Some info about PageProt way]] || --ee-block-validation=None
Line 273: Line 278:


=====FPU=====
=====FPU=====
<pre>The FPU is a fast single-precision unit that typically serves the EE by calculating in-game physics. It mostly controls the accuracy of the movement of in-game objects, or the game's gravity as a whole. In some cases, it is best to use COP2 commands with the FPU's to ensure the accuracy of the game's geometrical calculations.</pre>
<pre>The FPU is a fast single-precision unit that typically serves the EE by calculating in-game physics. It's also called (COP1).</pre>
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
! Command !! Values !! Notes !! Usage  
! Command !! Values !! Notes !! Usage  
Line 290: Line 295:
|-  
|-  
| --fpu-accurate-addsub || 0 = Disabled<br>1 = Enabled || Allows the FPU to accurately Add/Subtract for all offsets by using software floats rather than hardware floats. (Extremely slow) || --fpu-accurate-addsub=1
| --fpu-accurate-addsub || 0 = Disabled<br>1 = Enabled || Allows the FPU to accurately Add/Subtract for all offsets by using software floats rather than hardware floats. (Extremely slow) || --fpu-accurate-addsub=1
|-
| --fpjk-muldiv-range || offset (0x0 - 0x1FFFFFF) || ? || --fpjk-muldiv-range=0x123456
|-  
|-  
| --fpu-accurate-muldiv-range || start,end offset (0x0 - 0x1FFFFFF) || Allows the FPU to accurately Divide/Multiply by 0 in the specified ee memory range by using software floats rather than hardware floats. || --fpu-accurate-muldiv-range=0x1acce0,0x2acce0
| --fpu-accurate-muldiv-range || start,end offset (0x0 - 0x1FFFFFF) || Allows the FPU to accurately Divide/Multiply by 0 in the specified ee memory range by using software floats rather than hardware floats. || --fpu-accurate-muldiv-range=0x1acce0,0x2acce0
Line 298: Line 305:
|  || Speedhacks || ||
|  || Speedhacks || ||
|-
|-
| --fpu-rsqrt-fast-estimate || 0, 1 || Decreases RSQRT's accuracy. It is enabled by default. Disabling it is required for the full accuracy of the FPU. || --fpu-rsqrt-fast-estimate=1
| --fpu-rsqrt-fast-estimate || 0, 1 || Decreases RSQRT's accuracy. Enabled by default. Disabling it is required for full FPU accuracy || --fpu-rsqrt-fast-estimate=1
|-
|-
| --fpu-accurate-mul-fast || 0, 1 || A command that prevents muldiv commands from slowing the emulation down.  || --fpu-accurate-mul-fast=1
| --fpu-accurate-mul-fast || 0, 1 || A command that prevents muldiv commands from causing slowdowns.  || --fpu-accurate-mul-fast=1
|-style="background-color:#FFAA00"
|-style="background-color:#FFAA00"
|  || Other || ||
|  || Other || ||
Line 315: Line 322:


=====COP2=====
=====COP2=====
<pre>VU0 Macro-mode. These commands may assist the FPU further.</pre>
<pre>VU0 Macro-mode.</pre>
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
! Command !! Values !! Notes !! Usage  
! Command !! Values !! Notes !! Usage  
Line 321: Line 328:
|  || Speedhacks || ||
|  || Speedhacks || ||
|-
|-
| --cop2-opt-flags || 0, 1 ,2 || Optimize flags upon recompilation (1 is safe, 2 update sticky, and mac flag on every status flag update) setting it to 0 can in some cases improve FPU accuracy. [https://github.com/PCSX2/pcsx2/blob/58f5a5b915915293b90e7e8f34c33f9c0424d1e8/pcsx2/x86/microVU_Misc.h#L280 More Info] || --cop2-opt-flags=1
| --cop2-opt-flags || 0, 1 ,2 || Optimize flags upon recompilation (1 is safe, 2 update sticky, and mac flag on every status flag update) [https://github.com/PCSX2/pcsx2/blob/58f5a5b915915293b90e7e8f34c33f9c0424d1e8/pcsx2/x86/microVU_Misc.h#L280 More Info] || --cop2-opt-flags=1
|-  
|-  
| --cop2-opt-vf00 || 0, 1, 2 || Optimization for the vf00 register. || --cop2-opt-vf00=1
| --cop2-opt-vf00 || 0, 1, 2 || Optimization for the vf00 register. || --cop2-opt-vf00=1
Line 327: Line 334:
| --cop2-const-prop || 0, 1 || Disables or enables constant propagation. Can Be Used as speedhack for COP2 hungry games when set to 1 [https://github.com/PCSX2/pcsx2/blob/58f5a5b915915293b90e7e8f34c33f9c0424d1e8/pcsx2/x86/microVU_Misc.h#L312 More info] || --cop2-const-prop=1
| --cop2-const-prop || 0, 1 || Disables or enables constant propagation. Can Be Used as speedhack for COP2 hungry games when set to 1 [https://github.com/PCSX2/pcsx2/blob/58f5a5b915915293b90e7e8f34c33f9c0424d1e8/pcsx2/x86/microVU_Misc.h#L312 More info] || --cop2-const-prop=1
|-  
|-  
| --cop2-di-bits || 0, 1 || 0 to skip setting invalid, and div by Zero flags in status register, and therefore improve performance. Can be used as speedhack as it skip costly calculations. || --cop2-di-bits=0
| --cop2-di-bits || 0, 1 || 0 to skip setting invalid, and Div by Zero flags in status register, and therefore improve performance. Can be used as speedhack as it skip costly calculations. || --cop2-di-bits=0
|-style="background-color:#D7EF54"
|-style="background-color:#D7EF54"
|  || Game fixes || ||
|  || Game fixes || ||
Line 333: Line 340:
| --cop2-no-clamping ||  1 = Extra + preserve sign<br>0 = Extra || Changes the clamping behavior of the COP2. The default emulator's behavior is none of the included values and cannot be set by CLI commands.  || --cop2-no-clamping=0
| --cop2-no-clamping ||  1 = Extra + preserve sign<br>0 = Extra || Changes the clamping behavior of the COP2. The default emulator's behavior is none of the included values and cannot be set by CLI commands.  || --cop2-no-clamping=0
|-
|-
| --cop2-accurate-range || start,end offset (0x0 - 0x1FFFFFF) ||Accurate Mul/Div/Add/Sub math instructions for the COP2 by using software floats rather than hardware floats. Can be used for full COP2 mathematical accuracy in the specified range. || --cop2-accurate-range=0x123456,0x134567
| --cop2-accurate-range || start,end offset (0x0 - 0x1FFFFFF) ||Accurate Mul/Div/Add/Sub Math instructions for the COP2 by using software floats rather than hardware floats. Can be used for full COP2 Mathematical accuracy in the specified range. || --cop2-accurate-range=0x123456,0x134567
|-  
|-  
| --cop2-no-clamp-range || start,end offset (0x0 - 0x1FFFFFF) || Per-range clamping for COP2. || --cop2-no-clamp-range=0x123456,0x134567
| --cop2-no-clamp-range || start,end offset (0x0 - 0x1FFFFFF) || Per-range clamping for COP2. || --cop2-no-clamp-range=0x123456,0x134567
|-  
|-  
| --cop2-accurate-mul-range || start,end offset (0x0 - 0x1FFFFFF) || Accurate multiplication instructions for the COP2 in the specified range by using software floats rather than hardware floats || --cop2-accurate-mul-range=0x123456,0x134567
| --cop2-accurate-mul-range || start,end offset (0x0 - 0x1FFFFFF) || Accurate Multiplication instructions for the COP2 in the specified range by using software floats rather than hardware floats || --cop2-accurate-mul-range=0x123456,0x134567
|-  
|-  
| --cop2-accurate-mul || 1 = Enabled<br>0 = Disabled || Allows the COP2 to accurately multiply for all offsets by using software floats rather than hardware floats. (Extremely slow) || --cop2-accurate-mul=1
| --cop2-accurate-mul || 1 = Enabled<br>0 = Disabled || Allows the COP2 to accurately Multiply for all offsets by using software floats rather than hardware floats. (Extremely slow) || --cop2-accurate-mul=1
|-  
|-  
| --cop2-accurate-addsub ||  1 = Enabled<br>0 = Disabled || Allows the COP2 to accurately Add/Subtract for all offsets by using software floats rather than hardware floats. (Extremely slow) || --cop2-accurate-addsub=1
| --cop2-accurate-addsub ||  1 = Enabled<br>0 = Disabled || Allows the COP2 to accurately Add/Subtract for all offsets by using software floats rather than hardware floats. (Extremely slow) || --cop2-accurate-addsub=1
|-
|-
| --cop2-accurate-addsub-range || start,end offset (0x0 - 0x1FFFFFF) || Allows the COP2 to accurately Add/Sub in the specified ee memory range by using software floats rather than hardware floats. || --cop2-accurate-addsub-range=0x123456,0x134567
| --cop2-accurate-addsub-range || start,end offset (0x0 - 0x1FFFFFF) || Allows the COP2 to accurately Add/Subtract in the specified ee memory range by using software floats rather than hardware floats. || --cop2-accurate-addsub-range=0x123456,0x134567
|-
|-
|-style="background-color:#FFAA00"
|-style="background-color:#FFAA00"
|  || Other || ||
|  || Other || ||
|-
|-
| --cop2-regalloc || 0, 1 ? || PCSX2 seems to have this enabled by default. Uknown function, might be a speechack. ||
| --cop2-regalloc || 0, 1 ? || PCSX2 seems to have this enabled by default. ||
|-  
|-  
| --cop2-inst-q || 0, 1 || instant Q, no stalling on VWAITQ, or instances of Q. Crashes some games when enabled. ||
| --cop2-inst-q || 0, 1 || instant Q, no stalling on VWAITQ, or instances of Q. ||
|-  
|-  
| --cop2-inst-p || 0, 1 || instant P, no stalling on VWAITP, or instances of P. ||
| --cop2-inst-p || 0, 1 || instant P, no stalling on VWAITP, or instances of P. ||
Line 366: Line 373:
====Vector Units (VU)====
====Vector Units (VU)====
=====VU=====
=====VU=====
<pre>Custom DSPs used to process vertex data, physics calculations, and other related tasks. Settings found here affect VU1, VU0, and COP2. Most of these commands fix broken or missing geometry along with black screens.</pre>
<pre>Custom DSPs used to process vertex data, physics calculations, and other related tasks. Settings found here affect VU1 & VU0 & COP2</pre>
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
! Command !! Values !! Notes !! Usage  
! Command !! Values !! Notes !! Usage  
Line 374: Line 381:
| --vu-xgkick-delay  || Limit is between (0 => 31)  || Delay xgkick instruction execution. PCSX2 uses 6 cycles, PS3 uses 2-8 cycles depending on the game. Can be used to repair missing graphics with 0 being the most compatible. Useful for games with GIF issues || --vu-xgkick-delay=8
| --vu-xgkick-delay  || Limit is between (0 => 31)  || Delay xgkick instruction execution. PCSX2 uses 6 cycles, PS3 uses 2-8 cycles depending on the game. Can be used to repair missing graphics with 0 being the most compatible. Useful for games with GIF issues || --vu-xgkick-delay=8
|-
|-
| --vu-custom-min-max  || 0, 1 || Custom Max/Mini logic for denormals. Disabled on pcsx2 by default but enabled by default on a couple of emus such as jakv2. Disabling it could potentially restore missing graphics by speeding up the vector units.|| --vu-custom-min-max=0
| --vu-custom-min-max  || 0, 1 || Custom Max/Mini logic for denormals. Disabled on pcsx2 by default but enabled by default on a couple of emus such as jakv2. Disabling it could potentially restore missing graphics.|| --vu-custom-min-max=0
|-
|-
|-style="background-color:#D7EF54"
|-style="background-color:#D7EF54"
Line 421: Line 428:
|  || Speedhacks || ||
|  || Speedhacks || ||
|-
|-
| --vu1-mpg-cycles  || 0 - 400000 || Set initial speed for VU1 Micro-programs. 100 is the default value. If VU1 requirements were a bottleneck, increasing it will result in better performance while decreasing it will result in the opposite. Increasing it can be beneficial for MTVU sensitive games.|| --vu1-mpg-cycles=1000
| --vu1-mpg-cycles  || 0.1 - 20000|| Set initial speed for VU1 Micro-programs. Increasing it will result in better performance while decreasing it will do the opposite. Increasing it can be beneficial for games that are MTVU sensitive.|| --vu1-mpg-cycles=1000
|-
|-
| --vu1-di-bits || 0, 1 || 0 Skips setting invalid, and Divides by zero flags in status register. Can be used as a speedhack as it can skip costly calculations. But at the same time, it can cause issues such as broken geometry. || --vu1-di-bits=0
| --vu1-di-bits || 0, 1 || 0 Skips setting invalid, and Divides by zero flags in status register. Can be used as a speedhack as it can skip costly calculations. But at the same time, it can cause issues such as broken geometry. || --vu1-di-bits=0
Line 431: Line 438:
| --vu1-opt-vf00 || 0, 1, 2 || Optimization for the vf00 register. || --vu1-opt-vf00=2
| --vu1-opt-vf00 || 0, 1, 2 || Optimization for the vf00 register. || --vu1-opt-vf00=2
|-  
|-  
| --vu1-jr-cache-policy || newprog, sameprog, auto, new, same || PCSX2 uses newprog as default setting. Setting it into newprog has been proven to fix some crashes [https://github.com/PCSX2/pcsx2/blob/58f5a5b915915293b90e7e8f34c33f9c0424d1e8/pcsx2/x86/microVU_Misc.h#L319 Info] || --vu1-jr-cache-policy=newprog
| --vu1-jr-cache-policy || newprog, sameprog, auto, new, same || PCSX2 uses newprog as default setting.[https://github.com/PCSX2/pcsx2/blob/58f5a5b915915293b90e7e8f34c33f9c0424d1e8/pcsx2/x86/microVU_Misc.h#L319 Info] || --vu1-jr-cache-policy=sameprog
|-
|-
| --vu1-jalr-cache-policy || newprog, sameprog, auto, new, same || PCSX2 uses newprog as default setting. Setting it into newprog has been proven to fix some crashes [https://github.com/PCSX2/pcsx2/blob/58f5a5b915915293b90e7e8f34c33f9c0424d1e8/pcsx2/x86/microVU_Misc.h#L319 Info] || --vu1-jalr-cache-policy=newprog
| --vu1-jalr-cache-policy || newprog, sameprog, auto, new, same || PCSX2 uses newprog as default setting.[https://github.com/PCSX2/pcsx2/blob/58f5a5b915915293b90e7e8f34c33f9c0424d1e8/pcsx2/x86/microVU_Misc.h#L319 Info] || --vu1-jalr-cache-policy=sameprog
|-  
|-  
|-style="background-color:#D7EF54"
|-style="background-color:#D7EF54"
|  || Game fixes / Graphical fixes || ||
|  || Game fixes / Graphical fixes || ||
|-
|-
| --vu1 || jit-sync ||  Selector between IR/JIT and it modes. Jit-sync works similarly to disabling MTVU. jit, trans, and jit-async are unimplemented functions that do not change anything. || --vu1=jit-sync
| --vu1 || jit-sync,  jit, trans, jit-async ||  Selector between IR/JIT and it modes. Jit-sync works similarly to disabling MTVU. || --vu1=jit-sync
|-
|-
| --vu1-no-clamping ||  0,1 || Changes the clamping behavior of the VU1. Setting specific to ps4 emulators, unimplemented in pcsx2. The default emulator's behavior cannot be set by CLI commands. || --vu1-no-clamping=0
| --vu1-no-clamping ||  0,1 || Changes the clamping behavior of the VU1. Setting specific to ps4 emulators, unimplemented in pcsx2. The default emulator's behavior cannot be set by CLI commands. || --vu1-no-clamping=0
Line 467: Line 474:
| --vu1-inst-q || 0, 1 || instant Q, no stalling on WAITQ, or instances of Q.  || --vu1-inst-q=1  
| --vu1-inst-q || 0, 1 || instant Q, no stalling on WAITQ, or instances of Q.  || --vu1-inst-q=1  
|-  
|-  
| --assert-path1-ad || 0, 1 || Path 1 is how the GIF takes data from VU1 via XGKICK instruction. It's unknown what this command does but it's related to VU1, and helps prevent crashes in VU1 sensitive games when enabled. || --assert-path1-ad=1
| --assert-path1-ad || 0, 1 || Path 1 is how the GIF takes data from VU1 via XGKICK instruction. It's unknown what this command does but it's related to VU1 || --assert-path1-ad=1
|-  
|-  
|}
|}
Line 478: Line 485:
|  || Speedhacks || ||
|  || Speedhacks || ||
|-
|-
| --vu0-mpg-cycles || 0 - 400000 || Set initial cycle speed for VU0 Micro-programs. 100 is the default value. || --vu0-mpg-cycles=1000
| --vu0-mpg-cycles || 0.1 - 20000 || Set initial cycle speed for VU0 Micro-programs. || --vu0-mpg-cycles=1000
|-
|-
| --vu0-di-bits || 0, 1 || 0 to skip setting invalid, and Div by zero flags in status register. Can be used as speedhack as it skips costly calculations, but at the same time can cause issues like broken geometry, and weird physics behavior. Depending per game.|| --vu0-di-bits=0
| --vu0-di-bits || 0, 1 || 0 to skip setting invalid, and Div by zero flags in status register. Can be used as speedhack as it skips costly calculations, but at the same time can cause issues like broken geometry, and weird physics behavior. Depending per game.|| --vu0-di-bits=0
Line 523: Line 530:
====DMA Channels====
====DMA Channels====
=====VIF=====
=====VIF=====
<pre>The VIF decompresses vector data, uploads microprograms to the VUs, and sends graphical data to the GIF. Its commands
<pre>The VIF decompresses vector data, uploads microprograms to the VUs, and sends graphical data to the GIF.
are often used to fix freezing.</pre>
VIF CLI commands often fix freezing issues.</pre>
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
! Command !! Values !! Notes !! Usage
! Command !! Values !! Notes !! Usage
Line 532: Line 539:
| --vif-ignore-invalid-cmd || 0, 1 || Ignore invalid vif commands. In some cases, setting it to 1 can fix games that freeze while showing the same frame. || --vif-ignore-invalid-cmd=1
| --vif-ignore-invalid-cmd || 0, 1 || Ignore invalid vif commands. In some cases, setting it to 1 can fix games that freeze while showing the same frame. || --vif-ignore-invalid-cmd=1
|-
|-
| --vif-thread-chunk-size || 0, 1024 || Slows down both VIFS the lower it is, and speeds them up the higher it is. 1024 is the limit, with 112 being the default value.  ||  --vif-thread-chunk-size=100  
| --vif-thread-chunk-size || 1, 1000 || Unknown usage. 1024 is likely the limit.  ||  --vif-thread-chunk-size=100  
|-
|-
| --detect-idle-vif || 0, 1 || Enabled by default. Unknown function || --detect-idle-vif=0
| --detect-idle-vif || 0, 1 || Enabled by default. Unknown function || --detect-idle-vif=0
Line 540: Line 547:
| --vif1-ignore-cmd-ints || 0, 1 ||  Set to 1 to ignore command interrupt bit. ([https://psi-rockin.github.io/ps2tek/#vifcommands info] , explanation of int bit is right before command list). Can in some cases fix games that freeze while showing the same frame if set to 1. Games likes "Men in Black II - Alien Escape" and "Test Drive Unlimited" Will always need it. || --vif1-ignore-cmd-ints=1
| --vif1-ignore-cmd-ints || 0, 1 ||  Set to 1 to ignore command interrupt bit. ([https://psi-rockin.github.io/ps2tek/#vifcommands info] , explanation of int bit is right before command list). Can in some cases fix games that freeze while showing the same frame if set to 1. Games likes "Men in Black II - Alien Escape" and "Test Drive Unlimited" Will always need it. || --vif1-ignore-cmd-ints=1
|-
|-
| --vif1-instant-xfer ||  1 = Instant VIF1<br>0 = Delayed VIF1 || Changes VIF1 timing. 0 slows its timing and is the compatible option for most games, while 1 speeds up its timing, and being more compatible with a small fraction of games. It can be used to fix graphical glitches or potentially prevent games from freezing. || --vif1-instant-xfer=0
| --vif1-instant-xfer ||  1 = Instant VIF1<br>0 = Delayed VIF1 || Changes VIF1 timing. 0 is the accurate option. It can be used to fix graphical glitches or to potentially prevent games from freezing. || --vif1-instant-xfer=0
|}
|}


Line 550: Line 557:
|  ||  || SIF1 (IOP) ||
|  ||  || SIF1 (IOP) ||
|-
|-
| --iop-sif1-cycle-scalar || Accelerate SIF cycles: (0.99 => 0.1)<br>Decelerate SIF cycles: (1.1 => ∞ )|| Controls the speed at which the IOP receives from the EE || --iop-sif1-cycle-scalar=0.1
| --iop-sif1-cycle-scalar || Accelerate SIF cycles: (0.99 => 0.1)<br>Decelerate SIF cycles: (1.1 => ∞ )|| It controls how much data the IOP receives from the EE || --iop-sif1-cycle-scalar=0.1
|-
|-
| --ee-sif1-cycle-scalar ||Accelerate SIF cycles: (0.99 => 0.1)<br>Decelerate SIF cycles: (1.1 => ∞ )|| Controls the speed at which the EE sends to the IOP || --ee-sif1-cycle-scalar=0.1
| --ee-sif1-cycle-scalar ||Accelerate SIF cycles: (0.99 => 0.1)<br>Decelerate SIF cycles: (1.1 => ∞ )|| It controls how much data the EE sends to the IOP || --ee-sif1-cycle-scalar=0.1
|-style="background-color:#99ddff"
|-style="background-color:#99ddff"
|  ||  || SIF0 (EE) ||
|  ||  || SIF0 (EE) ||
|-
|-
| --iop-sif0-cycle-scalar || Accelerate SIF cycles: (0.99 => 0.1)<br>Decelerate SIF cycles: (1.1 => ∞ )|| Controls the speed at which the IOP sends to the EE || --iop-sif0-cycle-scalar=0.1
| --iop-sif0-cycle-scalar || Accelerate SIF cycles: (0.99 => 0.1)<br>Decelerate SIF cycles: (1.1 => ∞ )|| It controls how much data the IOP sends to the EE || --iop-sif0-cycle-scalar=0.1
|-
|-
| --ee-sif0-cycle-scalar || Accelerate SIF cycles: (0.99 => 0.1)<br>Decelerate SIF cycles: (1.1 => ∞ )|| Controls the speed at which the EE receives from the IOP || --ee-sif0-cycle-scalar=0.1
| --ee-sif0-cycle-scalar || Accelerate SIF cycles: (0.99 => 0.1)<br>Decelerate SIF cycles: (1.1 => ∞ )|| It controls how much data the EE receives from the IOP || --ee-sif0-cycle-scalar=0.1
|-
|-
|}
|}
Line 573: Line 580:
| --gs-adaptive-frameskip || 0, 1 || Speedhack. Skips frames when the gs demands more resources than there are available. doesn't work on all emulators.  It does however, work on jak emulators || --gs-adaptive-frameskip=1
| --gs-adaptive-frameskip || 0, 1 || Speedhack. Skips frames when the gs demands more resources than there are available. doesn't work on all emulators.  It does however, work on jak emulators || --gs-adaptive-frameskip=1
|-
|-
| --gs-h2l-list-opt || 0, 1 ||  Setting it to 1 improves GS performance||--gs-h2l-list-opt=1
|-style="background-color:#D7EF54"
|-
|  || Gs settings / Behaviour || ||
|-style="background-color:#cbddfb"
|  || GS features || ||
|-
|-
| --gs-use-mipmap || 0, 1 || Enables mipmapping support. Can be used to fix graphics. || --gs-use-mipmap=1
|-
| --gs-use-deferred-l2h || 0, 1 || Delay option for L2H (local to host, GS to EE). || --gs-use-deferred-l2h=1  
| --gs-use-deferred-l2h || 0, 1 || Delay option for L2H (local to host, GS to EE). || --gs-use-deferred-l2h=1  
|-
| --gs-use-clut-merge || 0, 1 ||Color lookup table(?). It could possibly solve graphical issues or improve the quality of the colors. || --gs-use-clut-merge=1
|-
| --gs-flush-ad-xyz || always, safe, safeZwrite, off, 0 || Force a primitive flush when a framebuffer is also an input texture. This fixes some processing effects, but it can sometimes be heavy on the GS in terms of performance. GTA: SA, and Jak 3 use this command. || --gs-flush-ad-xyz=safe
|-
|-style="background-color:#D7EF54"
|  || Gs settings / Behaviour || ||
|-
|-
| --gs-uprender || none,2x2 || Internal resolution upscaler. || --gs-uprender=2x2
| --gs-uprender || none,2x2 || Internal resolution upscaler. || --gs-uprender=2x2
Line 593: Line 589:
| --gs-upscale || none, gpu, edgesmooth, smooth, motion, motionvec, motionvector, point || Upscaling type Selector || --gs-upscale=EdgeSmooth
| --gs-upscale || none, gpu, edgesmooth, smooth, motion, motionvec, motionvector, point || Upscaling type Selector || --gs-upscale=EdgeSmooth
|-  
|-  
| --gs-kernel-cl-up || "DarkCloud2" "fantavision" "h2lpool2x2", "OptRightTri", "clutmerge2x2", "mipmap2x2", "up2x2simple", "up2x2skipinterp", "up2x2tc", "up2x2", default || Kernel Variant Color lookup Upscaler (?), mipmap and clutmerge and h2l need to be enabled before their options become usable|| --gs-kernel-cl-up="clutmerge2x2"
| --gs-kernel-cl-up || "DarkCloud2" "fantavision" "h2lpool2x2", "OptRightTri", "clutmerge2x2", "mipmap2x2", "up2x2simple", "up2x2skipinterp", "up2x2tc", "up2x2", default || Kernel Variant Color lookup Upscaler (?), Mipmap and clutmerge and h2l will have to be enabled first before using their options|| --gs-kernel-cl-up="clutmerge2x2"
|-  
|-  
| --gs-override-small-tri-area || 0, 1 || Small triangle rejection. Could potentially restore missing text in some games. || --gs-override-small-tri-area=1
| --gs-override-small-tri-area || 0, 1 || Small triangle rejection. Could potentially restore missing text in some games. || --gs-override-small-tri-area=1
Line 601: Line 597:
| --gs-ignore-dirty-page-border || 0, 1 || ? ||--gs-ignore-dirty-page-border=1
| --gs-ignore-dirty-page-border || 0, 1 || ? ||--gs-ignore-dirty-page-border=1
|-  
|-  
| --gs-ignore-rect-correction || 0, 1 || Setting it to 1 is known to fix graphical glitches occurring in far distances || --gs-ignore-rect-correction=1
| --gs-ignore-rect-correction || 0, 1 || || --gs-ignore-rect-correction=1
|-
|-
| --gs-opt-frbuff-switch || 0, 1 ||  || --gs-opt-frbuff-switch=0
| --gs-opt-frbuff-switch || 0, 1 ||  || --gs-opt-frbuff-switch=0
|-
|-
| --gs-kernel-cl || h2lpool, clutmerge, mipmap, DarkCloud2, fantavision, Mipmap and clutmerge and h2l need to be enabled before their options become usable ||Kernel Variant Color lookup(?). Options included here can be upscaling if --gs-kernel-cl-up were to be used along with it || --gs-kernel-cl="clutmerge"
| --gs-kernel-cl || h2lpool, clutmerge, mipmap, DarkCloud2, fantavision, Mipmap and clutmerge and h2l will have to be enabled first before using their options ||Kernel Variant Color lookup(?). Options included here can be upscaling if --gs-kernel-cl-up were to be used along with it || --gs-kernel-cl="clutmerge"
|-  
|-  
| --force-frame-blend || 0, 1 || Enables blend (Deinterlacing?). Should be used to fix games with shaking screens. || --force-frame-blend=1
| --force-frame-blend || 0, 1 || Enables blend (Deinterlacing?). Should be used to fix games with shaking screens. || --force-frame-blend=1
Line 611: Line 607:
| --force-pal-60hz || 0, 1 || Enables 60hz PAL mode. || --force-pal-60hz=1
| --force-pal-60hz || 0, 1 || Enables 60hz PAL mode. || --force-pal-60hz=1
|-
|-
| --gs-progressive || 0, 1 || Enables progressive scan. It's used to fix graphical glitches/double screen issues.  ||
| --gs-use-clut-merge || 0, 1 ||Color lookup table(?). It could possibly solve graphical issues or improve the quality of the colors. || --gs-use-clut-merge=1
|-
| --gs-use-mipmap || 0, 1 || Enables Mipmapping support. Can be used to fix graphics. || --gs-use-mipmap=1
|-
| --gs-progressive || 0, 1 || Enables progressive scan. It's used to fix Graphical glitches/double screen issues.  ||
|-  
|-  
| --gs-vert-precision || 8, 16 || 3D rendering vertex precision. The emu expects the values of 8 or 16, any other values are not permitted. || --gs-vert-precision=8
| --gs-vert-precision || 8, 16 || 3D Rendering vertex precision. The emu expects the values of 8 or 16. Any other values are not permitted. || --gs-vert-precision=8
|-
|-
| --gs-force-bilinear || 0, 1 || Forces bilinear filtering, can fix ghosting problems in some cases. Not recommended for games that use 2D images, as it could possibly break games that rely on nearest filtering.|| --gs-force-bilinear=1
| --gs-force-bilinear || 0, 1 || Forces bilinear filtering. Can fix ghosting problems in some cases. But despite this, it's not recommended for games that use 2D images. Can break games which use nearest filtering on purpose.|| --gs-force-bilinear=1
|-
|-
| --gs-skip-dirty-flush-on-mipmap || 0, 1 || Skip flushing textures marked as dirty from cache when enabled. It does, however, require mipmap to be enabled first. || --gs-skip-dirty-flush-on-mipmap=1
| --gs-skip-dirty-flush-on-mipmap || 0, 1 || Skip flushing textures marked as dirty from cache when enabled. It does, however, require mipmap to be enabled first. || --gs-skip-dirty-flush-on-mipmap=1
Line 636: Line 636:
|-
|-
| --gs-scanout-delay || 0, 200 ||  || --gs-scanout-delay=200
| --gs-scanout-delay || 0, 200 ||  || --gs-scanout-delay=200
|-
| --gs-flush-ad-xyz || always, safe, safeZwrite, off, 0 || Force a primitive flush when a framebuffer is also an input texture. This fixes some processing effects, but it can sometimes be heavy on the GS in terms of performance. GTA: SA, and Jak 3 use this command. || --gs-flush-ad-xyz=safe
|-
|-
| --gs-check-trans-rejection || 0, 1  || Check transfer rejection ? || --gs-check-trans-rejection=1
| --gs-check-trans-rejection || 0, 1  || Check transfer rejection ? || --gs-check-trans-rejection=1
Line 644: Line 646:
|-
|-
| --gs-h2l-accurate-hash || 0, 1 ||  ||--gs-h2l-accurate-hash=1
| --gs-h2l-accurate-hash || 0, 1 ||  ||--gs-h2l-accurate-hash=1
|-
| --gs-h2l-list-opt || 0, 1 ||  ||--gs-h2l-list-opt=1
|-
|-
|-style="background-color:#9042f5"
|-style="background-color:#9042f5"
Line 663: Line 667:


====IOP====
====IOP====
<pre>The emulated I/O Processor (IOP) settings. Commands here are rarely useful, as very few games will require them. The IOP controls the emulated DEV9, SPU2, USB, Memory cards, CDVD, Firewire, along with other input/output devices</pre>
<pre>The emulated I/O Processor (IOP) settings. Commands here are rarely useful; very few games will require these options. The IOP controls the emulated DEV9, SPU2, USB, Memory cards, CDVD, Firewire, along with other input/output Devices</pre>
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
! Command !! Values !! Notes !! Usage  
! Command !! Values !! Notes !! Usage  
Line 677: Line 681:
| --iop-hook || AdvanceClock, FastForwardClock || IOP native hook, Sony uses it on their official release of Red dead revolver || --iop-hook=0x0086ac,FastForwardClock
| --iop-hook || AdvanceClock, FastForwardClock || IOP native hook, Sony uses it on their official release of Red dead revolver || --iop-hook=0x0086ac,FastForwardClock
|-
|-
| --iop-block-validation || IsC, ShortHash, Hash || Way of validating that block been modified, and require recompilation. Other Possible values include PageProt, None, PageProtection || --iop-block-validation=IsC
| --iop-block-validation || IsC, ShortHash, Hash || Way of validating that block been modified, and require recompilation, other Possible values include PageProt, None, PageProtection || --iop-block-validation=IsC
|-
|-
|-style="background-color:#FEA15C"
|-style="background-color:#FEA15C"
Line 710: Line 714:
| --pcr0-delta-hack || 0.1 , 400000.0 || Modify delta of pcr0 when reading it from MFC0. Some games rely on good performance counters accuracy (Spyro ANB cutscenes), and since emulator don't implement most events, hack it is. || --pcr0-delta-hack=1.0
| --pcr0-delta-hack || 0.1 , 400000.0 || Modify delta of pcr0 when reading it from MFC0. Some games rely on good performance counters accuracy (Spyro ANB cutscenes), and since emulator don't implement most events, hack it is. || --pcr0-delta-hack=1.0
|-
|-
| --jitproc-use-aslr || || Disables compiler process ASLR, useful for easier debugging, as the compiler process will be always on fixed address. Theoretically useful for mast1c0re, but to change it you need to be already in... || --jitproc-use-aslr=0
| --jitproc-use-aslr || || Disable compiler process ASLR, useful when you want easier debugging, compiler process will be always on fixed address. Theoretically useful for mast1c0re, but to change it you need to be already in... || --jitproc-use-aslr=0
|-
|-
| --detect-idle-intc ||0, 1|| Enabled by default, 0 disables it || --detect-idle-intc=0
| --detect-idle-intc ||0, 1|| enabled by default, set to 0 in order to disable it || --detect-idle-intc=0
|-
|-
| --detect-idle-chcr|| 0, 1|| Enabled by default, 0 disables it || --detect-idle-chcr=0
| --detect-idle-chcr|| 0, 1|| enabled by default, set to 0 in order to disable it || --detect-idle-chcr=0
|-
|-
| --rom || location of the bios that's inside of the fpkg || Could allow to use custom bios, though still not working || --rom="PS20220WD20050620.crack" or --rom="/roms/PS20220WD20050620.crack"
| --rom || location of the bios that's inside of the fpkg || Could allow to use custom bios, though still not working || --rom="PS20220WD20050620.crack" or --rom="/roms/PS20220WD20050620.crack"
Line 727: Line 731:


====PCSX2's gameindex====
====PCSX2's gameindex====
<pre>PCSX2's commands on the PS4</pre>
<pre>PCSX2's equivalent commands on the PS4</pre>


<br>[https://raw.githubusercontent.com/PCSX2/pcsx2/master/bin/resources/GameIndex.yaml Current Gameindex.yaml]
<br>[https://raw.githubusercontent.com/PCSX2/pcsx2/master/bin/resources/GameIndex.yaml Current Gameindex.yaml]
<br>[https://github.com/Scalerize/Pcsx2-gameindexes Old Gameindex.yaml files]
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
! {{cellcolors|#00d6f2|#000000}}PCSX2 !! {{cellcolors|#c300ff|#000000}}PS4 !! Notes
! {{cellcolors|#00d6f2|#000000}}PCSX2 !! {{cellcolors|#c300ff|#000000}}PS4 !! Notes
Line 760: Line 765:
| MTVUSpeedHack: 0 || --vu1=jit-sync || Some games will also require --vu1-mpg-cycles= to be between "6000 - 19000"
| MTVUSpeedHack: 0 || --vu1=jit-sync || Some games will also require --vu1-mpg-cycles= to be between "6000 - 19000"
|-
|-
| mergeSprite<br>alignSprite || --gs-kernel-cl-up="up2x2simple" || Note: works similarly but not the equivalent
| mergeSprite<br>alignSprite || --gs-kernel-cl-up="up2x2simple" || Note: Works very similar but not the equivalent
|-
|-
| cpuSpriteRenderBW: 4 || --gs-opt-frbuff-switch=1 || Note: works similarly but not the equivalent
| cpuSpriteRenderBW: 4 || --gs-opt-frbuff-switch=1 || Note: Works very similar to it, but it's not exactly the same
|-
|-
| mipmap || --gs-use-mipmap=1  ||
| mipmap || --gs-use-mipmap=1  ||
Line 768: Line 773:
| autoFlush || --gs-flush-ad-xyz=safe || Possible values include always, safe, off, 0
| autoFlush || --gs-flush-ad-xyz=safe || Possible values include always, safe, off, 0
|-
|-
| VIF1StallHack || --vif1-instant-xfer=0 ||  If that doesn't work, the lua command eeObj.SchedulerDelayEvent("vif1.dma", 0x9000) might assist.
| VIF1StallHack || --vif1-instant-xfer=0 ||  if that doesn't work you can always use the lua command eeObj.SchedulerDelayEvent("vif1.dma", 0x9000)
|-
|-
| wildArmsHack || --gs-kernel-cl-up="DarkCloud2" ||
| wildArmsHack || --gs-kernel-cl-up="DarkCloud2" ||
Line 782: Line 787:
|  || 2018 || ||
|  || 2018 || ||
|-
|-
| The King of Fighters '98: Ultimate Match || The only known emulator where '''Mojin-ribbon''' is playable. Commonly known as "KOF98"|| 2.0 ||
| The King of Fighters '98: Ultimate Match || The only known emulator that managed to fix '''Mojin-ribbon'''. Commonly referred to as "KOF98"|| 2.0 ||
|-
|-
|-style="background-color:#D7EF54"
|-style="background-color:#D7EF54"
|  || 2017 || ||
|  || 2017 || ||
|-
|-
| Jak and Daxter: The Precursor Legacy || Good compatibility with most ps2 games. It has a very high api version which means more LUA commands are supported. In addition, Jak emus are one of the few emus that can use the '''--gs-adaptive-frameskip=1''' command. It is often referred to as "Jak v2"|| 2.2 || '''JakX,''' '''Jak 2,''' '''Jak 3,'''  
| Jak and Daxter: The Precursor Legacy || Good compatibility with most ps2 games. It has a very high api version which means more LUA commands are supported. Jak emus are one of the few emus that can use the '''--gs-adaptive-frameskip=1''' command. Often referred to as "Jak v2"|| 2.2 || '''JakX,''' '''Jak 2,''' '''Jak 3,'''  
|-
|-
| Art of Fighting Anthology || Similar to RECVX. It was successful in fixing "'''Coraline'''." Sometimes called "AOFA" || 2.0 ||
| Art of Fighting Anthology || It is programmed in a similar fashion to RECVX and was successful in fixing "Coraline." Often referred to as "AOFA" || 2.0 ||
|-
|-
| Resident Evil – Code: Veronica || Fixes games like '''Jackie chan Adventures, SpongeBob SquarePants: Creature From the Krust Krab, Pac-man World 3, Yu-Gi-Oh: Capsule monsters, SpongeBob's Atlantis SquarePantis''' freezing at a black/splash screen. Additionally, it fixes many games requiring '''OPL's mode 2'''. Often referred to as "RECVX" || 1.7 || '''Fatal Fury,''' '''Redfaction,''' '''AOFA.'''
| Resident Evil – Code: Veronica || Fixes Games like '''Jackie chan Adventures, Pac-man World 3, Yu-Gi-Oh: Capsule monsters, SpongeBob's Atlantis SquarePantis''' freezing at the splash screen. Often referred to as "RECVX" || 1.7 || '''Fatal Fury,''' '''Redfaction,''' '''AOFA.'''
|-
|-
| Fatal Fury Battle Archives: Volume 2 || The emulator with the closest VU0-EE sync on the PS4; setting eecyclescalar to 5 on this emulator will enable some VU0 sync demanding games to run on the PS4. ||  ||  
| Fatal Fury Battle Archives: Volume 2 || The emulator with the closest VU0-EE sync on the PS4; setting eecyclescalar to 5 on this emulator will enable some VU0 sync demanding games to run on the PS4. ||  ||  
Line 801: Line 806:
| Forbidden Siren || The only emulator that was able fix '''Ice age 2''' being stuck at splash screen by using it in conjunction with patches. It also fixed '''Gran turismo 4''' running EXTREMELY slow. || 0.1 ||
| Forbidden Siren || The only emulator that was able fix '''Ice age 2''' being stuck at splash screen by using it in conjunction with patches. It also fixed '''Gran turismo 4''' running EXTREMELY slow. || 0.1 ||
|-
|-
| King of Fighters 2000 || Seemingly the emulator with closest VU0-EE sync on the PS4. Fixes graphical issues and sps in games such as '''Crash Twinsanity''', '''Rayman 3''', '''Crazy Frog Racer''', and '''prevents Koei tecmo games from suddenly freezing when battle starts. Likely the only emulator where '''Batman Begins''' does not crash.''' Often referred to as "KOF2000"|| 1.2 || '''Roguev1''', '''KOF98''', '''Okage'''
| King of fighters 2000 || Fixes graphical issues and sps in games such as '''Crash Twinsanity''', '''Rayman 3''', '''Crazy Frog Racer''', and '''prevents Koei tecmo games from suddenly freezing when battle starts, and it is likely the only emulator where '''Batman Begins''' does not crash.''' Often referred to as "KOF2000"|| 1.2 || '''Roguev1''', '''KOF98''', '''Okage'''
|-
|-
| Destroy All Humans! || Fixed '''Tenchu: Fatal Shadows''' crashing. || 0.1 ||  
| Destroy All Humans! || Fixed '''Tenchu: Fatal Shadows''' in conjunction with patches. || 0.1 ||  
|-
|-
| Destroy All Humans! 2 ||  || 0.7 ||  
| Destroy All Humans! 2 ||  || 0.7 ||  
Line 812: Line 817:
|  || 2015 || ||
|  || 2015 || ||
|-
|-
|War of the monsters v1 || The emulator that's used in PS2CLASSICSGUI, and the best one around for GS/GIF accuracy. || 0.1 || '''Rogue v1 and v2, Arc the Lad, Star Wars Jedi Starfighter'''
|War of the monsters v1 || The emulator that's used in ps2classicsgui and the best one around for GS accuracy. || 0.1 || '''Rogue v1 and v2, Arc the Lad, Star Wars Jedi Starfighter'''
|-
|-
| GTA 3 || Fixed the pal version of '''Genji: Dawn of the Samurai''' || 0.6 ||
| GTA 3 || Fixed the pal Version of '''Genji: Dawn of the Samurai''' || 0.6 ||
|-
|-
| Parappa 2 || The only emulator that was able to boot '''Spyro: A Hero's Tail''' || 0.1 ||
| Parappa 2 || The only emulator that was able to boot '''Spyro: A Hero's Tail''' || 0.1 ||
Line 831: Line 836:
Require cleanup.
Require cleanup.
====ApiRequest====
====ApiRequest====
<pre>The most important part of the lua. The lua will crash the game if it were used without it. </pre>
<pre>The most important part of the lua. The lua will crash the game if it was used without it. </pre>
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
! Command !! Usage !! Notes
! Command !! Usage !! Notes
Line 914: Line 919:
|ThrottleFast || emuObj.ThrottleFast() || Faster than default, but exact value is unknown.
|ThrottleFast || emuObj.ThrottleFast() || Faster than default, but exact value is unknown.
|-
|-
|ThrottleMax || emuObj.ThrottleMax() || Disable framelimiter during loading screens.  
|ThrottleMax || emuObj.ThrottleMax() || Disable framelimiter During loading screens.  
|-style="background-color:#ffe680"
|-style="background-color:#ffe680"
|  || CDVD ||  
|  || CDVD ||  
Line 996: Line 1,001:
18 - english-uk</pre></div>
18 - english-uk</pre></div>
|-
|-
|PadSetLightBar || emuObj.PadSetLightBar(<port, red, green, blue>) || Set DS4 light bar color. The correct port values are 0-3, correct light values are 0-255.
|PadSetLightBar || emuObj.PadSetLightBar(<port, red, green, blue>) || Set DS4 light bar color. Correct port values are 0-3, correct light values are 0-255.
|-
|-
|PadPressureStickRemap || emuObj.PadPressureStickRemap()||
|PadPressureStickRemap || emuObj.PadPressureStickRemap()||
Line 1,294: Line 1,299:
|forcePoint|| emuObj.SetGsTitleFix( "forcePoint", "reserved", {mipIsGt=0,  mmin=0} ) ||
|forcePoint|| emuObj.SetGsTitleFix( "forcePoint", "reserved", {mipIsGt=0,  mmin=0} ) ||
|-
|-
|forceSimpleFetch ||  emuObj.SetGsTitleFix( "forceSimpleFetch",  "reserved", {psm=0} ) ||Used frequently to fix graphical corruptions
|forceSimpleFetch ||  emuObj.SetGsTitleFix( "forceSimpleFetch",  "reserved", {psm=0} ) ||Used frequently to fix Graphical corruptions
|-
|-
|forcePointSampling|| emuObj.SetGsTitleFix( "forcePointSampling", "reserved", {alpha = 0x80000048, twIsLess=5, thIsLess=5 } ) ||
|forcePointSampling|| emuObj.SetGsTitleFix( "forcePointSampling", "reserved", {alpha = 0x80000048, twIsLess=5, thIsLess=5 } ) ||
Line 1,526: Line 1,531:
| AdvanceClock || iopObj.AdvanceClock() ||
| AdvanceClock || iopObj.AdvanceClock() ||
|-
|-
| GetClock || iopObj.GetClock() || Returns the value of cycles the iop is ahead of (?)
| GetClock || iopObj.GetClock() || Returns the value of how many cycles the iop is ahead of normal clock (?)
|-style="background-color:#c6ecd9"
|-style="background-color:#c6ecd9"
|  || Hooks ||
|  || Hooks ||
Line 1,744: Line 1,749:
</pre>
</pre>


</pre>
'''GetCPR0/SetCPR0
'''GetCPR0/SetCPR0
'''
'''
Line 1,852: Line 1,858:
===EE-IOP===
===EE-IOP===
<pre>This list of registers is yet to be completed. Some registers are incorrectly named or include incorrect offsets. 0x1000000xxx base is not guaranteed in different emu revisions, but layout should be the same regardless.
<pre>This list of registers is yet to be completed. Some registers are incorrectly named or include incorrect offsets. 0x1000000xxx base is not guaranteed in different emu revisions, but layout should be the same regardless.
Assuming base is different (Like on kof2000), simply reduce these offsets by 8 hex values
Assuming base is different (Like on kof2000), simply reduce these offsets by 8 hex values.
(IOP, VU0, and VU1 registers' offsets are static in all emulators).
Regardless, this should not affect the IOP, VU0, or VU1 registers.
</pre>
</pre>
<pre> List was designed for Jak v2
<pre> List was designed for Jak v2
Line 1,952: Line 1,958:
===Emulator related regs===
===Emulator related regs===
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
! {{cellcolors|#7698FF|#000000}}"Fake" registers !! Address !! Notes   
! {{cellcolors|#7698FF|#000000}}"Fake" register !! Address !! Notes   
|-
|-
| (?) || 0x1000000360      || Locking the value seems to cause a crash.
| (?) || 0x1000000360      || Locking the value seems to cause a crash.
|-style="background-color:#8b9dc3"
|-style="background-color:#8b9dc3"
|Current PC<br>(4 Bytes) || 0x1000000368 || Shows the current offset that's being executed by the EE.<br>
|Current PC<br>(4 Bytes) || 0x1000000368 || Shows the current offset that's being executed by the EE.<br>
Updated only on branch/jump tests, unless commands such as --ee-pc-coherency  or --ee-insn-flush-pc are used.<br>
Updated only on branch/jump tests, unless command such as --ee-pc-coherency  or --ee-insn-flush-pc is used.<br>
Then updates are instant, right when instructions are executed. <br>
Then updates are instant, right when instruction is executed. <br>
Commonly used by sceners as a way of finding troublesome offsets. Can be found in some emulators here too: 0x8000016830
Commonly used by Sceners as a tool for finding troublesome offsets.
|-
|-
| (?) || 0x100000036C ||
| (?) || 0x100000036C ||
Line 1,980: Line 1,986:
|}
|}


===VU0 Registers===
---------------------------------------------------------------------------------------------------------------------------------
 
===VU0f-VU0i===
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| class=wikitable style="border: none; background: none;"
{| class=wikitable style="border: none; background: none;"
Line 2,072: Line 2,080:
|-
|-
|}
|}
===VU1 Registers===
 
---------------------------------------------------------------------------------------------------------------------------------
 
===VU1f-VU1i===
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: center;"
{| class=wikitable style="border: none; background: none;"
{| class=wikitable style="border: none; background: none;"
Line 2,378: Line 2,389:
! Issue !! Games affected !! Solution !! Description
! Issue !! Games affected !! Solution !! Description
|-
|-
| Inaccurate GIF timing || The Matrix: Path of Neo, Tenchu - Fatal Shadows, Genji dawn of the samurai, Batman begins, Dragon ball z budokai tenkaichi 1, possibly many more! || LUA patches or hooking schedulerdelayevent on a troublesome offset ||
| IOP emulation inaccuracy(?) || Zatch Bell! Mamodo Fury, Godfather, Gran turismo 4, SSX  || || a Stutter that's not caused by performance but by inaccurate iop emulation leading to stuttering fmvs/mainmenu
|-
| GS texture cache inaccuracy(?) || Taz Wanted, Ratchet And Clank Up Your Arsenal  || || Some textures being missing or miscoloured.
|-
| GIF timing is inaccurate || The Matrix: Path of Neo, Tenchu - Fatal Shadows, Genji dawn of the samurai, Batman begins, Dragon ball z budokai tenkaichi 1, possibly many more! || LUA patches or hooking schedulerdelayevent on a troublesome offset ||
|-
|-
| No support for EE Cache || Ice Age 2, DOA2: Extreme, Nascar 2009, Barnyard, [https://github.com/PCSX2/pcsx2/issues/2248 Others]|| Lua patches to the EE memory and picking the right emulator || It's not a ps4 issue per say since these issues are also encountered by Pcsx2. but Pcsx2 does have support for EE cache, though it doesn't use it to fix these games because emulating EE cache is extremely slow. so that's why the Pcsx2 team decided to use pnach patches to fix this issue.
| No support for EE Cache || Ice Age 2, DOA2: Extreme, Nascar 2009, Barnyard, [https://github.com/PCSX2/pcsx2/issues/2248 Others]|| Lua patches to the EE memory and picking the right emulator || It's not a ps4 issue per say since these issues are also encountered by Pcsx2. but Pcsx2 does have support for EE cache, though it doesn't use it to fix these games because emulating EE cache is extremely slow. so that's why the Pcsx2 team decided to use pnach patches to fix this issue.
|-
|-
| Missing COP2 pipeline emulation. ||  [https://github.com/PCSX2/pcsx2/issues/4439 other games affected by COP2 timing]  || Rearranging code through lua patches. || While COP2 is part of EE, in terms of emulation it's separate processor that can run on its own. So some operations take some time while EE still mind own business. Some games abuse that fact and do own thing knowing that COP2 calculation take expected number of cycles. On this emu every COP2 opcode is instant, which break games that expect it to take some time.
| Missing COP2 pipeline emulation. ||  [https://github.com/PCSX2/pcsx2/issues/4439 other games affected by COP2 timing]  || Rearranging code by lua patches. || While COP2 is part of EE, in terms of emulation it's separate processor that can run on its own. So some operations take some time while EE still mind own business. Some games abuse that fact and do own thing knowing that COP2 calculation take expected number of cycles. On this emu every COP2 opcode is instant, which break games that expect it to take some time.
|-
|-
| VU0 is not running in sync with EE core || 24 The Game, ATV Quad Power Racing 2, Ghosthunter, Rayman Arena, Rayman 3, Largo winch, Ratchet and clank games. All games using M-bit. || EE hook AdvanceClock or fastforwardclock commands on affected addresses to push VU0 ahead while stalling EE, patches to rearrange code. Most of the time it will be CTC2/QMTC2 instructions with interlock that are affected. || Emulator kickstart VU0 for 256 cycles, while report 512 cycles passed. Yup, we are out of sync right from the start of VU0 mpg because people working for $ony don't know that VU0 run at EE MHz, not at EE bus MHz. Not to mention that 256 cycles kickstart is too much even on correct speed. Later things just got worse. This issue can be partially replicated on Pcsx2 if you overclock the EE by +3
| VU0 is not running in sync with EE core || 24 The Game, ATV Quad Power Racing 2, Ghosthunter, Rayman Arena, Rayman 3, Largo winch, Ratchet and clank games. All games using M-bit. || EE hook AdvanceClock or fastforwardclock commands on affected addresses to push VU0 ahead while stalling EE, patches to rearrange code. Most of the time it will be CTC2/QMTC2 instructions with interlock that are affected. || Emulator kickstart VU0 for 256 cycles, while report 512 cycles passed. Yup, we are out of sync right from the start of VU0 mpg because people working for $ony don't know that VU0 run at EE MHz, not at EE bus MHz. Not to mention that 256 cycles kickstart is too much even on correct speed. Later things just got worse. This issue can be partially replicated on Pcsx2 if you overclock the EE by +3
Line 2,393: Line 2,408:
| Wrong disc read speed for some games || Shadowman(Textures), God of war (Music), Ratchet and clank size matters (Music), every game that's listed to require CDVD_READ_DELAY. [https://github.com/PCSX2/pcsx2/pull/3877 and many other affected games] || Try your luck with IOP and CDVD CLI commands. || Also known in sony's bios as CDVD_READ_DELAY
| Wrong disc read speed for some games || Shadowman(Textures), God of war (Music), Ratchet and clank size matters (Music), every game that's listed to require CDVD_READ_DELAY. [https://github.com/PCSX2/pcsx2/pull/3877 and many other affected games] || Try your luck with IOP and CDVD CLI commands. || Also known in sony's bios as CDVD_READ_DELAY
|-
|-
| Inaccurate VU0/VU1/COP2 emulation || Sly cooper games, Crash twinsanity, Crazy frog racer, Rayman 3, Klonoa 2, others.  || Choosing a VU accurate emulator such as Roguev1 or Kof2000 with the right clamping commands || The issue leads to SPS and graphical issues and sometimes freezing.
| In-accurate VU0/VU1/COP2 emulation || Sly cooper games, Crash twinsanity, Crazy frog racer, Rayman 3, Klonoa 2, others.  || Choosing a VU accurate emulator such as Roguev1 or Kof2000 with the right clamping commands || The issue leads to SPS and graphical issues and sometimes freezing.
|-
|-
| Multitap doesn't support all games || Urban reign, others || Lua patches || Emulator expect PS4 to be able to use 8 controllers (well, who doesn't? Even PS1 can do it...). That cause all kind of mess with controller detection when game expect multitap in second port.
| Multitap doesn't support all games || Urban reign, others || Lua patches || Emulator expect PS4 to be able to use 8 controllers (well, who doesn't? Even PS1 can do it...). That cause all kind of mess with controller detection when game expect multitap in second port.
Line 2,401: Line 2,416:
|VIF1 runs too fast || Urban reign, Avatar, Parappa 2, Eternal Poison, Soul Calibur 2, Soul Calibur 3, Others  || Using LUA's SchedulerDelayEvent command or Using CLI'S vif1-instant-xfer command || Sony wanted to improve the performance, which is the reason VIF1 is instant. The lua's command can be customizable to set the delay period, the cli can't, therefore lua's command is much more compatible
|VIF1 runs too fast || Urban reign, Avatar, Parappa 2, Eternal Poison, Soul Calibur 2, Soul Calibur 3, Others  || Using LUA's SchedulerDelayEvent command or Using CLI'S vif1-instant-xfer command || Sony wanted to improve the performance, which is the reason VIF1 is instant. The lua's command can be customizable to set the delay period, the cli can't, therefore lua's command is much more compatible
|-
|-
|Reading VU TPC registers returns wrong values || Street Fighter 3 EX(VU0), R: Racing Revolution(VU0), Spiderman 3 (VU0, in T-Bit handler...), Edge of Reality games(VU1) || Patches in lua. || In this emu TPC stores full addresses, which is wrong. Real hardware keep there addr >> 3. Worth noting that EoR games read VU1 TPC in a nasty way, accessing 0x43A0(VU1 TPC) from COP2 code.
|Reading VU TPC registers return wrong value|| Street Fighter 3 EX(VU0), R: Racing Revolution(VU0), Spiderman 3 (VU0, in T-Bit handler...), Edge of Reality games(VU1) || Patches in lua. || In this emu TPC store full address which is wrong. Real hardware keep there addr >> 3. Worth to note that EoR games read VU1 TPC in nasty way, accessing 0x43A0(VU1 TPC) from COP2 code.
|-
|-
|VIF command interrupts handled before VIFn_CODE is updated. || Onimusha Blade Warriors ||  Fixed by patch in intr handler. || This is very specific case because Onimusha check VIFn_CODE register in interrupt handler and do nothing if code is not 0x80 (NOP with I). But VIFn_CODE seems to be updated after interrupt is handled. This practically makes everything out of sync later as interrupts are happening, but handler does nothing about them.
|VIF command interrupts handled before VIFn_CODE is updated. || Onimusha Blade Warriors ||  Fixed by patch in intr handler. || This is very specific case because Onimusha check VIFn_CODE register in interrupt handler and do nothing if code is not 0x80 (NOP with I). But VIFn_CODE seems to be updated after interrupt is handled. This practically make everything out of sync later as interrupts are happening, but handler do nothing about them.
|-
|-
| IPU emulation inaccuracy || Burnout 3, Tony Hawk's Underground, Onimusha Dawn of Dreams || ? ||  
| IPU emulation inaccuracy || Burnout 3 || None yet ||  
|-
|-
| CDVD register 0x1F402038 (KeysValid) return wrong result. || Every "SCCS" game || Patches in lua. || Likely specific to NTSC-C releases, because that region uses special SDK. This issue makes cdvdman become stuck on any request because it thinks that the cdvd key is invalid.
| CDVD register 0x1F402038 (KeysValid) return wrong result. || Every "SCCS" game || Patches in lua. || Likely specific to NTSC-C releases, because that region use special SDK. Issue make cdvdman stuck on any request because it thinks that cdvd key is invalid.
|-
|-
| Lack of CDVD error handling || Demon Chaos, Spyro A new Beginning, Silent Hill 2 Black Ribbon, games from pcsx2 #5174 PR. || Patches in lua if needed. || One correctly supported error is SCECdErABRT, rest is just not handled or what's worst trigger emu panic on purpose like SCECdErILI (but not for 0 sector request - Spyro). Some affected games can still work if error is just accidental and not checked by game code.  
| Lack of CDVD error handling || Demon Chaos, Spyro A new Beginning, Silent Hill 2 Black Ribbon, games from pcsx2 #5174 PR. || Patches in lua if needed. || One correctly supported error is SCECdErABRT, rest is just not handled or what's worst trigger emu panic on purpose like SCECdErILI (but not for 0 sector request - Spyro). Some affected games can still work if error is just accidental and not checked by game code.  
|-
| Corrupted SIF0 transfer when not full QW is send by IOP || True Crime: LA, PDC DC 2008, Street Racing Syndicate(1.03) || Patches in lua. || IOP is able to send words by SIF0, EE DMAC can only transfer Quadwords. When IOP send not full QW real hardware use whatever was in buffer from previous transfer for missing words (only words that are requested by iop are overwritten in transfer buffer). Emu probably memset 0 that part.
|-
|}
|}


Line 2,419: Line 2,431:
==Description==
==Description==


The PS2 bios is the file '''PS20220WD20050620.crack''' included in every PS2 game .pkg. It is the same BIOS used by Sony in PS3's ps2_netemu.self. The lack of many X modules here means that homebrew compatibility is limited, as many of those need to be recompiled to use non X versions of modules, or need to load open source versions of them through MC/CDVD. An important non X module that is missing is LIBSD, therefore, homebrews that require it will likely fail to boot, or cause an error.
The PS2 bios is the file '''PS20220WD20050620.crack''' included in every PS2 game .pkg. It Is '''exactly''' the same BIOS that Sony used in ps2_netemu.self in PS3. Due to lack of many X modules, homebrew compatibility is limited, and many of those need to be recompiled to use non X versions of modules, or need to load open source versions of them through MC/CDVD. Important non X module that is missing is LIBSD, and homebrew that need it, will likely fail to boot, or cause an error.
<br>Bios is known to blacklist some titles, and refuse to boot them. This includes all titles with 00000000 000000A0 flag from that  [[PS2_Emulation#Game_ID/DiscID in PS20220WD20050620.crack | list (click here)]]
<br>Bios is know to blacklist some titles, and refuse to boot them. This include all titles with 00000000 000000A0 flag from that  [[PS2_Emulation#Game_ID/DiscID in PS20220WD20050620.crack | list (click here)]]


<br>'''More about the bios'''
<br>'''More about the bios'''
<pre>
<pre>
The version of the bios seems to be developement v2.20 from the Japanese region (22/01/2007), and is not limited to booting only NTSC-J games.
Bios version seems to be Developement v2.20 from Japan region (22/01/2007), but it's of course not limited to booting only NTSC-J games.
Emulator not support USB peripherals, but this seems to be not limitation of BIOS, as it is used also in CECH C/E PS3 consoles.  
Emulator not support USB peripherals, but this seems to be not limitation of BIOS, as it is used also in CECH C/E PS3 consoles.  
There are signs that different bios version exist, named PS20190AC20030623_nordram_miniOSD.bin. This bios has included handy extensions for debugging, and can debug print with "debug osd verbosity" from CLI set to "verbose". The most noticeable difference for both bios files seems to be the special RDRAM module.
There are signs that different bios version exist, named PS20190AC20030623_nordram_miniOSD.bin. This bios have included handy extensions for debugging, and can debug print with "debug osd verbosity" from CLI set to "verbose". Most noticeable difference for both bios files seems to be special RDRAM module.


While PS3 patches its bios to preferred regions, PS4 uses a so called CallHook which is better known for pcsx2 users as fastboot. No need to describe this patch here, just look at PCSX2 fastboot code. It's the same code, but the only difference is that PS4 emus don't have patches for different bios revisions.
While PS3 emulators patch bios to preferred region, emulator used in PS4 uses a so called CallHook which is better known for pcsx2 users as fastboot. No need to describe patch here, just look at PCSX2 fastboot code. It's the same code, but PS4 emus don't have patches for different bios revisions.
</pre>
</pre>
<br>'''Bios file information:'''
<br>'''Bios file information:'''
Line 3,701: Line 3,713:
*[https://forums.pcsx2.net/Thread-Fixing-unplayable-games A thread filled with patches for ps2 games]
*[https://forums.pcsx2.net/Thread-Fixing-unplayable-games A thread filled with patches for ps2 games]
{{Reverse Engineering}}
{{Reverse Engineering}}
<noinclude>
<noinclude>[[Category:Main]]</noinclude>
[[Category:Main]]
</noinclude>
Please note that all contributions to PS4 Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PS4 Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)