LimitlessDocs

Create an MMAP with RAMMap

Make a memory map from your gaming PC and convert it to mmap.txt in your browser.

An MMAP tells the cheat where your gaming PC's RAM is mapped. It contains address ranges, not a memory dump.

If your cheat already works, you don't need to make one. Use a custom MMAP for memory-map errors or when support asks for it. It won't fix a bad USB cable, an expired key, or a cheat that's down for an update.

Save your .RMP file#

  1. Download RAMMap from the official Microsoft page and extract it.
  2. Run RAMMap64.exe on the gaming PC, not the second PC. Approve the administrator prompt if Windows asks.
  3. Open Physical Ranges.
  4. Select File → Save and save the .RMP somewhere easy to find.
  5. Select it below and compare the result with RAMMap before downloading.

Keep the original .RMP private. It can contain process names and file paths. This page converts it locally and does not upload the snapshot.

Convert to mmap.txt#

Turn your RAMMap .RMP file into mmap.txt.

Your file stays in your browser. Nothing is uploaded or saved by this page.

RMP import is experimental. It has not been tested with a real RAMMap export yet.

Choose a file to get started.

Paste ranges instead

Copy Start and End from RAMMap’s Physical Ranges tab. Put one pair of hex addresses on each line.

Use your gaming PC’s ranges, not its RAM size or someone else’s map.

File format details

The importer accepts RAMMap XML 1.0 for amd64, with range versions 1 or 2. Other formats are rejected. The output uses start and inclusive end addresses in hex.

Check the generated file#

  1. Compare the Start addresses and Size values with RAMMap. Gaps should stay gaps.
  2. Download mmap.txt and show file extensions in File Explorer. Check that it is not mmap.txt.txt.
  3. Move the text file to your second PC if that is where the DMA cheat runs.

RAMMap's End is the first address after a range. The text file uses the last byte inside it, so that value is one lower. Do not change it back.

Rust DMA: where the map goes#

Rust DMA looks for this file on the second PC:

%APPDATA%\LimitlessDMA\mmap.txt
  1. Close the Rust cheat.
  2. Back up any existing mmap.txt in that folder.
  3. Copy the checked map into the folder, keeping the exact filename.
  4. Load Rust again and check the map path in the log.

The log says Using existing memory map from when it finds the file. It can still fall back to loading without a map if that attempt fails, so a working cheat alone does not confirm your map was used. If the folder contains -mmap.txt or -mmap, that is a deliberate no-map override; do not remove it without checking why it was added.

Apex DMA handles its map differently#

Apex DMA deletes its temporary mmap.txt at startup and then creates a new map. Replacing that file by hand won't make it a permanent custom map. Do not use Rust's folder for Apex.

Paths can differ between releases. Follow the path printed by your cheat; send that log and your loader version to support if it differs. CS2's manual-map location has not been confirmed.

The file won't convert#

If your file is rejected, use Paste ranges instead: copy each Start and End pair from Physical Ranges, one pair per line. Leave the end selector on the RAMMap option.

Loading still fails#

Run the DMA test and keep the first error. Capture a new map when RAM or firmware changes alter the gaming PC's address layout; another PC's map is not a replacement.

Use the support checklist. Send the text map only when needed, not the full snapshot.

Limitless Docs