Editing PS2 Emulation
Jump to navigation
Jump to search
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 169: | Line 169: | ||
| || 2015 || || | | || 2015 || || | ||
|- | |- | ||
| War of the Monsters v1 || Subjectively the best emulator to use. Used as PS2CLASSICSGUI's default emulator, it is the best one around for accurate GS emulation, as some graphical issues on the Ratchet series and Tekken 5 can only be fixed by it. Another interesting case is GTA SA's lack of need for auto flush on it, and being natively performant. Additionally, its VU0 timing | | War of the Monsters v1 || Subjectively the best emulator to use. Used as PS2CLASSICSGUI's default emulator, it is the best one around for accurate GS emulation, as some graphical issues on the Ratchet series and Tekken 5 can only be fixed by it. Another interesting case is GTA SA's lack of need for auto flush on it, and being natively performant. Additionally, its VU0 timing is much better than Jakv2's, making it one of the best emulators on the PS4. || 0.1 || '''Rogue v1 and v2, Arc the Lad, Star Wars Jedi Starfighter''' | ||
|- | |- | ||
| GTA III || Fixed the PAL version of '''Genji: Dawn of the Samurai'''. || 0.6 || | | GTA III || Fixed the PAL version of '''Genji: Dawn of the Samurai'''. || 0.6 || | ||
| Line 340: | Line 340: | ||
| || || || Speedhacks / Desync Fixes|| || | | || || || Speedhacks / Desync Fixes|| || | ||
|- | |- | ||
| --ee-cycle-scalar || {{Universal}} ||Slowest cycles speed: 5.00<br>Normal cycles speed: 1.000<br>Fastest cycles speed: 0.100 || {{Float}} || | | --ee-cycle-scalar || {{Universal}} ||Slowest cycles speed: 5.00<br>Normal cycles speed: 1.000<br>Fastest cycles speed: 0.100 || {{Float}} || Can benefit core sync or performance (lowering the cycle rate may affect FMVS). The default value for most emulators is ~1.0. It is highly sensitive, as any slight change may break or fix the game. (Dividing 100 with the entered value is how to find what EE clock speed percentage % the value is setting. For example, 100/5.00 = 20%) || --ee-cycle-scalar=1.0 | ||
|- | |- | ||
| --ee-context-switch-cycles || {{Exclusive}} || Accelerate cycles (360 => 0) <br>Decelerate cycles (361 => ∞ ) || {{4 Bytes}}||Its effects are mysterious. Possibly configures how many CPU cycles the emulator should run before switching between different tasks or threads. Does not work on Jak emulators. Default value is 360. Seems to be useful for Bee Movie, Metal Gear Solid 3, as well as others with IPU issues | | --ee-context-switch-cycles || {{Exclusive}} || Accelerate cycles (360 => 0) <br>Decelerate cycles (361 => ∞ ) || {{4 Bytes}}||Its effects are mysterious. Possibly configures how many CPU cycles the emulator should run before switching between different tasks or threads. Does not work on Jak emulators. Default value is 360. Seems to be useful for Bee Movie, Metal Gear Solid 3, as well as others with IPU issues.|| --ee-context-switch-cycles=2700? | ||
|- | |- | ||
| --ee-hook || {{Variable}} || AdvanceClock<br>FastForwardClock<br>Mfifodrain || style="background:#212d9c; color:#ffffff;|4 Byte hex (offset),string,4 Byte hex (opcode),4 Byte Decimals (advanceclock value)|| Runs the specified functionality each time a selected EE offset is reached. FastForwardClock and AdvanceClock help fix core sync issues, but can be used as a speedhack. It is believed that AdvanceClock stalls the EE for a specified amount of cycles, while FastForwardClock behaves similarly. They are commonly used on the offset directly succeeding an affected CTC2 instruction. For a mysterious reason, some offsets are ignored by AdvanceClock - it could be that this function only works on instructions 2 cycles ahead of a branch, likely specifically designed to work at both the start or end of a branch. However, this is only the case for old emulators like King Of Fighters 2000 and War Of The Monsters. Newer ones such as Jak operate differently, where AdvanceClock only works 2 cycles ahead at the end of a branch instruction.<pre> | | --ee-hook || {{Variable}} || AdvanceClock<br>FastForwardClock<br>Mfifodrain || style="background:#212d9c; color:#ffffff;|4 Byte hex (offset),string,4 Byte hex (opcode),4 Byte Decimals (advanceclock value)|| Runs the specified functionality each time a selected EE offset is reached. FastForwardClock and AdvanceClock help fix core sync issues, but can be used as a speedhack. It is believed that AdvanceClock stalls the EE for a specified amount of cycles, while FastForwardClock behaves similarly. They are commonly used on the offset directly succeeding an affected CTC2 instruction. For a mysterious reason, some offsets are ignored by AdvanceClock - it could be that this function only works on instructions 2 cycles ahead of a branch, likely specifically designed to work at both the start or end of a branch. However, this is only the case for old emulators like King Of Fighters 2000 and War Of The Monsters. Newer ones such as Jak operate differently, where AdvanceClock only works 2 cycles ahead at the end of a branch instruction.<pre> | ||
| Line 2,150: | Line 2,150: | ||
| ra || 0x10000001F0 || f31 || 0x10000002AC || Rsvd31 || 0x100000034C || ra || 0x102000007C | | ra || 0x10000001F0 || f31 || 0x10000002AC || Rsvd31 || 0x100000034C || ra || 0x102000007C | ||
|- | |- | ||
| hi/hi1 (2x 64bit) || 0x1000000200 || fACC || 0x10000002B0 || {{cellcolors|#7698FF|#000000}}COP0 additional registers || || | | hi/hi1 (2x 64bit) || 0x1000000200 || fACC || 0x10000002B0 || {{cellcolors|#7698FF|#000000}}COP0 additional registers || || pc || 0x102000008C | ||
|-style="background-color:#EEEFF2" | |-style="background-color:#EEEFF2" | ||
| lo/lo1 (2x 64bit) || 0x1000000210 || {{cellcolors|#7698FF|#000000}}FPU CTRL (FCR) || || real Pcr0 || 0x1000000350 || hi ||0x1020000090 ?? | | lo/lo1 (2x 64bit) || 0x1000000210 || {{cellcolors|#7698FF|#000000}}FPU CTRL (FCR) || || real Pcr0 || 0x1000000350 || hi ||0x1020000090 ?? | ||