What are you trying to do exactly? Which addresses? That has never happened to me, but some addresses might be protected against that kind of debugging.
I know how to find a pointer using cheat engine, using the Find out what writes or accesses this address buttons.
But it crashes when I do it to MW3, is there a way I can get around this?
Help would be appreciated.
Sorry if I'm in the wrong section, etc.
What are you trying to do exactly? Which addresses? That has never happened to me, but some addresses might be protected against that kind of debugging.
CoD Minion from 09/19/2012 to 01/10/2013
Also a pointer scan would be better, you aren't finding pointer using a pointer scan fyi.
Last edited by MarkHC; 01-03-2013 at 11:17 AM.
Have same when I try to get the address which writes too 0x25914648 (game time for me)
Okay, the pointer scan is working but crashes after a couple of minutes because it makes my computer really slow. The other debugger just ends mw3 instantly.
If "other debugger" = OllyDBG, I had the same problem.. never found out why it happened :S It feels like some kind of checking against debuggers, but I really don't think they have one so... And it happened just on Steam, I can debug IW5M without any problem so... /
CoD Minion from 09/19/2012 to 01/10/2013
There is debugging protection
Not by "starting" it via Olly|IDA
But attaching it at run-time will cause the game to freeze.
(Note: Sometimes you're able to make the game run, but rare)
So, yes. There is protection, and yes. Cheat Engine debug attaching will cause game to crash