Fix: Unity Input System Control Scheme Not Switching

Here is how to fix Unity New Input System control schemes that refuse to switch when the player picks up a controller. Keyboard works on game start. Plug in a gamepad, press buttons, and the action callbacks come through — but PlayerInput.currentControlScheme still says “Keyboard & Mouse.” Your on-screen prompts stay on keyboard glyphs. The fix is usually a single checkbox in the inspector, or a missing SwitchCurrentControlScheme call.

The Symptom

The PlayerInput on your character is wired up correctly. Keyboard W/A/S/D moves. So does the gamepad left stick. But the prompt UI never updates from keyboard glyphs to controller glyphs. PlayerInput.currentControlScheme is stuck on its initial value. onControlsChanged never fires.

What Causes This

Auto-Switch disabled. The PlayerInput inspector has a checkbox labeled Auto-Switch (under the Notification Behavior dropdown). When unchecked, the component does not change schemes even if input from a different device arrives.

Multiplayer lock-in. If you have multiple PlayerInput components (local co-op), the system pairs each one to specific devices and refuses to switch on its own. This is by design but surprising for solo developers who just want device-agnostic input.

Scheme name mismatch. When calling SwitchCurrentControlScheme, the string must match exactly what is defined in the .inputactions asset. Case-sensitive.

Device not paired. Schemes can list devices as required or optional. If your gamepad is not paired with the user, the scheme cannot activate even when input arrives.

The Fix

Step 1: Enable Auto-Switch in the inspector. Select your PlayerInput component, expand Behavior, and check Auto-Switch. This is the simplest fix for single-player games.

Step 2: Subscribe to onControlsChanged for UI updates.

using UnityEngine;
using UnityEngine.InputSystem;

[RequireComponent(typeof(PlayerInput))]
public class InputDeviceWatcher : MonoBehaviour
{
    private PlayerInput playerInput;

    void Awake() { playerInput = GetComponent<PlayerInput>(); }

    void OnEnable()  { playerInput.onControlsChanged += OnControlsChanged; }
    void OnDisable() { playerInput.onControlsChanged -= OnControlsChanged; }

    void OnControlsChanged(PlayerInput pi)
    {
        Debug.Log($"Active scheme: {pi.currentControlScheme}");
        UpdatePromptGlyphs(pi.currentControlScheme);
    }
}

Step 3: Force a switch when needed.

// Swap to gamepad scheme using the connected gamepad device
if (Gamepad.current != null)
{
    playerInput.SwitchCurrentControlScheme("Gamepad", Gamepad.current);
}

Pass the device explicitly so the scheme has something to pair with. Pass multiple devices for schemes requiring keyboard plus mouse:

playerInput.SwitchCurrentControlScheme("Keyboard&Mouse",
    Keyboard.current, Mouse.current);

Step 4: Confirm scheme names. Open the .inputactions asset, click the Control Schemes dropdown at the top, and note the exact names. Use them as constants in code:

const string SCHEME_KBM     = "Keyboard&Mouse";
const string SCHEME_GAMEPAD = "Gamepad";

Step 5: For listen-for-any-device, use InputUser. If you want the player to start the game without a paired device and pair on first input, use the InputUser API:

InputUser user = InputUser.PerformPairingWithDevice(Gamepad.current);
user.AssociateActionsWithUser(actionAsset);
user.ActivateControlScheme("Gamepad");

Multiplayer Considerations

In split-screen, each PlayerInput owns specific devices. Auto-Switch is meaningless because each player’s scheme is fixed to their assigned devices. Use PlayerInputManager with Join Action to pair devices to players as they join.

UI Glyphs Best Practice

Cache a dictionary of glyph sprites keyed by scheme name. Update once per scheme change, not per frame. Reading currentControlScheme in Update is safe but unnecessary — onControlsChanged already gives you the events.

Understanding the issue

Input handling sits between hardware and gameplay. Hardware has its own protocol; gameplay has its own model. When these don't agree, the player perceives unresponsiveness even though every layer is technically functional.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Auto-Switch checkbox handles 90% of cases. The other 10% is explicit SwitchCurrentControlScheme with the right device array.”

Related Issues

For input not arriving at all, see New Input System Actions Not Updating. For UI failures, see New Input System UI Not Working.

Auto-Switch on. Subscribe to onControlsChanged. Match scheme names exactly. Done.