Cheat Engine

iPromise · Posted: Thu May 12, 2011 10:37 am Post subject: MEMORY.TMP

I noticed that CE writes to a disc file for its scans. I was testing CE and its how it preformed its unknown initial value scans. It preformed them simularly to mine, I write to a disc file to record my results and then I check those results to see if any values have changed. (Check out my other topic to get a further elaboration on how I do my UIV scans and what my problem is).

I attached CE to itself, and did a UIV scan, CE recorded more than 23,000,000+ results in just half a second. How? How does CE do that, how does CE write to the buffer so fast? My problem is that the buffer becomes too big and records to much results.

I am trying to read the source code but I don't undestand delphi so i'm having trouble there.

Please, any help on how it writes that fast can fix my problems so I can finally release a final good copy of my memory engine.

Krähne · Posted: Thu May 12, 2011 11:57 am Post subject:

Why did you not make it virtual?... i mean, without the temp file.

I guess, in the virtual memory would be more faster. (by the garbage collector (?)).

NoMercy · Posted: Thu May 12, 2011 12:35 pm Post subject:

Krähne · Posted: Thu May 12, 2011 2:02 pm Post subject:

Dark Byte · Posted: Thu May 12, 2011 3:20 pm Post subject:

Ce doesn't write the memory to disk immediately, it first copies the target process's memory to it's own region, and then returns control to the user telling it's done.

Then it starts a low priority thread that saves that memory to disk so it can be used with "same as first scan" later on.
The user then goes to the game and does stuff, and then comes back and does a next scan. That will then increase the priority of the saving thread, wait for it, and then does the next scan (and usually the time between the first scan and next scan is long enough to not get noticed, except on a few slower systems)

(In short, I cheat! The scan isn't really complete when it's done, but it's done enough as in, the memory changes won't make an effect)

Also, ce doesn't save it as address1-memory1, address2-memory2, but as:
address-size
address-size

and another file containing the raw copy of the memory
It's best to write a few big chunks instead of a million small chunks

iPromise · Posted: Fri May 13, 2011 10:45 am Post subject:

Dark Byte · Posted: Fri May 13, 2011 12:01 pm Post subject:

Memory.tmp would just hold a direct copy of the target process's memory and wouldn't even know what type was used. Only for next scan

addresses.tmp holds the description of the memory regions so a next scan can read through the memory file and if it encounters something, use addresses.tmp to look up what the virtual address for it is