You press a button once and the game jumps twice. You map a key in AntiMicroX and the character also performs the game’s native controller action. That doubling is the classic sign that two input translators are working at the same time: Steam Input is remapping your controller for the game while AntiMicroX is also sending keyboard and mouse output for the same presses. Neither program is malfunctioning — they are both doing their jobs on top of each other. This post explains the overlap and how to give each game exactly one input path. It expands on the Steam section of our general troubleshooting guide.
Why double inputs happen
Think of the chain. Your physical press can reach a game through several routes: directly as a controller, through Steam Input as a translated controller or keyboard action, and through AntiMicroX as a keyboard or mouse action. If Steam Input is enabled for a game and AntiMicroX is also active with a loaded profile, a single press can produce the native controller action and the mapped key at the same time. Menus that scroll twice, characters that jump and interact simultaneously, and screenshots taken when you meant to pause are all typical fingerprints. The fix is conceptual before it is technical: for each game, decide whether Steam Input or AntiMicroX owns the translation, and turn the other path off for that game. Leaving both on and trying to tune around the doubling rarely works, because the doubling is structural, not a sensitivity problem.
Choosing per game in Steam
Steam lets you manage Steam Input per game, which is the right granularity. For a game where you want AntiMicroX mappings — for example a title with no native controller support — open that game’s controller settings in Steam and disable Steam Input for it, then test with only AntiMicroX active. For a game with good native controller support that you enjoy as-is, do the opposite: keep Steam Input or native support, and do not load an AntiMicroX profile for that game, or quit AntiMicroX before playing it. A global, all-or-nothing setting creates new problems every time you switch genres. Also remember the desktop side: Steam can apply a desktop configuration to the controller outside games, which can make AntiMicroX testing on the desktop confusing. If the pad behaves oddly in menus before any game starts, check what Steam is doing in the background, or close Steam entirely for one clean AntiMicroX test.
Detection problems caused by the same overlap
Steam involvement can also sit behind a controller that seems missing. When another program presents a virtual controller or holds the physical device in a particular mode, AntiMicroX may list something unexpected or nothing at all. If detection is your symptom, work through our dedicated checks for a controller AntiMicroX is not detecting, with Steam fully closed as one of the isolation tests. Keep the experiments separate: first prove AntiMicroX sees the pad and sends correct output on the desktop with Steam closed, then reintroduce Steam and the game and change only the per-game Steam Input setting. Changing AntiMicroX profiles, Steam settings and in-game bindings in the same session makes the result impossible to interpret.
A clean setup routine you can reuse
Use this routine for every new game. One: quit AntiMicroX and set the game up the way Steam and its native support intend, and play briefly to know the baseline. Two: decide what AntiMicroX would add — keyboard-only actions, mouse control, macros or accessibility remapping, for example. Three: if AntiMicroX adds something real, disable Steam Input for that game, load your profile, and test each binding in a menu or safe area. Four: save the profile with the game name in it, so future you knows which input path that game uses. You can always get the current build and its profiles workflow from the download page. The goal is not to defeat Steam Input; it is a capable system. The goal is a deliberate choice per game, so one press always means one action.
How to tell which program produced an action
When a press does something unexpected, identify the author before changing settings. Quit AntiMicroX completely, including from the tray, and repeat the press in the same game menu: whatever still happens is produced by Steam Input or the game’s native support. Then close the game, disable AntiMicroX, and test the controller on the desktop with Steam’s desktop configuration in mind, because Steam can act there too. Next, run the game with Steam Input disabled for that title and only AntiMicroX active: whatever happens now is AntiMicroX’s work alone. Comparing those three controlled states is slower than guessing, but it is conclusive, and it usually takes less than ten minutes. Keep a short note per game — native, Steam Input, or AntiMicroX — in the profile name itself, so months later you do not have to repeat the experiment when a game updates or Steam resets a per-game setting after a client update.
Keep exploring
- General AntiMicroX troubleshooting guide — the cluster overview for all common faults.
- Download AntiMicroX 3.6.1 — official GitHub release channel with hash information.
