mappingMinor issue

Controller Assigned to the Wrong Player

If the wrong controller moves Player 1, start the game with only the pad you want to use connected. Then check the game's player-join or controller-order settings. A browser's device number is not a universal player assignment. Virtual controllers and keyboard mappings can also make two pads act like one player.

Step 0

Diagnose before you fix

Find out which physical controller produces each visible action before changing player assignments.

Diagnostic tool

Button Test

Connect only the intended pad and confirm its buttons respond. Repeat separately for the other pad. This checks each input source without assuming that the tester's device order matches the game's player order.

Run the button test
Time required
10 minutes
You'll need
  • The affected game and its local multiplayer instructions
  • The controllers you intend to use
  • A note of any virtual-controller or remapping apps
The fix

Step by step

Work through these in order. After the last step, run the diagnostic again to confirm the fix held.

  1. 01

    Start with one physical controller

    Close the game and disconnect spare pads, steering wheels, and controller adapters. Connect the pad meant for Player 1, then start the game. If it works alone, the issue is likely tied to how the game selects among input sources. Keep that baseline before reconnecting anything.

  2. 02

    Use the game's own join process

    Look for a local multiplayer lobby, Press to Join prompt, or input-device setting. Some games keep a keyboard player separate; others let a keyboard and pad control the same player. Follow that title's rules instead of expecting a controller light or browser number to decide the player slot.

  3. 03

    Check the launcher only where it applies

    For a Steam game, check its input layout. If Steam offers a way to change pad order for this game, try it. The options vary by game. Check the player slots again after each change. For other games, start with their own input settings.

  4. 04

    Look for an extra virtual pad

    A remapping app may add a virtual pad alongside the real one. Pause that app for a test and restart the game. Save any access settings you need first. If you need the app to play, follow its guide to hide duplicate input. Do not delete drivers at random.

  5. 05

    If two pads control one player, inspect their mappings

    Two controllers mapped to the same keyboard keys may both drive the same keyboard player. Use separate gamepad input where the game supports it, or follow its specific local multiplayer mapping guide. Also confirm that the title supports local co-op; online multiplayer alone does not establish that.

  6. 06

    Reconnect and verify each player

    Add the second pad, join with it, and test movement separately for each player. Repeat after leaving and reopening the lobby. If the problem returns only after reconnecting a device, record that trigger and check the game's support notes. Replug order is a useful test, not a guaranteed permanent setting.

Fix held? Bookmark this page. Issue back? Jump to escalation below.
If the fix didn't hold

Where to go next

If the game still chooses the wrong pad, use its own local multiplayer instructions. Save the device and input-mode details for support.

Related tests

Other tests for the same controller

Check inputs with one pad at a time. A device index in a tester does not assign a player inside another application.

Frequently Asked

mapping questions

No. It can display the input it receives, but it does not control another game's player assignments. Use the game's settings or supported launcher controls.

No. An input API index and an in-game player slot are different concepts. A game can choose how it maps available devices to players. Do not use a browser index as proof of the game's assignment.

A virtual-controller app can create another input device. Other causes are possible, so compare with that app paused before removing anything. Preserve profiles you need.

Check whether both layouts send the same keyboard keys, whether the second player has joined, and whether local multiplayer is supported. A working second pad in the tester does not automatically create a second player.

Start with player assignment and virtual-device checks. Removing drivers can disrupt a working input source. Use a documented driver repair only when there is evidence of a driver problem.

It may reveal that device order affects this game, but it is not a universal permanent fix. Test after reconnecting and use the game's saved input options where available.

Still seeing the issue?

Re-run the diagnostic to confirm whether the fix held or whether escalation is needed.

Run the test again