Home
Welcome to the MemoryEngine360 wiki!
Here you can find in-depth information about how to use this program.
This is a guide on how to get started scanning for values.
Press CTLR + O or click File > Connect to console.... This will open up a dialog for connecting to a console. Select Xbox 360 (XBDM) and click Connect.
XBDM is the recommended for most things, however XDevkit can run First Scan almost twice as fast, but for some reason, is twice as slow when running Next Scan. So pick wisely!
-
Set
Data Typeto the type of value you want to search for. All integer types are signed except for byte which is unsigned. -
When searching for numbers, set the
Compare Modeto what you want. For example, Equals matches if the console value equals the search query, LessThan matches when the console values is less than the search query, and Between gives a result when the console value is between the two search queries.
Here you can specify a start address and also how many bytes you want to read. By default, the start is 0x82600000, which is where most games start at, and the length is 0x1000000 or 16MB.
On supported consoles, click the little green table button to open a dialog, which lets you select a memory region to scan. Games are usually around the 0x82000000 area.
Once you've configured the search options and you've entered the value (or values, when searching between/not between) into the query(ies), click First Scan. This will search the scanning region in the Additional Options panel for values that match your search options.
You'll see results show up in the left panel.
Since the xbox 360's XBDM connection connects via IP, the read process is very slow compared to Cheat Engine. We can only read data at around 0.8~ MB/s.
The status bar will show something like Region a/b (c/d). This means it's processing memory region A out of B, and has read C out of D bytes from the console. It may also say Chunk when Scan Memory Pages is off, since we read in chunks of 64K
Then, once the scan is complete, it may show Updating result list.... This is where it adds the results into the UI at a steady pace to prevent the UI freezing (rate of about 2000/s (system performance dependent)). It shows how many results are pending at the top.
You can cancel the activity once it shows
Updating results list, and the rows become 'Hidden', but they will still be processed next scan along with the rows in the UI.
This reads the values of all your current results and compares them to your search query(ies) again, and removes any that do not match.
For example, you run First and Next scan for "25" (say it's an ammo count), but after first scan, you shot rounds, so the value became 22, and therefore won't show up in the next scan as you're searching for 25.
There are 2 buttons First and Prev next to the value field. These toggle whether to use the scan results' First Value or Previous Value as a search value, instead of using the search query.
For example, say you want to find results whose values changed relative to the previous scan (includes first and all subsequent next scans), Select Prev and set the Scan Type to NotEqual
This clears all search results, allowing you to run First Scan again.