OPL+PS2RD Cheat Engine Integration Beta Release

[lee4]

[repost]

I did quick test in USB mode, work fine

mass:/CHT/SLUS_203.13.cht
mass:/CD/SLUS_203.13.Wave Rally.iso

inside SLUS_203.13.cht

Enable Code (Must Be On)
9020262C 00832021

Max Engine Status	
00395ECC 0000000C
  
Max Grip Status	
00395ED0 0000000C
  
Max Handling Status		
00395EC8 0000000C
  
Max Tricks Status		
00395ED4 0000000C
  
Never Penalty Misses
0066BC24 00000000
0066BC28 00000009

[lee4]

0.9.2 official and older,
no problem

new OPL modified by SP193,
alots problems

[47iscool]

yes, it is new OPL
older OPL didnt write there before

As for PS2rd problem
its run in different area than codebreaker does.
PS2rd probably has data where subroutine is writing

0.6, 0.7 etc?

[lee4]

It's not OPL, it's ps2rd.

If you use the cracked CB with those codes then launch SoTC on OPL it works flawless. Sadly the ps2rd gui hasn't seen an update in a while. It would be nice to be able to use it on PS2ESDL.

yes, it is new OPL
older OPL didnt write there before

As for PS2rd problem
its run in different area than codebreaker does.
PS2rd probably has data where subroutine is writing

[47iscool]

Codes like that are deliberately using kernel space because most games won't touch it. There's only one Capcom or Konami game I'm aware of that use it for game data, and a few that access it for anti-cheat purposes. Other than that, it's a free resource.

How compatible the codes are with your software is down to the specific package. I thought PS2RD used 0x80000 - 0x9FFFF, but maybe I'm mistaken, and it steps on 0xF0000 and up. Although, it could just be clearing the space to prevent issues. Likewise OPL could be using 0xA0000 - 0xCFFFF for it's own purposes, doesn't allow writes to kernel space for safety, or keeps the memory clear for some other reason.

It's not OPL, it's ps2rd.

If you use the cracked CB with those codes then launch SoTC on OPL it works flawless. Sadly the ps2rd gui hasn't seen an update in a while. It would be nice to be able to use it on PS2ESDL.

[Pyriel]

Codes like that are deliberately using kernel space because most games won't touch it. There's only one Capcom or Konami game I'm aware of that use it for game data, and a few that access it for anti-cheat purposes. Other than that, it's a free resource.

How compatible the codes are with your software is down to the specific package. I thought PS2RD used 0x80000 - 0x9FFFF, but maybe I'm mistaken, and it steps on 0xF0000 and up. Although, it could just be clearing the space to prevent issues. Likewise OPL could be using 0xA0000 - 0xCFFFF for it's own purposes, doesn't allow writes to kernel space for safety, or keeps the memory clear for some other reason.

[47iscool]

seem new OPL's new CDVDFSV and CDVDMAN stuff
breaks most of codebreaker subroutines codes
(official codes) 200c0000 and (skiller's codes) 200a0000

I've had issues with some of bungholio codes for Shadow of The Colossus.

The activator/jump codes won't work with ps2rd.

This code here:

Activator
200ff000 3c19012f
200ff004 3739b6ac
200ff008 8f380000
200ff00c 1300003b
200ff010 3c190013
200ff014 3739d85c
200ff018 972f0000
200ff0fc 03e00008
2135828c 0803fc00

But they work fine on the CB. I'm guessing it's that last code which is pretty high in RAM.

Some codes for Tony Hawk's Project 8 lock up when using ps2rd, namely the ones that are high memory such as the level swap codes

[lee4]

seem new OPL's new CDVDFSV and CDVDMAN stuff
breaks most of codebreaker subroutines codes
(official codes) 200c0000 and (skiller's codes) 200a0000

[47iscool]

Thanks for the info lee! Now I need to hook my PS2 back up!

[lee4]

Press Start in OPL to bring up options menu
Go to Settings to Enable

"Show PS2RD cheat Engine on Main Menu" to [ON]

Go to Cheat Settings to Enable

"Enable PS2RD cheat Engine Mode" to [ON]

Go to "Save changes" to Save settings

source:
http://psx-scene.com/forums/f150/ope...ml#post1135590