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 1: Line 1:


=2024-present year=
<pre>No emulator backported yet.</pre>
=2014-2018 emulators=
= Description =
= Description =


Line 275: Line 271:
| --fpu-no-clamp-range || start,end offset (0x0 - 0x1FFFFFF) || Per-range clamping for the FPU in the selected memory range. || --fpu-no-clamp-range=0x1acce0,0x2acce0
| --fpu-no-clamp-range || start,end offset (0x0 - 0x1FFFFFF) || Per-range clamping for the FPU in the selected memory range. || --fpu-no-clamp-range=0x1acce0,0x2acce0
|-  
|-  
| --fpu-accurate-muldiv  || 0 = Disabled<br>1 = Enabled  || Allows the FPU to accurately Divide/Multiply for all offsets by using software floats rather than hardware floats. (Extremely slow) || --fpu-accurate-muldiv=1
| --fpu-accurate-muldiv  || 0 = Disabled<br>1 = Enabled  || Allows the FPU to accurately Divide/Multiply by 0 for all offsets by using software floats rather than hardware floats. (Extremely slow) || --fpu-accurate-muldiv=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
| --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-muldiv-range || start,end offset (0x0 - 0x1FFFFFF) || Allows the FPU to accurately Divide/Multiply 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
|-  
|-  
| --fpu-accurate-addsub-range || start,end offset (0x0 - 0x1FFFFFF) || Allows the FPU to accurately Add/Subtract in the specified ee memory range by using software floats rather than hardware floats. || --fpu-accurate-addsub-range=0x1acce0,0x2acce0
| --fpu-accurate-addsub-range || start,end offset (0x0 - 0x1FFFFFF) || Allows the FPU to accurately Add/Subtract in the specified ee memory range by using software floats rather than hardware floats. || --fpu-accurate-addsub-range=0x1acce0,0x2acce0
Line 415: Line 411:
|  || Speedhacks || ||
|  || Speedhacks || ||
|-
|-
| --vu1-mpg-cycles  || Decimals<br>0 - 65535 || 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<br><pre> Symbols (They change values close to VU1-mpg-cycles' offset):
| --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<br><pre> Symbols:
 
$ = ?
$ goes to the specified succeeding offsets. $0 will go 2 bytes forward and change them. $1 will go 4 bytes forward and change the 2 bytes specified. For example, $0,$1 will change the 4 bytes ahead as the specified 2 bytes' value.
0x = ?
 
- = Changes the specified preceding 2 bytes behind VU1 mpg cycles' offset according to the added number. Adding -1, for example will change the 2 bytes before it. Likewise, adding -2 will go 4 bytes away and change the specified 2 bytes accordingly. It even can change EE cycle scalar itself if you go far enough. These numbers are in HEX. Infinite amounts of '-' symbols seem to be supported.</pre>
'0x' Is like '+' a symbol that modifies succeeding values. 0x0 goes 2 bytes ahead and changes them, 0x1 goes 4 bytes ahead and so on and so forth.
 
'-' or '+' Changes the specified preceding or succeeding 2 bytes of VU1 mpg cycles' offset according to the added number. Adding -1, for example will change the 2 bytes before it. Likewise, adding -2 will go 4 bytes away and change the specified 2 bytes accordingly. It even can change EE cycle scalar itself if you go far enough. These numbers are in HEX. Infinite amounts of '-' and '+' symbols seem to be supported.</pre>
|-
|-
| --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 478: Line 471:
|  || Speedhacks || ||
|  || Speedhacks || ||
|-
|-
| --vu0-mpg-cycles || Decimals<br>0 - 65535 || Set initial cycle speed for VU0 Micro-programs. 100 is the default value. It is not available in older emulators such as War of the Monsters. Raising the value helps COP2 timing, while lowering does the opposite.|| --vu0-mpg-cycles=1000<br><pre> Symbols (They change values close to VU0-mpg-cycles' offset):
| --vu0-mpg-cycles || 0 - 400000 || Set initial cycle speed for VU0 Micro-programs. 100 is the default value. It is not available in older emulators such as War of the Monsters. || --vu0-mpg-cycles=1000<br><pre> Symbols:
 
$ = ?
$ goes to the specified succeeding offsets. $0 will go 2 bytes forward and changes them. $1 will go 4 bytes forward and changes the 2 bytes specified. For example, $0,$1 will change the 4 bytes ahead as the specified 2 bytes value.
0x = ?
 
- = Changes the specified preceding 2 bytes behind VU1 mpg cycles' offset according to the added number. Adding -1, for example will change the 2 bytes before it. Likewise, adding -2 will go 4 bytes away and change the specified 2 bytes accordingly. It even can change EE cycle scalar itself at -15 (Jakv2). These numbers are in HEX. Infinite amounts of '-' symbols seem to be supported.</pre>
'0x' Is like '+' a symbol that modifies succeeding values. 0x0 goes 2 bytes ahead and changes them, 0x1 goes 4 bytes ahead and so on and so forth.
 
'-' or '+' Changes the specified preceding or succeeding 2 bytes of VU0 mpg cycles' offset according to the added number. Adding -1, for example will change the 2 bytes before it. Likewise, adding -2 will go 4 bytes away and change the specified 2 bytes accordingly. It even can change EE cycle scalar itself at -15 (Jakv2). Setting it to --vu0-mpg-cycles=1280,-15 would, for example, set ee-cycle-scalar to 5. These numbers are in HEX. Infinite amounts of '-' and '+' instances seem to be supported.</pre>
|-
|-
| --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 588: Line 578:
| --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 ||  Enabling CLUT merging helps improve how the emulator processes textures that use indexed color palettes. It ensures more accurate emulation of the PS2’s color handling. It sometimes restores missing graphical elements, and fix texture flickering (prominently flickering shadows or UI elements).  It prevents Spyro's shadow from flickering in Enter the Dragonfly. Enabling it is the accurate, albeit slow option. || --gs-use-clut-merge=1
| --gs-use-clut-merge || 0, 1 ||  Enabling CLUT merging helps improve how the emulator processes textures that use indexed color palettes. It ensures more accurate emulation of the PS2’s color handling. It sometimes restores missing graphical elements, and fix texture flickering (prominently flickering shadows or UI elements). Enabling it is the accurate option. || --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
| --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
Line 768: Line 758:
<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]
{| 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|#38ffc3|#000000}}PS4 !! Notes
! {{cellcolors|#00d6f2|#000000}}PCSX2 !! {{cellcolors|#d352fa|#000000}}PS4 !! Notes
|-
|-
| {{cellcolors|#0b9fb3|#000000}}XGKickHack ||{{cellcolors|#03fcb1|#000000}}--vu-xgkick-delay= ||  Possible equivalent value is 8
| {{cellcolors|#0b9fb3|#000000}}XGKickHack ||{{cellcolors|#b52fde|#000000}}--vu-xgkick-delay= ||  Possible equivalent value is 8
|-
|-
| {{cellcolors|#0b9fb3|#000000}}VuAddSubHack ||{{cellcolors|#03fcb1|#000000}}--vu-hack-triace=1 || Required for every single game developed by TriAce
| {{cellcolors|#0b9fb3|#000000}}VuAddSubHack ||{{cellcolors|#b52fde|#000000}}--vu-hack-triace=1 || Required for every single game developed by TriAce
|-
|-
| {{cellcolors|#0b9fb3|#000000}}vuClampMode: 2 ||{{cellcolors|#03fcb1|#000000}}<br>--vu1-no-clamping=0<br>--vu0-no-clamping=0<br>--cop2-no-clamping=0  ||
| {{cellcolors|#0b9fb3|#000000}}vuClampMode: 2 ||{{cellcolors|#b52fde|#000000}}--vu1-clamp-operands=1<br>--vu1-clamp-results=1<br>--vu1-no-clamping=0<br>--vu0-clamp-operands=1<br>--vu0-clamp-results=1<br>--vu0-no-clamping=0<br>--vu-to-double=0  ||
|-
|-
| {{cellcolors|#0b9fb3|#000000}}vuClampMode: 3  || {{cellcolors|#03fcb1|#000000}}<br>--vu1-no-clamping=1<br>--vu0-no-clamping=1<br>--cop2-no-clamping=1<br>--vu-to-double=1 ||
| {{cellcolors|#0b9fb3|#000000}}vuClampMode: 3  || {{cellcolors|#b52fde|#000000}}--vu1-clamp-operands=1<br>--vu1-clamp-results=1<br>--vu1-no-clamping=1<br>--vu0-clamp-operands=1<br>--vu0-clamp-results=1<br>--vu0-no-clamping=1<br>--vu-to-double=1 ||
|-
|-
| {{cellcolors|#0b9fb3|#000000}}eeClampMode: 2 || {{cellcolors|#03fcb1|#000000}}--fpu-to-double=0<br>--fpu-no-clamping=0<br> ||
| {{cellcolors|#0b9fb3|#000000}}eeClampMode: 2 || {{cellcolors|#b52fde|#000000}}--fpu-clamp-operands=1<br>--fpu-clamp-results=1<br>--cop2-clamp-operands=1<br>--cop2-clamp-results=1<br>--fpu-to-double=0<br>--fpu-no-clamping=0<br>--cop2-no-clamping=0 ||
|-
|-
| {{cellcolors|#0b9fb3|#000000}}eeClampMode: 3  || {{cellcolors|#03fcb1|#000000}}--fpu-to-double=1<br>--fpu-no-clamping=1<br> ||
| {{cellcolors|#0b9fb3|#000000}}eeClampMode: 3  || {{cellcolors|#b52fde|#000000}}--fpu-clamp-operands=1<br>--fpu-clamp-results=1<br>--cop2-clamp-operands=1<br>--cop2-clamp-results=1<br>--fpu-to-double=1<br>--fpu-no-clamping=1<br>--cop2-no-clamping=1 ||
|-
|-
| {{cellcolors|#0b9fb3|#000000}}eeRoundMode: || {{cellcolors|#03fcb1|#000000}}--fpu-accurate-muldiv=1<br>--fpu-accurate-addsub=1 ||
| {{cellcolors|#0b9fb3|#000000}}eeCycleRate: || {{cellcolors|#b52fde|#000000}}--ee-cycle-scalar= || '''"Potential" equivalent values: PCSX2 - PS4''':<br>300% --> 0.333<br>180% --> 0.555<br>130% -->0.769<br>'''100% --> 1.0'''<br>75% --> 1.333<br>60% --> 1.666<br>50% --> 2
|-
|-
| {{cellcolors|#0b9fb3|#000000}}vu0RoundMode: || {{cellcolors|#03fcb1|#000000}}--cop2-accurate-mul=1<br>--cop2-accurate-addsub=1<br>--vu0-accurate-addsub-range=<br>--vu0-mul0fix-range= ||
| {{cellcolors|#0b9fb3|#000000}}FpuNegDivHack<br>FpuMulHack || {{cellcolors|#b52fde|#000000}}--fpu-accurate-muldiv=1 ||  
|-
|-
| {{cellcolors|#0b9fb3|#000000}}vu1RoundMode: || {{cellcolors|#03fcb1|#000000}}--vu1-accurate-addsub-range=<br>--vu1-mul0fix-range=||
| {{cellcolors|#0b9fb3|#000000}}cpuCLUTRender: 1 || {{cellcolors|#b52fde|#000000}}--gs-uv-shift-pointsampling=1 ||
|-
|-
| {{cellcolors|#0b9fb3|#000000}}eeCycleRate: || {{cellcolors|#03fcb1|#000000}}--ee-cycle-scalar= || '''"Potential" equivalent values: PCSX2 - PS4''':<br>300% --> 0.333<br>180% --> 0.555<br>130% -->0.769<br>'''100% --> 1.0'''<br>75% --> 1.333<br>60% --> 1.666<br>50% --> 2
| {{cellcolors|#0b9fb3|#000000}}MTVUSpeedHack: 0 || {{cellcolors|#b52fde|#000000}}--vu1=jit-sync || Some games will also require --vu1-mpg-cycles= to be between "6000 - 19000"
|-
|-
| {{cellcolors|#0b9fb3|#000000}}FpuNegDivHack<br>FpuMulHack || {{cellcolors|#03fcb1|#000000}}--fpu-accurate-muldiv=1 ||  
| {{cellcolors|#0b9fb3|#000000}}mergeSprite<br>alignSprite || {{cellcolors|#b52fde|#000000}}--gs-kernel-cl-up="up2x2simple" || Note: works similarly but not the equivalent
|-
|-
| {{cellcolors|#0b9fb3|#000000}}cpuCLUTRender: 1 || {{cellcolors|#03fcb1|#000000}}--gs-uv-shift-pointsampling=1 ||
| {{cellcolors|#0b9fb3|#000000}}cpuSpriteRenderBW: 4 || {{cellcolors|#b52fde|#000000}}--gs-opt-frbuff-switch=1 || Note: works similarly but not the equivalent
|-
|-
| {{cellcolors|#0b9fb3|#000000}}MTVUSpeedHack: 0 || {{cellcolors|#03fcb1|#000000}}--vu1=jit-sync || Some games will also require --vu1-mpg-cycles= to be between "6000 - 19000"
| {{cellcolors|#0b9fb3|#000000}}mipmap || {{cellcolors|#b52fde|#000000}}--gs-use-mipmap=1<br>--gs-kernel-cl="mipmap" || Note: Works best on War of the Monsters emu
|-
|-
| {{cellcolors|#0b9fb3|#000000}}mergeSprite<br>alignSprite || {{cellcolors|#03fcb1|#000000}}--gs-kernel-cl-up="up2x2simple" || Note: works similarly but not the equivalent
| {{cellcolors|#0b9fb3|#000000}}autoFlush || {{cellcolors|#b52fde|#000000}}--gs-flush-ad-xyz=safe || Possible values include always, safe, off, 0
|-
|-
| {{cellcolors|#0b9fb3|#000000}}cpuSpriteRenderBW: 4 || {{cellcolors|#03fcb1|#000000}}--gs-opt-frbuff-switch=1 || Note: works similarly but not the equivalent
| {{cellcolors|#0b9fb3|#000000}}VIF1StallHack || {{cellcolors|#b52fde|#000000}}--vif1-instant-xfer=0 || If that doesn't work, the lua command eeObj.SchedulerDelayEvent("vif1.dma", 0x9000) might assist.
|-
|-
| {{cellcolors|#0b9fb3|#000000}}mipmap || {{cellcolors|#03fcb1|#000000}}--gs-use-mipmap=1<br>--gs-kernel-cl="mipmap" || Note: Works best on War of the Monsters emu
| {{cellcolors|#0b9fb3|#000000}}wildArmsHack || {{cellcolors|#b52fde|#000000}}--gs-kernel-cl-up="DarkCloud2" ||
|-
|-
| {{cellcolors|#0b9fb3|#000000}}autoFlush || {{cellcolors|#03fcb1|#000000}}--gs-flush-ad-xyz=safe || Possible values include always, safe, off, 0
| {{cellcolors|#0b9fb3|#000000}}deinterlace || {{cellcolors|#b52fde|#000000}}--force-frame-blend=1 ||
|-
| {{cellcolors|#0b9fb3|#000000}}VIF1StallHack || {{cellcolors|#03fcb1|#000000}}--vif1-instant-xfer=0 ||  If that doesn't work, the lua command eeObj.SchedulerDelayEvent("vif1.dma", 0x9000) might assist.
|-
| {{cellcolors|#0b9fb3|#000000}}wildArmsHack || {{cellcolors|#03fcb1|#000000}}--gs-kernel-cl-up="DarkCloud2" ||
|-
| {{cellcolors|#0b9fb3|#000000}}deinterlace || {{cellcolors|#03fcb1|#000000}}--force-frame-blend=1 ||
|}
|}


Line 1,869: Line 1,853:
[https://www.psdevwiki.com/ps4/Talk:PS2_Classics_Emulator_Compatibility_List#Custom_PS2emu_Configuration_Files Other custom configurations made by users can be found here]
[https://www.psdevwiki.com/ps4/Talk:PS2_Classics_Emulator_Compatibility_List#Custom_PS2emu_Configuration_Files Other custom configurations made by users can be found here]


= Memory Map =
= Memory Mapping =


{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: left;"
{| cellspacing="0" cellpadding="2" border="1" class="wikitable" style="text-align: left;"
Line 2,509: Line 2,493:
|-
|-
| ? || Unavailable || Yu-Gi-Oh! The Duelists of the Roses || In-game data corruption (?) leading to a hang || #11576
| ? || Unavailable || Yu-Gi-Oh! The Duelists of the Roses || In-game data corruption (?) leading to a hang || #11576
|-
| ? || Janky patch || Flame of Recca: Final Burning || IPU running faster than it should. || #11335
|-
|-
| ? || Unavailable || Ape Escape 3 || Sudden burst of in-game speed at some random points in the map || Unavailable
| ? || Unavailable || Ape Escape 3 || Sudden burst of in-game speed at some random points in the map || Unavailable
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)