Controllers & launcher navigation

GBAx uses input in two places: the launcher interface and the running emulator. A controller can browse your collection, launch a game and open the quick menu, while the emulator maps its buttons to the GBA controls. Testing both layers prevents a common confusion: being able to select a cover does not prove that every in-game button is mapped correctly.

Connect and identify the controller

Connect the controller before starting your first test. If it can use both USB and Bluetooth, begin with the connection you intend to use regularly and record it when reporting a problem. Different connections or device modes can expose different button and axis identities to the operating system.

Open Settings → Open Emulator Settings and inspect the input configuration. Use the controller you actually want to play with. A second connected gamepad, steering wheel or virtual controller can complicate the result if the wrong device is selected.

Map the GBA controls deliberately

The console expects A, B, L, R, Start, Select and four directions. Match each one to a physical control that feels comfortable. Controller lettering differs between manufacturers, so use physical position and the response shown by the mapping interface rather than assuming that identical letters always mean identical positions.

Test the result in a game that makes the response obvious. A menu is useful for directions and confirm/back; gameplay may be needed to check shoulder-button actions. Press and release each control separately before testing combinations. This helps identify a stuck axis or an input that is mapped twice.

Launcher shortcuts in the supplied interface

The following shortcuts are shown in the reviewed Preview 1 launcher settings. The notation pairs common Xbox/Nintendo-style and PlayStation-style labels where the interface does so. Check your installed Settings screen if a later build changes them.

These are application-navigation shortcuts, not a complete list of a game’s controls. A game still decides what GBA A, B or a shoulder button does within its own rules.

Use the quick menu as a control checkpoint

Open the quick menu, choose Resume and verify that the game receives input again. Then test Save State and Load State with a disposable test position, so you understand what restoring an earlier snapshot does before relying on it.

If navigation works in the quick menu but the game does not respond, check focus and the in-game mapping. If neither interface reacts, investigate device recognition or connection first. The point of this sequence is to locate the failing layer rather than changing unrelated settings.

Reconnect, fullscreen and focus

After the initial mapping works, test the way you will actually use the app: disconnect and reconnect the controller, enter and leave fullscreen, and switch between the launcher and the game. A connection change can cause a device to be rediscovered, while a window switch can change which interface receives events.

For a stuck direction, release the sticks and compare the D-pad. Check whether another connected input device is providing an axis value. Reassigning a game button will not solve every focus or device-selection issue; change one variable, repeat the same action and record what improved.

Keyboard use and alternative layouts

Keyboard bindings can be reviewed in the emulator settings. Use the bindings shown by your installed build rather than treating a shortcut from another mGBA frontend as a guaranteed GBAx default. Confirm that operating-system shortcuts and other applications are not intercepting a key you intend to use.

If a combination fails only when several keys are held together, try another combination or a controller. Keyboard hardware can limit which simultaneous key presses it reports. That is separate from how the core interprets the GBA’s active-key register.

Browser controls are configured separately

The website uses the web player’s control mapping. Start the player, give it focus and press a button on the connected controller so the browser can recognise activity. Open the player’s controls/settings interface and verify the mapping there.

Desktop launcher shortcuts do not automatically apply inside EmulatorJS. Browser focus, device support and reserved browser/operating-system shortcuts can also change the experience. Export saves before using reloads or storage resets as part of troubleshooting.

What to include in an input report

Include the controller model, USB/Bluetooth connection, operating system, GBAx version and the exact physical control involved. State whether the launcher, quick menu and running game each respond. For a web-player issue, add the browser version and whether the same controller works in the desktop app.

For the implementation behind these steps, read Input & link communication. It follows a host button event through mapping into the register the game reads.