Use Unity's Input System Like a Pro 

This is incredible, Paridot. This fixed all the issues I was having with my movement and the handling of all the different states. This was invaluable.

"And you need something else to procrastinate with even though what you have right now works just fine"... I feel personally attacked🙃

This is great. Thanks for making this. So many tutorials just use the Player Input script and nice to see a better way.

Wow. Just Wow! Amazing walkthrough with Input system and it's usage! Thanks for sharing, and merry Christmas to you and your RU-vid channel!

I just subscribed. I'm an impatient person, so I absolutely love the pace and depth of your presentation. Perfect for guys like me!

Clean Implementation - nice work !

I´ve found this just recently, but please. Let me pay you to teach me, the calm and good way you explain alone this. I´m sure you could explain much much more in a very great way. Thank you so much for this and many upcoming videos :D

I think things finally just clicked for me on all this! I have struggled so much with perfecting a input system that uses all the robust features of the new input system and is simple to understand to implement across my controllers!! Thank you so much!!

Yes, this is the best video about using the new input system. Basically, everyone shows an example using the playerInput component.

This video was on my 2 weeks old tab designated to be watched some day... :) Finally watched it today, subbed, you have awesome teaching ability. And I was looking for the way to jump over to new input system, thanks.

Thank you very much for the video, this is the first time I've seen such an implementation and it's the best one I've ever seen

Perfect. Thank you. I was doing something similar with the "old" system so had the abstractions. Glad I found this before I tore it all down :)

Thank you, this clarified a couple things for me

Just earned a subscribe. I actually was starting to tackle this today, and was having issues with the jump. Move was a breeze. Just couldn't figure out the button part. awesome stuff!

This channel is a hidden gem!

Wow, very good tutorial, I liked and subscribed

It is scary... somehow it exactly answers my needs, and what I was searching for for several days. What can I say? Subscribed. Thank you!

I also used extra layer of abstraction while setting up my input system, but never thought about diong it with SO. That is actually a game changer, deffinitely gonna improve my game with this idea, thanks!

That was the smoothest like and subscribe call to action 😂. Great tutorial!

I don’t know why i did not find your video when i was searching how to implement the input system with the generated C# class instead of the input component. I ended up with a messy player script because i don’t have the skill yet to create that intermediate layer, so i put everything in the player controller script. Looking forward to more content!

I remember watching this when I first started with unity and had no idea why you did it this way and it seemed all so complicated and weird. I didn't know what events were or Scriptable Objects. I had watched so many other videos on the input system and in all of them people did it different (tutorial hell). I found an easy way and stuck with it for a while, because it worked. Now months later, while still being a noob, I totally get it and I really appreciate your way of handling inputs. it's easily the most methodical and cleanest way that I have come across and for me the only way to do it. The only "issue" that I see, and maybe you just forgot (or maybe I am still too much of a noob), is that you didn't unsubscribe from the events to prevent memory leaks. but yeah cheers for showing this!

This is pure gold, really appreciate the way you explained the topic and implementation.

Amazing guide man, you should have a tip jar or something, wouldnt mind giving 5 bucks for such good knowledge my man

Amazing vidéo 🤙🤙

Since you made me laugh within the first 30 seconds of the video, I am now subscribed. Thanks for that!

What a great guide, it was my first time with the new input system and it works perfectly. Thx !! Let smash the subscribe button 👌

very insightful video!

"This button isn't working for me for some reason, maybe you can... check it out see if it works for you" Hahaha, definitely subscribing after that.

I've always been using Unity's build-in solution and using the unity events methods to hook up my corresponding functions. It works indeed just fine, but Unity Events are more cost heavy then C# events. I'm glad I found this video showing me how to set this up similarly to Unity, but better! :) The fact that you've even turned it in to an SO made me really curious on how I could implement this solution in my own project. :) Thank you so much for making this video! It learned me something new! :D UPDATE: I've been tinkering with your method some more and I've managed to improve it a bit. :) Instead of making a function for each type of action map you want to use, I instead have one function that passes through the new action map name I want to enable. I loop over all the action maps and compare the names and if they match I'll enable the action map, otherwise I'll disable it. :) Here is the code I've used to make it more managable: public void SetActionMap(string newInputActionMap) { foreach (InputActionMap inputActionMap in _gameInput.asset.actionMaps) { if(inputActionMap.name == newInputActionMap) { inputActionMap.Enable(); } else { inputActionMap.Disable(); } } }

When I saw multiple Action Maps being created (GamePlay and UI) and multiple actions (Move and Jump) and multiple controllers/bindings (WASD and GamePad), I realized there's going to be a lot more video watching and typing than necessary. DRY and KISS principles can apply to teaching videos. Just my 2 cents as someone with the attention span of a … oh got to go! Subscribed BTW.

I've been using this exact system that I basically ripped off from the Chop Chop community project that Unity started a while back. It helped me a lot compared to instantiating different instances of the generated input class in different scripts.

Pretty nice solution! This is the endless struggle of using Unity, you typically want to take advantage of its nice editor features (like its serialization) and in the same time to move away from its counter productive API. The new input system is pretty powerful but it is no easy task to properly abstract its functionality. Also, are you using Rider? How did you made it to look so lightweight? Congratulation again for the grate video!

great vieo

Might I suggest the events be static to remove the dependency on the scriptableobject being injected into every component?

aaand with THIS video you got my subscriiption.... HOOW does´t anyone mentioned this interfaces before??

disabling the UI action map doesn't actually prevent the EventSystem from using the actions defined in the InputSystemUIInputModel component though does it? Would you use Unity's provided Interfaces for UI with this setup?

How would you implement input rebinding ?

That's a very nice implementation. Just one detail regarding your video: for a non-native English speaker, sometimes is hard to hear your voice. It's like you're speaking so low that your voice becomes hoarse, and it becomes difficult to understand.

Make sure you dont bind the actions in the start() method like shown in the video. instead you should bind and unbind them in OnEnable() and OnDisable() to avoid null refs when respawning gameobjects like the player or scene changes. using OnEnable and OnDisable is also the way it was done in the example open source project but its missing in this tutorial.

I dont get how to use th einput system for Aiming with a mouse or joystick. To shoot that direction in a 2d game. Anyone know?

This is a decent tutorial but i'm stuck @ 11:33 because i'm having a namespace error/reference error how can i fix this?

11:16 What do you use? Radory? Readoi? I dont get it

Great tutorial! I have one question, why are you using ScriptableObject on the Input Reader and not just a plain C# Class?

Hello great video !! I fully understand everything and it was really nice, i have a question cause i already implement a input system but in my case i use a MonoBehavior, there is any difference between these two? more than one must be assign to the object and other is just there in the project ? Thank you!!

What is the name of the website that you're using for the input system visualization?

I think for the events, there can be created a static class. It would eliminate the necessity of creating the reference for the SO?

hey very nice approach but i got a question is it viable or better in anyway to NOT use the unityEvents Actions and instead use public variables to store the values directly in the Scriptable object inputReader for example inside The OnMove(InputAction.CallbackContext context) method we can say MyVariable = context.ReadValue()) , and simply access MyVariable on the playerController code that is already referencing inputReader... is it less expensive than subscribing to events or am i missing something ? Thank you so much!

the joyatick never go to zero what can i do?

The events have callbacks in the generated file already. Why not use those? Also, why are you using a scriptable object for the intermediary? Won't both be attached to the player, which is loaded every scene anyway? There doesn't seem to be state information we're passing between scenes. I'm confused about the point of all this.

I'm having trouble and hope someone can help. I followed the video step by step but encountered a problem in playmode. The first time i enter playmode after creating a new Input Manager Scriptable object everything works as intended, but as soon as I exit and reenter playmode (without deleting the existing Input Manager SO) none of my inputs are detected. Anyone run into this? Anyone solve it?

Thank you for your video, good editing as well. I'm a bit questioning the purpose of the InputReader layer to be honest. Except from the fact that you're not instantiating the Input class for each component and make it a drag and drop Scriptable Object, what is the purpose of Observing an event on the Input class just to expose another event on the InputReader without any globalized goal here? It seems to me that you added a Layer Input Reader because you didn't refactorize and didn't want to register the Input class directly. I could be wrong and there's a real advantage to this layer but I'm very curious to hear it 🤔

Hello ! Good job for the video ! What is the name of the software to make the diagram please ?

This is cool and all, but how is this easier than just using the Player Input? We'd still need to create the scriptable object input reader anyway. Isn't it the same as attaching the player input component to the thing we want to control?

Solution is good. But I can't understand for what we used Scriptable Object? As I understand we simply can use an usual MonoBehaviour script. Would be really grateful to get feedback Does this method suit to handle touchscreen elements like a button (to open inventory in game etc)?

How would you extend this so only some ui can block only part of the gameplay map (ie only movement)? Making another action map ie UI_WITH_ONLY_X_ENABLED , doesn't scale. Setting particular actions enable and disable becomes such a mess also. Adding to this gui buttons action blocking is also such a mess. I havent found yt video that would satify all scalable requirements. Everyone just focuses on basics ;/

What is code editor?

I've always wanted to be a pro

why would you make your own "input reader" when it already has an event system built into it? That's really redundant. The whole point to the new input system is so you don't have to do this

15:28 'The first thing we have to do in unity is create the Input Reader asset'. There is no asset in my create menu. Game over. That's 2 hours of my life I won't get back.

Using a prebuilt system 🤢✋🏻 Using a system you built using a premade system you copied 😎🤌🏼 Note: i did not watch the video yet, just a joke im sure theres plenty of reason to use this video to develop a deeper level of understanding and i appreciate that