Cheat Engine

paul44 · Last edited by paul44 on Wed May 15, 2024 1:18 am; edited 1 time in total

Images: [ https://ibb.co/album/TqvZt4 ]

Pure coincidental - while using v6.7 - I came across this feature (image 1). I then checked every other version I have installed: v6.8.x upto v7.5, and none of these reproduce the very same output.
I also compared settings between 6.7 and 6.8x (no apparent diff) and file/folders (no additional/new; but quite some diffs obviously)

=> Obvous Q: can it be "re-enabled" again (somewhow) ?

ps: this is for Watch Dogs 2...

ParkourPenguin · Posted: Mon May 13, 2024 1:17 pm Post subject:

Try enabling some of the bottom settings in Memory View -> View. In particular "Show symbols"

Dark Byte · Posted: Mon May 13, 2024 1:40 pm Post subject:

the modulename+offset notation is the correct one.
6.7 has a bug where the last symbol is stretched all the way to the end of the module. the code you see there has no relationship to the symbol shown

paul44 · Posted: Wed May 15, 2024 1:17 am Post subject: bummer...

well, that is unfortunate... from my point of view ofc Crying or Very sad

FYI: in case anyone wonders why I still use v6.7 ?
images: [ https://ibb.co/album/Rj9BLr ]

1. set debugger to 'page exceptions'
2. in v6.7+ (?) you can 'find out...' over a large range of bytes
3. in v7.x (?) this feature is limited to just "1" line (green-colored bytes)
=> no idea why it is even less in this game; usually you'll get 32 bytes monitored ?!

When/why do i use this:
a. fastest way to find "unique" opcodes that access that particular structure
b. "easy" way to find particular/related (1-byte) system_flags

source info: #Sunbeam

=> Important:
1. do not forget to set it back to 'HW BP' ! (~ as you'll get strange behaviour when trying 'find out what...' then + also when setting BPs)
2. if CE/PC responseTime goes down the drain (can happen occassionally...), then try:
a) select less bytes
b) enable 'wait for gui update' (i tend to forget/skip that one)

Dark Byte · Posted: Wed May 15, 2024 3:10 am Post subject:

page exceptions in settings only affects the basic debug options tied to a hotkey

For more advanced options you have multiple options. Rightclick the selected bytes, and then go to data breakpoint, and then instead of selecting the debug option, set the breakpoint method you wish to use. In your case set it to "exception breakpoint"

this way you don't have to close the whole debugger if you only needed to find one thing and then continue using normal hardware watchpoints