Closing Steam and switching the controller mapping to Pad B resolves a large share of 2XKO controller problems on PC. Common symptoms include double inputs, incorrect button icons, triggers not registering, or the controller working in menus but not during matches.
Fix Steam Input conflicts (PC)
Steam’s controller layer can override or duplicate inputs in 2XKO. Disabling Steam Input or fully closing Steam typically restores correct detection. See the official Supported Devices & Peripheral Troubleshooting for Steam settings and known conflicts: support-2xko.riotgames.com.
Step 1: Exit Steam completely. Right‑click the Steam icon in the system tray and select Exit. This removes Steam’s input hooks so 2XKO can read your device directly.
Step 2: Open Task Manager with Ctrl+Shift+Esc and end any stray Steam or steamwebhelper processes. Lingering helpers can continue to intercept inputs.
Step 3: Launch 2XKO and test the controller in menus and in a match. If inputs now register cleanly, keep Steam closed while playing.
Step 4: If you must keep Steam open, disable Steam Input: open Steam → Settings → Controller and toggle off all controller support options. For PlayStation pads, set the PlayStation support dropdown to “Not Enabled.” Restart 2XKO afterward.
Correct the default mapping (select Pad B)
On first plug‑in, 2XKO can apply incorrect defaults. Selecting the Pad B preset restores expected gamepad mappings.
Step 1: In 2XKO, open Settings → Controller Mappings. This menu controls in‑game button assignments.
Step 2: Select the Pad B preset. This replaces the incorrect default with the game’s intended layout for standard controllers.
Step 3: Test inputs in a training match. If buttons still look wrong, proceed to manual remapping in the section below.
Remove device and driver conflicts (optical keyboards, vJoy, remap tools)
Certain devices and virtual drivers can block or duplicate controller input. Known conflicts include optical keyboards and virtual joystick software. These issues and workarounds are also referenced on the official Known Errors/Solutions page: support-2xko.riotgames.com.
Step 1: Unplug optical keyboards (e.g., specific models with optical switches) and any second keyboards. Test the controller again to confirm whether input returns.
Step 2: Uninstall virtual joystick drivers such as vJoy. Virtual HID devices can capture or inject inputs that confuse the game.
Step 3: Close input utilities and overlays: DS4Windows, reWASD, Razer Synapse, joystick emulators, and GPU/voice overlays. These can layer remaps or hooks over the device.
Step 4: Disconnect extra input hardware and dongles (flight sticks, wheels, extra gamepads, wireless receivers) to eliminate stray axes and button spam.
Reconnect or change how the controller is connected
Re-seating the connection forces Windows to reload the device and clears stale pairings.
Step 1: If wired, unplug the cable and use a different USB port or cable. Front‑panel ports and long cables can be unreliable.
Step 2: If using Bluetooth, remove the controller from Windows: Settings → Bluetooth & devices → select the controller → Remove device. Restart the PC, then re‑pair the controller.
Step 3: Prefer a wired USB connection while troubleshooting. Wired eliminates latency and pairing problems, making input behavior easier to verify.
Reset and remap safely inside 2XKO
Some bindings can soft‑lock menu selection or leave directions “stuck.” Use these safe practices when remapping.
Step 1: Reset to Defaults in Settings → Controller Mappings. This clears any conflicting or partial remaps.
Step 2: Remap only a few critical buttons at a time, testing after each change. Avoid assigning vital actions to the “X” or “A” buttons until a fix is released, as selection can get stuck if those are bound.
Step 3: If an analog direction gets stuck, briefly press the opposite direction to cancel the lockout. This is a known behavior and can be cleared on demand.
Step 4: If the tutorial behaves differently or won’t proceed, complete it with keyboard controls and switch back to the controller afterward.
Check supported controllers (2XKO on PC)
2XKO Early Access supports a short, verified list of devices, and explicitly excludes some.
| Device | Support status | Notes |
|---|---|---|
| Keyboard and mouse. | Supported. | Standard PC input. |
| Xbox controllers. | Supported. | Works as a gamepad on PC. |
| PlayStation 5 DualSense. | Supported. | Advanced features like adaptive triggers and full touchpad are not used. |
| Hori Alpha (PC mode). | Supported. | Set the device to PC mode. |
| Razer Kitsune (PC mode). | Supported. | Set the device to PC mode. |
| Nintendo Switch controllers. | Not supported. | Excluded in Early Access. |
| Consoles. | Not available. | 2XKO Early Access is PC‑only. |
Most PC control devices beyond Switch controllers generally work, but if you have trouble, test with one of the listed devices to isolate a device‑specific issue.
Quick system resets that often restore input
Fast resets clear cached states and reload USB/Bluetooth drivers cleanly.
Step 1: Close 2XKO and the Riot client. Fully exit both before retesting to ensure the game re‑detects the controller on launch.
Step 2: Power cycle the controller. Turn it off, wait a few seconds, and turn it back on so it reconnects from a clean state.
Step 3: Reboot the PC. This clears device conflicts and stale driver hooks that persist across app restarts.
Still not working? Final checks and support
Step 1: Try a second, known‑supported device (e.g., Xbox controller or PS5 DualSense) on the same USB port. If it works immediately, the original device or its firmware/driver is the likely cause.
Step 2: Gather details (controller model, wired or Bluetooth, steps you tried, whether it works in other games) and open a ticket with support so the team can isolate remaining compatibility issues: support-2xko.riotgames.com.
With Steam Input out of the way, Pad B selected, and conflicts removed, the controller should behave consistently in menus and in matches. Re-check after patches, as input fixes are delivered over time.
