dragonjon99
Just put both archives in your cheat engine directory, something like C: \program files\cheat engine\autorun
Prince of Persia - The Sands of Time (PAL-M5) SLES-51918 4B58A7A8
SLES-51918_4B58A7A8.pnach
Tested at 50 fps and with progressive scan
Red Dead Revolver (PAL-M) SLES-52478 E2E67E23
SLES-52478_E2E67E23.pnach
Tested at 50/60fps
Add 480p progressive scan mode. When enabling the patch you will not be able to select 50 hz
Score International Baja 1000 - The Official Game
SLUS-21850
CRC=9AB3424F
60fps
Update: hang in loading screen fixed
Lara Croft Tomb Raider - Anniversary (PAL-M) SLES-54674 A629A376
SLES-54674_A629A376.pnach
Tested at 50 and progressive scan.
update: graphical glitches fixed
Teenage Mutant Ninja Turtles 2 - Battle Nexus
SLUS-20981
CRC=EE628509
60FPS
Teenage Mutant Ninja Turtles 3 - Mutant Nightmare
SLUS-21184
CRC=DB42119C
60FPS
Note: graphical glitches fixed, you do not worry anymore for desactivate cheats from inicial boot, now patch in both games works like charm
Sorry for taking the freedom to ask but I've been trying to unlock the framerate on the NTSC-U versions of "The Sims: Bustin' Out" and "The Urbz: Sims In The City" and and I'm kind of stuck.
While I'm able to check some debug flags in both games that handle certain leftover developer only mechanics, I'm unable to spot which one is responsible for the FPS unlocking mechanism (I know that there is a mechanism somewhere inside). Bustin Out seems for some reason to always lock it's framerate at 20FPS and Urbz locks sometimes at 30 and sometimes at 20.
If it helps, these codes will show the dev FPS counter on screen (I guess finsing what routines are being accessed by this memory could be a lead):
The Sims: Bustin' Out:
patch=1,EE,203F8770,extended,00000001
The Urbz: Sims In The City:
patch=1,EE,204C5C4C,extended,00000001
(07-17-2023, 08:41 PM)VIRGIN KLM Wrote: [ -> ]Sorry for taking the freedom to ask but I've been trying to unlock the framerate on the NTSC-U versions of "The Sims: Bustin' Out" and "The Urbz: Sims In The City" and and I'm kind of stuck.
While I'm able to check some debug flags in both games that handle certain leftover developer only mechanics, I'm unable to spot which one is responsible for the FPS unlocking mechanism (I know that there is a mechanism somewhere inside). Bustin Out seems for some reason to always lock it's framerate at 20FPS and Urbz locks sometimes at 30 and sometimes at 20.
If it helps, these codes will show the dev FPS counter on screen (I guess finsing what routines are being accessed by this memory could be a lead):
The Sims: Bustin' Out:
patch=1,EE,203F8770,extended,00000001
The Urbz: Sims In The City:
patch=1,EE,204C5C4C,extended,00000001
Well, in my experience with the Sims games I can tell you that those games use 2xxx0002 pattern so you try to find 28xx0002 or 24xx0002 nearly of this suspicious addresses, the Sims castaway use 28820002 pattern, you can start a mass searching with this pattern. Good luck