Enhanced Input Not Working in Unreal Engine 5? Here’s the Fix

Table of Contents

Works in Unreal Engine 5.1 to 5.8. Updated November 2026.

Quick answer: most of the time the Input Mapping Context was never added to the player.

  1. Open your Player Controller Blueprint (or your character).
  2. On Event BeginPlay, call Get Enhanced Input Local Player Subsystem, then Add Mapping Context.
  3. Pick your Input Mapping Context (for example IMC_Default) and set Priority to 0.
  4. Press Play and test the key again.

How Enhanced Input fits together

Three things must line up for an input event to fire:

AssetWhat it does
Input Action (IA_Jump)The action itself, and its value type: Digital (bool), Axis1D, Axis2D or Axis3D
Input Mapping Context (IMC_Default)Which keys trigger which actions
Add Mapping Context nodeTurns the mapping context on for a player

If any one is missing, the EnhancedInputAction event in your Blueprint stays silent, with no error.

Fix 1: Add the mapping context

In the Player Controller’s Event BeginPlay:

  1. Right-click and add Get Enhanced Input Local Player Subsystem.
  2. Drag from it and add Add Mapping Context.
  3. Set Mapping Context to your IMC asset.

If you do this in the character instead, use Get Controller, Cast To PlayerController, then the subsystem node with the cast result as Player Controller.

Is your character spawned during play, not placed at the start? Then its BeginPlay can run before a controller possesses it, so Get Controller returns nothing and the cast fails. Adding the mapping context in the Player Controller avoids this.

Fix 2: The key is in the wrong context or action

  • Open the IMC and check the key is listed under the right Input Action.
  • Check the event in your Blueprint uses the same Input Action asset. Duplicated assets like IA_Jump1 are easy to mix up.
  • If two mapping contexts use the same key, the one with the higher Priority wins.

Fix 3: A menu set the input mode to UI only

If input stopped after a menu or a pause screen, something probably called Set Input Mode UI Only. Game input is blocked until you call Set Input Mode Game Only (or Game And UI) again. See mouse cursor not showing or widgets not clickable for the full menu setup.

Fix 4: The value type doesn’t match

Movement on WASD needs an Axis2D action. In the IMC, add modifiers to each key:

  • W: Swizzle Input Axis Values
  • S: Swizzle Input Axis Values and Negate
  • A: Negate
  • D: no modifier

With a Digital (bool) action, you get only true or false, never a direction.

Fix 5: The actor isn’t the player

Input events only fire on actors that receive input: the possessed pawn and the Player Controller. For another actor, such as a door, call Enable Input with the Player Controller first. Usually it’s cleaner to handle the key in the character and tell the door what to do.

Check the project settings

In Project Settings > Engine > Input, Default Player Input Class should be EnhancedPlayerInput and Default Input Component Class EnhancedInputComponent. New UE5 projects set this already. Projects upgraded from UE4 may not.

FAQ

The event fires once but not while I hold the key. Use the Triggered pin for continuous input. Started fires only on the first frame.

Gamepad works but keyboard doesn’t (or the other way round). Each device needs its own key rows in the IMC.

How do I see which contexts are active? Type showdebug enhancedinput in the console while playing.

Related tutorials