How to Easily Use the NEW Enhanced Input Action System in Unreal Engine 5.1

Hello guys, in this quick and simple tutorial we are going to learn how to use the new Enhanced Input system in Unreal Engine 5.1

unreal engine 5,ue5,enhanced input system,tutorial,quixel,megascans,unreal engine enhanced input system,enhanced input mappings unreal engine 5,ue5 enhanced input,ue5 enhanced action mappings tutorial,ue5 how to use enhanced input system,unreal engine 5 enhanced input mappings,unreal engine 5 input actions enhanced,unreal engine 5 enhanced mappings,unreal engine 5 how to map keys enhanced input action, unreal engine 4,ue4,unreal engine 5 enhanced input tutorial,ue5 enhanced mappings tutorial, enhanced input actions in ue5

[darrenj.griffiths]

"Which I will not be covering" and "Which I will not be covering" and "Which I will not be covering" and "Which I will not be covering" .... brilliant!

[GordonSeal]

The new Enhanced Input System is a mess: 1. Allowing the players to remap them ingame requires you to build a dedicated save-game system just for the Enhanced Inputs, because the inputs are data-files now and thus reset every time the game starts.

2. The values in the enhanced inputs do NOT reset, meaning axis mapping (e.g. Move Forward & Move Backward) requires you to set the value of the input to zero again after "Cancelled" or "Completed".

3. You have to create all these data assets, generating more possibilities for bugs to appear - since Unreals file dependencies are prone to errors.

4. Creating inputs takes way longer than it did with the old system. Equally changing your inputs takes way longer, as you now have to go through all these files instead of having them all cleanly in one place.

5. I personally don't like all that logic in the new inputs ticking in the background, although the impact is rather negligible. I also don't like the necessity to cast for adding input contexts (as I don't use the controller for inputs), but that's just me.

6. Switching input methods requires more work now and is way more convoluted than it did before. Before all an input switch took was a branch after the input function, wheres now you not only have to handle all these extra input data files, (cast and) add the input context, but you also have to recreate all this extra logic for the inputs.

7. Prototyping with the Enhanced Input system takes way longer than it did before. Wanna just quickly set up a project to test out something? Well now you have to create all these input data assets for it to work.
It's also way harder for a team to prototype, as now everyone has to learn and completely understand the new Enhanced Input system, whereas before everyone could understand & edit the inputs by just looking at the Project Settings page.

There is nothing you couldn't do with the old system, Epic should have just expanded and overhauled the old system with new options, instead of deprecating a good, working system.

[griglog]

"In this tutorial I will explain how to use the new system"
"I wont cover this"
"I wont cover that"
"This one is a bit too complicated"

[FlyingLotus]

Ahhhh it was so much easier before. They love to complicate things😂

[TrocarQueen]

This was exactly what I needed to make a slightly outdated tutorial I was following work. Thanks for making it!

[MnMultimedia]

Thanks, I watched this a year ago when it came out, but didn't really absorb it. This time I did. Much appreciated, thank you!

[matamare-zsui]

How is this better than before? Seems like it's needlessly complicated 😕

[PirateDion]

Not too long ago fought about getting the engine to recognize a right click vs a right mouse button held and this just invalidated all that effort with the triggers and modifiers and I love that for it.

Still figuring out the basics but was one of those problems that seemed easy on paper then implementation became messy.

[daniyalmehmood]

can you make a tutorial on the triggers and modifiers?

[VividMind-of]

Thanks, I needed this tutorial. You saved ne a headache.

[DirectionGaming]

i'm having issue...
Sprint forward - "Shift+W"
Jump - "SpaceBar"
Input action Jump is not Getting Registered when "Shift+W"+SpaceBar" pressed for Jump while sprinting.
so how should i add Jump Action while Sprinting.

[KudeKube]

I'd really like a tutorial about the modifiers and triggers.

[escorpianoyqueee]

I'm confused, I used to create input mappings and assign them from a custom Player controller, then move the actions to the pawn. Does this means that the player controller is not needed anymore?... The whole example is applied in the Pawn, what if you want to change the controller to be AI?

[Alexlinnk]

GUYS if it doesn't work

Add "Enable input"

[nobodyimportant]

I'm just trying to figure out how to feed analog data into your movements so that when you move with a controller, it doesn't lock you into 8 predefined directions like in dark souls 2, but actually respects the exact angle you wanted to go.

[kfirkfir]

Fought hard to integrate this system the first time, wish this video came sooner :D worth showing the C++ way of doing it too, it is much harder

[woxi]

i dont get this system at all, all i wanted was MMB a keybind, theres a 100 menues, options and drop down things going on. it feels like i went from a horse pulled carriage to a fighter jet, and yet i cant find the horse, by which i mean where do i bind the MMB as a keybind, so that i can make it do stuff in a blueprint later

[duxart]

Great lesson! Can you tell us about the new GAS modular system?

[adel]

when I have the button triggers as hold, I can display the UI widget, but when I release the button the widget doesn't get removed. any suggestions? with the same blueprint when the triggers is set as pressed, when I press the button the widget appears and when I press the button again the widget gets removed.

[StianF]

What is happening between 9:01 and 9:48?
"About the axis: you can see that we have two values over here that we have"
X and Y, and both can be -1 and +1, sure, and you open the action mapping to show that the value type is
"basically using the Axis1D float or the Axis2D vector". "Just outputting more stuff, ok?".
"And basically, digital bool is just, if you press a key it will just trigger whatever it has to do"?

I would like to know how the movement-input gets translated from WASD to a vector/vector2D, as you state, but you didn't show the mapping context so we still have no idea how to pass W A S D as x:1, x:-1, y:1, y:-1 :(