😀When using Play In Editor, inputs may not register until the editor window receives focus. Click inside the game window after starting play to enable input.

This behavior is normal while running inside the editor. It is not caused by incorrect input bindings.

😀Unexpected Camera Rotation in Play-In-Editor

A common question is why the camera rotates around the player when it shouldn’t.

In many cases, the cause is Level Editor Joystick Controls being enabled in the Unreal Editor. When this option is active, the editor may interpret joystick input and apply it to the pawn camera rotation by default.

This behavior can make it seem like there is a problem with your Input Settings, but the issue is actually coming from the editor itself.

If this happens, check whether Level Editor Joystick Controls are enabled in the editor settings and disable them if necessary.

😀Avoid Mixing Input Systems

When using WM Input Manager with Enhanced Input, bind only HID_Joystick events.

Remove any bindings for:

• Generic Gamepad
• Xbox Gamepad
• PlayStation Gamepad

WM Input Manager already processes input from all of these devices internally. Keeping those additional bindings can cause the same input to be received multiple times, resulting in unintended or duplicate actions.

😀Axis2D Inputs Are Not Supported by WM Input Manager

When configuring Enhanced Input, always use Axis1D inputs.

For example, Horizontal and Vertical movement should be defined as separate Axis1D inputs, rather than using a combined Axis2D input, which is sometimes used in native Unreal setups.

This system is designed as a low-level, fully rebindable device configuration layer, so combined axes such as Axis2D are not permitted. Each axis must be configured and handled independently.