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,382: Line 2,382:
| 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
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)