ROG Ally X controller mapping is handled mainly in Armoury Crate SE: the 2024 RC72LA offers system-level Gamepad and Desktop control modes as well as game-specific profiles. The goal is to identify which input layer owns the buttons before assigning actions, because Steam Input and games can also remap controls. If a button works on the desktop but not inside a game, check the active Armoury Crate profile, Steam Input settings, and the game’s own bindings in that order. This prevents two mapping tools from competing for the same press.
Three mapping layers and why they can conflict
The Armoury Crate SE layer maps the handheld’s physical controls to gamepad, keyboard, mouse and shortcuts. It can use Gamepad Mode, Desktop Mode, and Auto switching when enabled. A Game Profile can override global preferences for one title. Separately, Steam Input may transform a detected controller into a game’s desired input scheme. Finally, many games expose their own binds and controller layouts. Change one layer at a time; stacking a keyboard bind over a Steam virtual controller can yield duplicate inputs or confusing button prompts.
| Symptom | Likely layer | First check |
|---|---|---|
| Face buttons act like keyboard keys in a controller game | Armoury control mode | Switch to Gamepad Mode and retest |
| Touchpad-like mouse motion or unexpected cursor | Desktop configuration / gyro | Check Desktop Mode and gyro mapping |
| One Steam game ignores a back-button shortcut | Steam Input or game profile | Compare game-specific settings with global |
| A and B appear reversed | Platform-specific game setting or layout | Check game’s controller prompts before physical remap |
| Buttons trigger twice | Multiple active mapping layers | Disable one override and test again |
Set up a reliable baseline
- Update Armoury Crate SE through its own Settings > Update Center; restart if prompted. ASUS’s current introduction applies to ROG Ally X (2024) RC72LA, although its illustrations may include other Ally generations.
- Launch Armoury Crate SE using the dedicated hardware shortcut. Open Settings > Control Mode and inspect Gamepad Mode and Desktop Mode configurations. Select Gamepad Mode for a game with built-in controller support.
- Open the button assignments and identify Primary Button and Secondary Function for each assignable control. ASUS documents that a secondary function can be invoked with a rear paddle acting as a modifier, depending on the chosen mapping.
- Test Start, Menu, the face buttons, bumpers, triggers and sticks in a gamepad-friendly title. Do not assign two incompatible actions to the same input while building a baseline.
- Save the global layout. Only afterward create a Game Profile for a game with unusual keyboard-only commands or a launcher that needs a mouse click.
The two back buttons are not automatically two new buttons recognizable by every game. Mapping them to keyboard or gamepad commands through the supported configuration is often necessary. If a multiplayer game prohibits macros or automation, do not use repeated-input functions to evade its rules.
Create a per-game controller profile
Open the target game in Armoury Crate SE Game Library and use its Game Profile control. ASUS documentation identifies the X shortcut from a selected game for access to profile-related operations, although version and screen arrangement can vary. Assign game-specific functions such as a rear paddle for a frequently used menu or an action that otherwise requires an awkward chord. Launch the game normally and verify the assignments in an interactive area rather than assuming that a saved profile has loaded.
If the game is distributed through Steam, open Steam > Library > [game] > controller settings and check whether Steam Input is enabled, disabled or using a community layout. A game with native XInput support may behave best with a basic Xbox-style mapping rather than a complex Steam Input layout. For keyboard-only titles, mapping a few keys in Armoury or Steam Input can be useful, but don’t simultaneously configure both layers with competing actions.
Sticks, dead zones, triggers and gyro are separate controls
Under the current ASUS Armoury Crate SE menu, Control Mode > Configure contains stick and trigger configuration, including inner dead zone and outer threshold. Too large a dead zone sacrifices precise aiming; too small one can reveal harmless sensor noise or real drift. Anti-deadzone changes the early response and is not a hardware repair. Start at vendor defaults and adjust only after testing in a neutral calibration view.
The Gyro mapping can emulate mouse or stick movement where offered; this does not mean every game natively supports gyroscopic aiming. For games with controller-only menus, gyro-as-right-stick may be more practical than gyro-as-mouse, but mixed-input games can switch UI prompts repeatedly. Use a hold-to-enable control for aim-down-sights when a constant moving cursor would be distracting.
Diagnose mapping that changes or disappears
Check the active control mode, current Game Profile, whether a Steam community layout loaded, and whether the game changed from controller to keyboard/mouse input. Disconnect an external controller, keyboard or dock temporarily. In Windows Settings > Bluetooth & devices, inspect whether Windows sees an unexpected additional game controller. Do not uninstall a system HID device indiscriminately; some entries support built-in buttons and sensors.
If a back-button action stops after an update, check the ASUS Update Center and the RC72LA firmware history rather than downloading a generic driver for the 2025 Xbox Ally X. ASUS’s official RC72LA download page documents MCU firmware fixes affecting button behavior; driver and firmware packages are model-specific.
Check controller input across mapping layers
Armoury Crate SE: Free ASUS application for global and game-specific mapping. Steam Input: Free with Steam for per-game controller layouts, when used instead of conflicting simultaneous remaps. Windows Game Controllers test (joy.cpl): Built-in diagnostic surface for some XInput/HID paths; not every handheld virtual controller appears identically.
Check when a game-specific profile actually takes control
ASUS distinguishes the default Gamepad/Desktop control modes from Auto behavior. In Auto, the focused title can load the matching Armoury Crate SE Game Profile; for a game without a custom profile in the library, ASUS documents a default Gamepad Mode path. This gives a useful diagnostic: keep the Command Center visible, launch one library title and one non-library application, and compare the selected control mode after focus changes. If a remap works on the desktop but disappears in the game, check the active profile before rebuilding the global layout. A rear paddle set as a secondary-function modifier is not the same as a separately exposed gamepad button: the secondary assignment may require holding that paddle while pressing the mapped face button. Verify this chord in a harmless test screen before assuming the game ignored input.
Check a rear-button modifier before blaming the game
ASUS documents that the M1 and M2 rear buttons are secondary-function modifiers by default, rather than additional independent XInput buttons. A secondary mapping may require holding a rear button while pressing the mapped front control; pressing M1 or M2 alone therefore may not register as a new button in a game. For a reproducible test on the 2024 RC72LA, switch Command Center Control Mode to Auto before opening Armoury Crate SE > Settings > Control Mode > Configure, choose the mode to edit, and inspect Primary Button versus Secondary Function for the affected control. Test the combination in a text field or game training area, then verify whether a per-game profile overrides it. ASUS lists the Command Center, Armoury Crate, volume and power keys among controls that cannot be remapped; do not recommend firmware flashing to unlock those keys.
Use a single button as a mapping-layer diagnostic
Choose a harmless button such as one rear paddle and assign it to a distinctive keyboard key in the active Armoury Crate game profile. In the Windows desktop or a text field where key entry is safe, confirm that only one keystroke arrives. Launch the game and compare its binding display with the Steam Input configuration. If the same press invokes two actions, disable the redundant layer before editing the in-game binding. Keep an unmodified default profile ready as the rollback.
Write the active ACSE version, controller mode (Gamepad or Desktop), per-game profile name, Steam Input enabled/disabled state and the final in-game action on one line. A rear-button chord that works in Desktop mode but fails in a game is not proof of bad hardware: the game can load a different Armoury Crate profile and Steam can translate the virtual controller again.
Keep each game on one mapping layer
Use a plain Gamepad Mode as your reference, build one per-game override at a time, and inspect Steam Input only when a Steam title behaves differently. Controller mapping fixes input translation; it does not calibrate faulty sensors or repair physical stick drift. That separation prevents most unnecessary driver reinstalls and keeps your layout portable across games.
