Post: CCDebugger and GT6
Options
03-27-2014, 12:34 PM
#1
Mint Sauce
Do a barrel roll!
When I dump the memory within a set range, then alter a game setting and dump again, there's loads of differences between the two when comparing in a hex editor. It's impossible for me to pin down the correct area
With GT5 it was just one change, is this because it was static save file and not real time?
03-29-2014, 02:10 AM
#2
Mint Sauce
Do a barrel roll!
Entered some random stuff near where it said debug camera (lol), around 0x3060800 iirc and got this:
You must login or register to view this content.
Pathetic for a hours messing about, I can't do anything else with it but I remember the PSP version of GT having one of these debug cameras that you could fully control. So maybe it's possible here with the correct editing?
Everything else I changed caused a continuous load
You must login or register to view this content.
Pathetic for a hours messing about, I can't do anything else with it but I remember the PSP version of GT having one of these debug cameras that you could fully control. So maybe it's possible here with the correct editing?
Everything else I changed caused a continuous load
03-30-2014, 04:05 AM
#4
FarSideX
I’m too L33T
Originally posted by Mint
Is anybody using this and could you please offer any tips on where to find stuff? I would like the game's options.
When I dump the memory within a set range, then alter a game setting and dump again, there's loads of differences between the two when comparing in a hex editor. It's impossible for me to pin down the correct area
With GT5 it was just one change, is this because it was static save file and not real time?
When I dump the memory within a set range, then alter a game setting and dump again, there's loads of differences between the two when comparing in a hex editor. It's impossible for me to pin down the correct area
With GT5 it was just one change, is this because it was static save file and not real time?
Working with real time is not the same as working with a save file. A save file is basically a snapshot of a bunch of the variables from a running program, saved in a particular order so they can read back. In RTE those variables are not just read back to one spot in memory; they are assigned to variables that could exist anywhere in memory.
When using CCdebugger the numbers in red are those that changed since the last refresh, I almost never use auto refresh because of this. Also as you page down the numbers in red are those that are different in that position on the screen and not necessarily changed since the last scan. Use the load refresh button to look for changes.
The game regions: The region that starts at 0x00010000 is the EBOOT.bin, all other regions are game dependent. One exception is the 0xC0000000 region. That is almost always the stack, you should not change anything in there, there is rarely anything of use in that region.
It looks like you already found something interesting. It could possibly be the X,Y,Z,H,P,B values for the camera by the look of the picture you posted.
The following user thanked FarSideX for this useful post:
Copyright © 2026, NextGenUpdate.
All Rights Reserved.
