How to Create, Save and Load an AntiMicroX Profile (.amgp)

A profile is where all of your AntiMicroX work actually lives. The program itself only provides the engine; the profile stores which button sends which key, how your sticks behave, which of the eight Sets you are using and how your controller was calibrated. AntiMicroX profiles are saved as .amgp files, and learning to create, save, load and organise them properly is the difference between a tool you set up once and a tool you fight every session. This guide covers the full workflow for version 3.6.1 on Linux and Windows: what a profile contains, how to build your first one in a sensible order, how to save and name it so you can find it in six months, how loading works, and how Auto Profiles can load the right file for each game automatically. For the broader picture of what profiles can hold, see our overview of AntiMicroX profiles, and get the program itself from the download page if you have not installed it yet.

What a profile contains

One .amgp profile contains the complete assignment layout for a controller: every button, trigger, D-pad direction and stick direction, and what each one sends — a keyboard key, a mouse button or movement, a script or executable, or a macro. It also contains up to eight Sets, which are eight full layouts inside the same profile, so a single file can hold, for example, a driving layout, an on-foot layout and a menu layout for the same game. Stick behaviour such as deadzones belongs to the profile too, as does calibration data; support for storing calibration for multiple controllers in a profile was added back in version 3.2.5, which matters if you rotate between two different gamepads. When you open a different profile, you get that profile’s deadzones, Sets and calibration as well as its button map, because all of it was saved together in the one file.

Create a profile in a sensible order

Start with the controller connected and responding in the main window, then work through assignments in the order you will test them. First map the controls the game cannot function without: movement, confirm, cancel and one or two main actions. Save the profile at that point, even though it is unfinished, and give it its real name straight away. Next, add the secondary actions and menu controls, testing each group before moving on. Leave sticks until the main buttons work, then set deadzones conservatively: 8000 is the typical XInput profile value noted in project guidance, and around 2000 was suggested from the author’s experience with a Logitech F310, so start within that kind of range and adjust for drift or responsiveness on your own hardware. Finally, add anything advanced — macros, advanced slots or extra Sets — only after the plain layout has survived a real play session. Features layered onto an untested base are much harder to debug than features added one at a time.

  • Save early with the profile’s real name, then keep saving as you build.
  • Core actions first, secondary actions second, sticks and deadzones third.
  • Advanced slots, macros and extra Sets last, one feature at a time.
  • Test each group of assignments before adding the next group.

Save and name profiles so you can find them

Use names that answer three questions at a glance: which game, which controller, and which variant. A name built from those three parts stays meaningful when your collection grows to dozens of files, while names like test2 or new-profile become useless within a week. Keep your .amgp files in one folder you control and include that folder in whatever backup routine you already use, because profiles represent hours of tuning that an uninstall or a system reinstall should never take with them. The program files themselves can always be downloaded again in minutes; your tuned deadzones and carefully arranged Sets cannot. If you use both the Windows installer and the portable build, or both a Linux package and an AppImage, remember that profiles are just files on disk: the same .amgp can be loaded by any of them, which makes one shared profile folder the simplest way to keep your layouts consistent across machines. Treat a finished profile the way you would treat a saved game — it is small, personal and far more valuable than its file size suggests.

Load a profile and confirm it is active

Loading is the reverse of saving: open the saved .amgp file through AntiMicroX and the layout it contains replaces the current assignments. Always confirm the load actually happened before you start a game. Press a button whose assignment differs between your profiles and watch the response, or check a distinctive deadzone or Set; assuming a profile loaded because you clicked the right menu is how players end up blaming a game for a layout that was never active. AntiMicroX can also reload your most recently used profile on startup, which is convenient on a single-game machine and confusing on a shared one, so know whether that behaviour is what you want. If you switch between games manually, build a simple habit: launch AntiMicroX, load the named profile for the game, do the one-button confirmation test, then launch the game. When manual loading starts to feel repetitive because you play several games in rotation, that is the right moment to set up automatic loading, which the next section covers.

Reuse a good profile instead of starting over

Most games in the same genre need nearly the same layout. The fastest way to create a profile for a new game is to load your best existing profile for a similar game, save it under the new game’s name first, and then edit the copy. Saving under the new name before editing is the important step: it guarantees your changes land in the new file and your proven original stays untouched. Keep one deliberately simple profile as your personal template, containing the stick settings, deadzones and basic arrangement you prefer, with only the game-specific actions left to fill in. Over time this template approach compounds: every improvement you discover — a better deadzone, a more comfortable arrangement — can be folded back into the template so the next profile starts from a better base. This is also the honest way to use profiles shared by other players. A downloaded or shared .amgp is a starting point to inspect and adapt, not a promise that someone else’s deadzones and taste will suit your controller and hands.

Let Auto Profiles load the right file for you

Auto Profiles watch which application window is active and load the profile you associated with that application, and AntiMicroX can also associate profiles so the correct layout follows the program you are using rather than the last one you loaded manually. Set it up one game at a time: associate the game’s window with its saved profile, switch to the game, and confirm the layout changed, using the same one-button test as manual loading. The important limitation, documented by the project itself, is that Auto Profiles do not work on Wayland. On a Wayland session you should plan on manual loading and not troubleshoot automatic loading as if it were broken; on X.org and on Windows the feature works as described. Our dedicated guide to AntiMicroX Auto Profiles goes deeper into setup and window matching. Combined with Sets inside each profile, Auto Profiles complete the system: the right file loads for the game, and the right Set inside that file handles each situation within the game, with no rebuilding in between.

Similar Posts