Page 1 of 1

Cheat Engine "what writes to this address" crashes game

Posted: Sat Sep 22, 2018 1:34 am
by Pedroma34
I know it's probably anti hack or something. The game is Prototype. Every time I want to see what writes to a address the game crashes. Is there a way of bypass this? I'm not over writing anything so I don't think it's integrity check. Help

Re: Cheat Engine "what writes to this address" crashes game

Posted: Sat Sep 22, 2018 2:54 am
by TimFun13
Check the debugger settings (settings->debugger), try "VEH" if "windows debugger" is selected or visa versa.

Re: Cheat Engine "what writes to this address" crashes game

Posted: Sat Sep 22, 2018 5:27 am
by Pedroma34
ShyTwig16 wrote:
Sat Sep 22, 2018 2:54 am
Check the debugger settings (settings->debugger), try "VEH" if "windows debugger" is selected or visa versa.
It's detecting both ways :( still crashing. Is there another way?

Re: Cheat Engine "what writes to this address" crashes game

Posted: Sat Sep 22, 2018 5:34 am
by TimFun13
Pedroma34 wrote:
Sat Sep 22, 2018 5:27 am
...

It's detecting both ways :( still crashing. Is there another way?
It's SP only, and there is no DRM; so I doubt it's "detecting" the debugger.
You can try the "kernelmode" debugger, if your processor supports what CE uses.
You can also try it with CE "6.7" see if it's an error with "6.8.*".

EDIT:
I think it might be related to this:
[Link]

Re: Cheat Engine "what writes to this address" crashes game

Posted: Sat Sep 22, 2018 5:43 am
by Pedroma34
ShyTwig16 wrote:
Sat Sep 22, 2018 5:34 am
Pedroma34 wrote:
Sat Sep 22, 2018 5:27 am
...

It's detecting both ways :( still crashing. Is there another way?
It's SP only, and there is no DRM; so I doubt it's "detecting" the debugger.
You can try the "kernelmode" debugger, if your processor supports what CE uses.
You can also try it with CE "6.7" see if it's an error with "6.8.*".
OH MAH GAWD GOD BLESS YOU. It worked with 6.7. I've been having a lot of problems with 6.8, like if I search for a value on "all" types, I would get 0 results. Now thats fixed too. Thank you!