2019-02-18 06:50 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000012Cheat Enginepublic2007-09-19 07:28
Assigned ToDark Byte 
Summary0000012: "Copying memory" on pointer scanner
DescriptionI found it annoying that the default pointer scanner always has to copy memory between 2 consecutive searches. Say I want to find a pointer, sure - let it copy the memory and scan withing the copied data. But if I find no results for level 1, and want to scan for a level 2 pointer, why does it have to copy the memory again? It's annoying for people with low amount of RAM :( Like me...

Hope there is something to be done about it?! Thanks in advance!
TagsNo tags attached.
Attached Files




Dark Byte (developer)

The 2nd scan actually does free the old memory before starting the new one, but I guess if memory fragmentation happens the 2nd one probably wouldn't be able to allocate 1.5GB again

I guess I could add a checkbox to 'reuse' a buffer if you like, but keep in mind that all pointers may not have changed since the first scan.

e.g during scan the game got closed, that doesn't matter to the scan since the copy it uses, and you now restarted it and are now looking for a pointer to a new address. The copy still only contains all addresses of before the game was restarted, so that address you're scanning may then not even exist.
But if you're sure, I can add a checkbox you can tick when scanning


SunBeam (reporter)

Please do so and thank you. Am aware of all the consequences it involves, and won't ask dumb, retarded questions such as "why does that happen?" :) Thanks for the clarification...

P.S.: Am using same memory, only to scan higher leveled pointers (e.g.: didn't find any on level 1 scan, and want to scan for level 2 pointers - same memory, game didn't close, just another scan...)


Dark Byte (developer)

it now contains a option to reuse the copy.
Also, fixed a bug where at the end of the scan, it didn't free the memory. (used to only free it on a new scan)

-Issue History
Date Modified Username Field Change
2007-09-15 14:12 SunBeam New Issue
2007-09-15 18:25 Dark Byte Status new => assigned
2007-09-15 18:25 Dark Byte Assigned To => Dark Byte
2007-09-15 18:32 Dark Byte Note Added: 0000016
2007-09-15 18:32 Dark Byte Status assigned => confirmed
2007-09-16 23:08 SunBeam Note Added: 0000019
2007-09-19 07:28 Dark Byte Status confirmed => resolved
2007-09-19 07:28 Dark Byte Resolution open => fixed
2007-09-19 07:28 Dark Byte Note Added: 0000020
+Issue History