Understanding Controller Setup: LaunchBox, Big Box, and Emulators

A controller can work in one part of your setup and fail in another because several independent systems handle input. Windows detects the device; LaunchBox and Big Box use their own front-end mappings; and each emulator or native game controls gameplay. Pause, exit, and focus actions add another layer.

🧱 The six control layers

1. The physical controller

The connection method, battery, firmware, hardware mode, and any device-specific switch determine what the controller presents to Windows. Some controllers can operate in more than one mode, such as XInput or DirectInput.

2. Windows and input-routing software

Windows must detect the controller before LaunchBox, Big Box, or an emulator can use it. Steam Input, a Steam Desktop Layout, DS4Windows, Joy2Key, Xpadder, InputMapper, and similar tools can translate one physical input into keyboard input or a virtual controller.

3. LaunchBox Desktop

LaunchBox Desktop has its own game-controller device settings and mappings for navigating the desktop interface. These settings do not configure gameplay controls inside an emulator.

4. Big Box

Big Box has separate settings for the controller device and for front-end actions such as Navigate Up, Select, Back, and View System Menu. These mappings do not replace the LaunchBox Desktop mappings and do not assign emulator controls.

5. The emulator or native game

The emulator or game decides which device is Player 1, which virtual console button each physical control represents, and which hotkeys it uses. Different emulators, and sometimes different systems within one emulator, can require different input profiles.

6. Pause, exit, and focus automation

LaunchBox and Big Box can watch for mapped controls while a game is running and invoke actions such as Show Pause Screen, Close the Active Window, or Show LaunchBox. Whether pause and exit work cleanly depends on the emulator profile, its running script or integration, and the behavior of the launched application.

✅ Configure the layers in this order

1. Confirm the controller works in Windows.

2. Configure and test gameplay directly in one emulator or native game.

3. Launch the same game from LaunchBox and retest gameplay.

4. Configure LaunchBox Desktop navigation if you want to control the desktop interface.

5. Configure Big Box navigation.

6. Configure and test pause, exit, and focus behavior.

7. Repeat the emulator test for each emulator family you use.

This sequence makes it much easier to identify which layer is responsible when something stops working.

🪟 1. Test the controller in Windows

• Connect or pair the controller and confirm it appears as the expected device.

• Press Windows key + R, enter joy.cpl, and use the controller's Properties page to test buttons and axes.

• Disconnect extra controllers while troubleshooting.

• If applicable, note whether the controller is in XInput, DirectInput, Switch, or another hardware mode.

If Windows does not receive the correct input, fix the connection, pairing, driver, firmware, or controller mode before changing LaunchBox or emulator settings.

🎮 2. Configure gameplay in the emulator

Open the emulator outside LaunchBox. Select the intended input backend and device, assign Player 1 and any additional players, map the system's controls, and save the emulator's profile. Then load a game directly in that emulator and test it.

If gameplay fails when the emulator is opened directly, the problem is not a LaunchBox or Big Box navigation mapping.

🖥️ 3. Configure LaunchBox Desktop controls

In LaunchBox, go to Tools > Options > Game Controllers.

• Enable Game Controllers allows LaunchBox Desktop to receive controller input.

• Use All Attached Controllers allows any attached controller to control LaunchBox Desktop; otherwise, choose one device.

• Open Game Controllers > Mappings to review LaunchBox Desktop actions.

Test navigation and selection in LaunchBox, then launch the game from LaunchBox and verify that its gameplay controls still work. LaunchBox Desktop's controller settings do not change player assignments inside the emulator.

📺 4. Configure Big Box controls

In Big Box, open the System Menu, then use:

• Options > Controller for Enable Game Controllers, Use All Controllers, and the selected Device.

• Options > Controller Mappings for Big Box actions.

Use All Controllers means Big Box listens to all attached controllers for its own mapped actions. It does not combine controllers into one emulator player, choose player order, or configure gameplay. If you want only one device to navigate Big Box, leave it off and select that device.

For a detailed mapping walkthrough and cabinet recommendations, see Setting Up Keyboard and Controller Controls. This guide stays focused on how the layers relate.

⏸️ 5. Separate the three kinds of pause

• A game's native pause button opens that game's own pause menu.

• An emulator pause hotkey pauses the emulator using the emulator's input system.

• Big Box's Show Pause Screen mapping requests the LaunchBox/Big Box pause screen while a game is running.

These are not interchangeable. The pause screen and its available actions depend on the game and emulator profile, and you should confirm that gameplay actually pauses behind it. Avoid assigning the same button or combination to conflicting in-game, emulator, and Big Box actions.

🚪 6. Separate exit from focus recovery

In the current Big Box Controller Mappings list, the game-exit automation action is labeled Close the Active Window. It runs the configured exit behavior for the active game or emulator. It is different from Exit, which exits Big Box itself.

Show LaunchBox is a separate focus/recovery action. It can bring the LaunchBox front end forward, but it is not a substitute for closing the emulator and does not guarantee that a lingering game process has ended.

Test the complete result for every emulator or native-game type:

• The intended game or emulator closes.

• No emulator process remains running unexpectedly.

• Big Box becomes the active interface again.

• The same input does not also trigger an in-game or emulator command.

👥 Multiple controllers and player order

Connect controllers in a consistent order, but always verify player assignments inside the emulator. Windows device order can change after reconnecting a controller, changing USB ports, or switching between wired and wireless use.

When troubleshooting, start with one controller and keep Use All Controllers or Use All Attached Controllers off. Add devices one at a time, then test both front-end navigation and emulator player assignments after each change.

⚠️ Why one press can register twice

A double input usually means the same physical press is reaching the front end through two paths. Common causes include:

• Steam's Desktop Layout sends keyboard input while Big Box also reads the controller directly.

• Remapping software exposes both a physical device and a virtual controller.

• A controller-to-keyboard mapping duplicates a direct controller mapping.

• Two connected devices or a cabinet encoder send the same mapped action.

• A noisy or stuck axis repeatedly crosses the navigation threshold.

Use All Controllers does not create duplicate events by itself, but it can reveal a duplicate physical/virtual device or allow a second device to send the same action. Quit Steam and remapping tools temporarily, disconnect extra devices, and reintroduce one input path at a time.

For focused steps, see Double Inputs When Navigating Big Box with a Controller.

🧪 End-to-end test

1. Confirm the controller passes the Windows test.

2. Play a game directly in the emulator.

3. Navigate LaunchBox Desktop, if configured.

4. Open Big Box and navigate without repeated or missed input.

5. Launch the same game and verify every gameplay control.

6. Open and close the intended pause screen.

7. Use Close the Active Window and confirm that the emulator closes and Big Box is active again.

8. Restart Big Box, reconnect the controller, and repeat the critical checks.