-
Notifications
You must be signed in to change notification settings - Fork 4
Connecting to a console
Click File > Connect to console... or press CTRL+O. It will open up a dialog for connecting to a console. By default, XBDM is selected.

-
XBDM uses the Xbox Debug Monitor's command system. It provides the most features that Memory Engine uses and is well tested, but seems slightly slower than XDevkit when reading values
-
XDevkit uses COM objects, implemented by
xbdm.dllwhich you get when you install Xbox 360 neighbourhood. This connection provides less remote commands but is significantly faster when scanning values. It's slower when running a next scan however.
There's also a debug-only connection type only available when the debugger is attached, which lets you treat a file as a console. If you attempt to write to it, it will enlarge the file to the write address, which is quite bad because if you write an integer to 0xFFFFFFFB, that file will become 4.29 gigs.
Most likely, it will just be an IP address
Memory Engine is designed to be pretty flexible. It allows you to register any number of connection types, e.g. for a PS3. So feel free to try writing one for yourself! See MemEngine360.Xbox360XBDM for examples.
-
Home
- Connect to a console
- Scanning Options
- Scan results & Saved Address Table
- Remote Commands
- Memory Dump
- Tools
- Preferences/App Settings
-
API
- Making a custom connection
- Busy Tokens
- Models, ViewStates, MVP & Binding
- Plugins
- Config Pages
- Brushes and Icons
- Data Manager, Context Data and Data Keys
- Commands and Shortcuts
- Context Menus
- Windows and Dialogs