Cheat Engine

Alesto · Newbie cheater Reputation: 0 Joined: 20 May 2020 Posts: 10

Hey guys,

i opened a thread about this problem like over a year ago. Somehow i can't answer to that one, so i'm forced to open a new one right here. I'm doing that, because it occurred again and i now know how to produce it.

My problem is the following:

I got a pointer pointing to the right address (XCor), showing the right value. There is absolutely no problem with changing the value or it being not reliable.

But, when i'm searching for something else, f.e. HP and open the memory browser to watch the data some weird stuff happens. I can still find values, i can still edit them, so the handle to the process seems to be alright and the pointer in the table still points to the correct value, but if i open the edit window for the pointeraddress to look/edit (at) the offsets, it breaks and suddenly points to "???". The address for the XCor, the pointer is pointing to, has not changed, but from then on i can't "add it manually". It always points to ???.

From my newbie point of view, it looks like some bug in CE, like it suddenly can't follow the pointer anymore even if nothing has changed.

When i'm only searching values the pointer is absolutely reliable, it never breaks, so it has nothing to to with some sort of anticheat that kicks me out after some time. But after opening memory view (even if i close it soon after) the problem occurres.

It makes no sense to my, why the pointer should be affected in any way by opening the memory view.

Maybe someone can help me with that.

Thanks in advance!
Greetings

ParkourPenguin · Posted: Wed Jun 09, 2021 11:19 am Post subject:

This topic?
https://forum.cheatengine.org/viewtopic.php?t=614253

I've had problems where the pointer scanner would find a base address in something CE controls: e.g. a pointer to whatever address you're looking at what instructions access. What exactly is the pointer path? You can replace the game's name with game.exe, but if it's something.dll and "something" isn't uniquely related to the game, leave it.

I guess it could be an anticheat triggering on something CE does when the memory view window opens, but I'd imagine the anticheat would be more direct about it.

Alesto · Newbie cheater Reputation: 0 Joined: 20 May 2020 Posts: 10

Thank you very much for linking the thread. Somehow i couldn't log in while looking at this old thread and therefore i couldn't answer to it.

Alesto · Newbie cheater Reputation: 0 Joined: 20 May 2020 Posts: 10

ParkourPenguin · Posted: Sat Jun 19, 2021 11:15 am Post subject:

Sounds like the symbolhandler stops being able to recognize the symbol "Game.exe".
After that 4 seconds of having the memory viewer open and stuff goes wrong, execute this in the Lua console:

Alesto · Newbie cheater Reputation: 0 Joined: 20 May 2020 Posts: 10

Thank you very much for replying again.

ParkourPenguin · Posted: Sun Jun 20, 2021 11:14 am Post subject:

No one else seems to have this problem, so it's probably either that particular game or some third party software (e.g. antivirus) screwing with stuff. There's not much anyone else can do for you.

You'd have to debug CE to figure out exactly what's failing. Look through the source code to see how symbols get resolved. You might be able to narrow it down from inside CE using Lua, and DebugView can view strings passed to outputdebugstring. Compiling CE from source and debugging it is an option too.

Alesto · Newbie cheater Reputation: 0 Joined: 20 May 2020 Posts: 10

Thank you very much for your patience, time and effort to help me.