Cheat Engine

[Davethewave]

I've noticed I can pointer scan once, but trying to pointer scan a second time will just sit there and do nothing.. was wondering if it's a known bug?

Also, when I click an address and find what "Reads from" the address instead of what writes, it is slower than "what writes" and often crashes the program I am looking at.

There's also a problem it seems sometimes after I save a pointer table, when I go to open it again later it crashes CE when I move my mouse over it.. I think it has something to do with the tool tips in windows but I'm not sure, because when I click it fast and open it CE doesn't crash, but if I hover over the Pointer table then CE crashes.

Feature Request:
The ability to set many addresses to show up in HEX as a selection/group rather than one by one or an option to set HEX as the default display.

[Dark Byte]

Is it the injected pointerscan option or the default?
And are you using ce5.3?

And reads is known to do that yes, there I have to use software debugging instead of hardware. (it consists out of making the memory inaccessible and when the process accesses it it generates a exception and a code I can use to see if it was a read or write, with hardware debugging I can only see if it was a access or write)

about the pointer table, no idea, never seen that happen. Got a table like that and can you upload it?

and feature:
I guess I forgot to add the grouping to that

[Davethewave]

I am using 5.3, when using the pointer scan option under "Memory View - Tools - Pointer scan" which I think is basic, non injected I scan once and it goes through, once the scan is either complete or I have stopped it and closed the pointer scan window, if I go to scan a second time it will just sit there or sometimes report an exception/crash. While using the injected pointer scan it is similar, I right click an address and scan for a pointer using injection, it scans.. I close the scanner and try a second time but the scan window does not show up, if I close Cheat Engine and reload it, and try again the scan window still does not show up when I press the button that says "injected"

The tables don't always crash CE so it may just be a random error.

Is there any way to find what reads from without crashing when the program accesses it?

[Dark Byte]

No, but I recommend using "find what accesses" instead and use your brain to filter out the writes.

[Davethewave]

OK cool! that's what I started doing, thanks.

Actually, could you make the "find out what reads from this address" work like a filter? Basically when you would press find what reads from this address, it actually only does a "find what writes" then it would "find what accesses" right after and conclude that the extra addresses are reads? I've done this manually but an automated feature would cut down on time.
so the new feature would:
Find out what writes to the address, then find out what accesses.. then filter out the writes and display only the remaining as reads.
I don't know, it may be a bit of coding I can keep doing it manually. Also it may be possible that there may be a different write during the filter process, and it might add a write as a read?