Well, you said you got the same result using CE and the PCSX2 debugger. I assumed you repeated the test with each, since getting a halt on 0x001200AC would clearly not be the same result as your previous work.
Announcement
Collapse
No announcement yet.
Tutorial for creating ASM codes for PS2 with Cheat Engine and pcsx2
Collapse
X
-
I only get the same result if I'm using the debug version of pcsx2. If not it will still be the first one I showed you.Originally posted by Pyriel View PostWell, you said you got the same result using CE and the PCSX2 debugger. I assumed you repeated the test with each, since getting a halt on 0x001200AC would clearly not be the same result as your previous work.
Comment
-
OK, that's what I figured. The debugging version probably runs automatically in an interpreter mode with fewer threads going. When you used the optimized version, I'm guessing CE was thrown way out of whack by recompilation, etc.
The guides should probably note that you should use a debugger friendly version or emulation mode if you want to do this sort of task with CE. Otherwise, your results are likely to be inaccurate—probably close enough, if you do further analysis, but not immediately useful. However, if you're already using a version with a debugger, I don't know why you'd want to fall back to CE, unless the debugger is deficient somehow.
Comment

Comment