Cheat Engine

HalfPrime

Say I've got a game that takes 6 megs in memory. What would be the best size to read it at? I know the bigger the better because you shouldn't call that API a million times, but I dont know if I should read all 6 megs at once, either. I was thinking 500K-1M at a time, but I have no idea.

atom0s · Posted: Sun Jun 01, 2008 4:14 pm Post subject:

Uh.. what do you need to read for? Care to be a bit more specific on the actual purpose? Surprised

HalfPrime · Posted: Sun Jun 01, 2008 4:17 pm Post subject:

Trying to make a CE type thing in C++

atom0s · Posted: Sun Jun 01, 2008 4:32 pm Post subject:

Dump in parts based on the memory regions? Would be more efficient I would say to scan chunks inside threads. Just my suggestion, I'm sure others will follow with their own.

HalfPrime · Posted: Sun Jun 01, 2008 4:34 pm Post subject:

rofl, hivemind. I just finished up my EnumProcessModules code. But the problem is, some of the modules are huge and I don't know if I should read the entire module or break it up.

atom0s · Posted: Sun Jun 01, 2008 4:40 pm Post subject:

Dumping a full module doesn't really take that long. I use my sigScan DLL for a prog that dumps a 2.5MB DLL from memory to scan for signatures and it can complete the task for all of the signatures I scan for within about 1-2 seconds. (It's not programmed for efficiency either as it dumps each time it scans for a new signature.)

I wouldn't think it would be an issue for anything bigger either. Of course the bigger the DLL the more space and such will be needed and speed will start to be effected but I would say it would probably be fine.

Just test it out and see how it performs with the full dumps, if not, then possibly divide into chunks based on the size.

HalfPrime · Posted: Sun Jun 01, 2008 4:58 pm Post subject:

Alright, I'll try different sizes. I was mostly worried about an effect on speed when my program has 6 megs allocated to it.