Thanks for the feedback. I will update this guide with improved images.

Appreciate the breakdown of each process but by not showing a large view of each step in the process and how they relate/ connect with another node (box/ axis mapping box) in a ‘single’ picture.. It’s hard to understand where to start if you’re a rookie

That does sound like it most likely has a performance impact.

Have you tried to disable the consume input box on the input action you are trying to use?

The input system is a priority stack and the highest priority will get exclusive use of that input.

https://docs.unrealengine.com/Images/Gameplay/HowTo/ActorInput/Blueprints/input_9.webp

On the Unreal Engine documentation it shows examples of the input enable and disable steps in more detail: https://docs.unrealengine.com/en-US/Gameplay/HowTo/ActorInput/Blueprints/index.html

Thanks Matt,
I used Enable Input node in Game Mode and now input action works fine for me. I was looking for this answer all over the internet.
But why doesn’t “Input Action” work without this node as it works in level blueprint. Does it cost any performance degradation?

Actors that aren’t possessed by the player controller will not inherit input automatically.

To fix this add an enable input node and connect your player controller to it. This should fix the input issues you are having.

We missed this out in the guide and have just updated the guide showing how to use non character blueprints with input. Thanks for pointing this out!

I mean input ‘logic’

This doesn’t seem to be true. When I try to use the action mapping in Game Mode blueprint, it doesn’t fire. In other blueprints it does.
Any idea why is that?

I would like to have my input login in the game mode.