Weird CE behavior; P -> ???

[erudite]

Hey com,

lately i've been playing around in CE on a new game i found and a weird problem occurred, that i've never seen before.

I did some pointerscans and got promising results. They work absolutely fine until i open the Memory View for the first time. I just need to open and close the Memory View and the Pointers in the Table still work fine until i try to edit the address. Then they suddenly break and it seems like CE can't follow the path anymore.

I got you some screens right here.

Pointers working

 Spoiler

After i've opened and closed the memory view the table still works fine and shows the correct XCor. But if i try to open the Addressview this happens:

 Spoiler

From now on, only a restart can fix it. I can still search for values just fine and edit the found values but i can't add a pointer manually.

Can someone help me? I would be pleased.
Thanks and have a nice day!

[elmarcia]

Originally Posted by erudite

Hey com,

lately i've been playing around in CE on a new game i found and a weird problem occurred, that i've never seen before.

I did some pointerscans and got promising results. They work absolutely fine until i open the Memory View for the first time. I just need to open and close the Memory View and the Pointers in the Table still work fine until i try to edit the address. Then they suddenly break and it seems like CE can't follow the path anymore.

I got you some screens right here.

Pointers working

 Spoiler

After i've opened and closed the memory view the table still works fine and shows the correct XCor. But if i try to open the Addressview this happens:

 Spoiler

From now on, only a restart can fix it. I can still search for values just fine and edit the found values but i can't add a pointer manually.

Can someone help me? I would be pleased.
Thanks and have a nice day!

Try switching between debuggers:


My guess is that the inyected debugger is messing with memory map, but its a guess

Or Update/DownGrade Cheat Engine, maybe its a bug

[erudite]

Originally Posted by elmarcia

Try switching between debuggers:


My guess is that the inyected debugger is messing with memory map, but its a guess

Or Update/DownGrade Cheat Engine, maybe its a bug

I thought about that too, but the debugger is not attached at all, so this shouldn't effect CE following the Pointerpath.

I will absolutely try some older versions of CE. I tried 7.1 and 7.2, as well as 6.8 and the error occurred with all of them.

Thank you very much for your reply!
Greetings