If you play more than one game with AntiMicroX, you know the small ritual: open the program, load the right profile, confirm it, then start the game. Auto Profiles remove that ritual by watching which application window is active and loading the profile you associated with that application. AntiMicroX can also load your most recently used profile on startup, which pairs naturally with automatic switching during a session. This guide explains how Auto Profiles work in version 3.6.1, how to associate profiles with games step by step, how to test that the correct layout really loaded, and the one limitation you must know before you begin: Auto Profiles do not work on Wayland, a fact the project documents itself. Everything here builds on having good saved profiles in the first place, so if your .amgp files are not yet organised, start with creating and saving profiles and the overview on the profiles page, then return and automate the loading you are currently doing by hand.
How Auto Profiles work
The idea is an association table. For each application you care about, you tell AntiMicroX which saved profile belongs to it. While AntiMicroX runs, it watches the active window, and when a window belonging to an associated application becomes active, it loads that application’s profile. Switch to a different associated game and the profile switches with you; return to the desktop or an unassociated application and you are back to whatever default behaviour you configured. This is per-application automation, not per-game magic: AntiMicroX knows windows and applications, not the internal state of your games. It cannot tell a menu screen from gameplay, which is why Sets exist for differences inside one game. The division of labour is clean — Auto Profiles choose the right file for the application, and the Sets inside that file handle variations within it. Understanding that boundary prevents the classic disappointment of expecting automatic loading to solve a problem that is actually about layouts inside a single game, and it tells you exactly which feature to reach for when something needs to change automatically.
Set up Auto Profiles step by step
Begin with finished, named profiles saved on disk for each game; automatic loading can only load files that exist and already work when loaded manually. With AntiMicroX running, open the Auto Profile settings and add an association: choose the application, using its running window where the interface offers that route, and point it at the saved .amgp file for that game. Add one association only, and test it before adding the next. Start the associated game, switch focus to it, and verify the profile changed by pressing a button whose assignment is unique to that game’s layout. Then switch away and back, confirming the change repeats reliably rather than happening once by luck. Only after the first association survives that test should you add the second game, and repeat the same test. Adding ten associations before testing any of them is how users end up with a table full of near-misses and no idea which entry is wrong. One at a time feels slower and finishes faster, because every new entry is tested against a base you have already proven.
- Prepare named, manually tested .amgp profiles first.
- Add one application association at a time.
- Verify with a button unique to that game’s profile.
- Repeat the switch-away-and-back test before adding more games.
The Wayland limitation, stated plainly
Auto Profiles do not work on Wayland. That is not a rumour or a configuration problem on your machine; it is a limitation the project itself documents, added to the release notes in version 3.5.1 and stated in the project README alongside the feature. The underlying reason is that Wayland restricts how applications can observe other windows, which is exactly the information automatic profile switching depends on. If you run a Wayland session on Linux, plan your workflow around manual loading: launch AntiMicroX, load the named profile, do the one-button confirmation test, then launch the game. On X.org sessions and on Windows, Auto Profiles work as described in this guide. Do not spend hours troubleshooting a Wayland setup as though the feature were broken, and be suspicious of any advice promising a simple toggle that restores it. Our AntiMicroX on Linux guide covers the platform picture more broadly, including the other installation and session details that matter there. Knowing a limitation in advance is what documentation is for: it turns a potential afternoon of frustration into a ten-second decision about how you will load profiles on that machine.
Startup behaviour and the default profile
AntiMicroX can automatically load the last used profile when it starts, and it is worth deciding deliberately whether that helps you. On a machine mostly used for one game, loading the last profile at startup means the correct layout is often already active before you touch anything. On a shared or multi-game machine, the last profile is just as often the wrong one, carried over from whoever played previously — which is why the confirmation habit still matters even with automation enabled. Think through what should happen in the gaps between associated applications, too: when you are on the desktop between games, which profile do you want live? A neutral desktop profile, perhaps with mouse control on a stick, is a sensible answer for many users, and our controller-as-mouse guide shows how to build one. The goal of all this automation is not maximum cleverness; it is that the active profile is boringly predictable at every moment. If you ever find yourself unsure which layout is live, the system needs simplifying, not expanding — reduce associations to the games you actually rotate between, and let the rest load manually.
Troubleshooting automatic loading
When Auto Profiles misbehave, work through three checks in order. First, is the profile itself correct? Load it manually and play: if the layout is wrong manually, automatic loading is faithfully loading a wrong file, and the fix belongs in the profile, not the automation. Second, is the association pointing at the application and file you think it is? Recheck the entry character by character, especially after moving profile files to a new folder, because an association to a moved or renamed .amgp cannot load what is no longer there. Third, is the session one where the feature can work at all? A Wayland session explains total non-function in one step, and no setting change will alter it. Window-matching quirks — a launcher window versus the game window, for example — are handled by associating the window that is actually active during play, which you discover by switching to the running game and observing which application AntiMicroX sees. Keep associations few, profiles named clearly, and tests based on unique button assignments, and automatic loading becomes what it should be: invisible infrastructure you set up once and then stop thinking about.
