CCAPI Debugger - Are you deeply entrenched in the development sector of the PS3 scene? Check out this updated debugging tool by Madetho!
Madetho has released versions of CCAPI Debugger before, but this is the first time that QJ has talked about it. It's essentially a tool designed to display how your PS3 allocates memory in real-time. That means as you open backups and play homebrew, this tiny app will show you the contents of your system memory as it changes. This particular utility has been tested with CEX systems, but should also work on DEX as well. Version 2.2 adds a few bug fixes to the already established base. Check out more info below!
Connection via CCAPI(CEX) and TMAPI(DEX - Not tested).
Set/Get offset value (1 byte, 2 bytes, 4 bytes and text).
Debugging: Show current PS3 memory, starting at a specific address.
Auto update PS3 Memory in a specified interval time (Changes will be shown red in Hex).
Search for a value (Hex or Dec) in a specific range of memory. Results will be shown in a table. Refresh searched results to get current values of memory.
Search in Result for specific changes like ammo changing from 345 to 344.
Single click on result: Offset and current value will be shown in Offset Box to edit. Double click: Same as single click + PS3 memory at clicked offset will be shown.
Dump memory: Dumps PS3 Memory in specific range to a binary file.
Find Offset ranges for your game.
CTRL + D - Dump memory
F6 - Reload debug PS3 memory
F5 - Refresh search results
Bugfix: "[...] is not a parameter-less method, property or field of type '????????'"
Bugfix: small searching performance fix
Optimized the layout for people with lower resolutions.
Finding game ranges (Credits to Dnawrkshp).
Search in Result performance update (For 53,000 results: Old algorithm = 9:48 mins / New algorithm = 39 secs!).
Added time counter for Search/Refresh
ccarlsen Design Concept and Thread
byDaan for testing
Dnawrkshp NetCheat idea
Like it? Share with your friends!
If you got an error while installing Themes, Software or Games, please, read FAQ.