This video really helped me to understand how to use the new input system. Thank you!

I went through four different tutorials on this new system, including the one in Unity's documentation, and this is the only one that got my character moving. Thank you!

Thanks for this

i need to have 5 joystick on screen stick , joystick but istruggle to set which joystick should control the correct function, cause it only work with right and left gamepad

The best video I've seen about the New Input System. Thank you! Also, what software did you use to edit your video and do the picture-in-picture and zooming?

Great that you added a little explanation about what control schemes and action maps are. And an interesting way to create the event for it that's different to other tutorials. I've been trying to set up a game that has both keyboard and mouse enabled at the same time for movement (it's a simple game, doesn't need a controls selector). I've only been able to make it work in code by only triggering a pointer move when you click. But I wasn't sure if input actions are actually able to do that? I tried a composite with a modifier, didn't seem to do it. I also don't get how it works when you get a canvas involved. It doesn't do everything, mouse needs a raycast if you have a canvas UI and in-game controls.

I like how I cant add this video to a playlist like I can every other video

I have 15 minutes to spare, so watching it and commenting on it, should be possible. This is a great example of 'show and tell' cause even a noob like me can just begin with this. Now thinking of what kind of game I want to write .... that might take a bit longer. A waaaaaaaaaaayyyyyyyyyyyyyy bit longer. And 3 seconds left. Nailed it!

Very cool introduction to the Unity Inputsystem. I started using it, but I'm still not familiar with all the possibilities it will bring.

The second Thomas-tuesday in a row! Now it's a pattern. Stick to it! I like the new input system. It's better, far better than the old magic string based system. But it isn't completely thought through though ( like the consistent pronounciation of "-ough" in some english words). The InputSystem can create a c# class of itself. That class does not reference the asset, but insteads delivers a duplicate as serialized json within itself. Which means, if you use the c#-class version, but you also have a UI event linked to the InputSystem asset, those are not the same instance which is really not handy when enabling and disabling keymaps when switching states. The c#-version has a reference to it's runtime-created asset and that can be assigned to the event system via code, but it's kinda strange and feels like one of these "did you talk to actual developers when designing this?" moments that tend to happen sometimes with Unity components. The rebinding is a little obscure but practical once done.

I wish I had seen this before I implemented an input observer from scratch because I thought polling for input in update() was stupid.

niceee

Hello! Thank you for the video. I would like a deeper study of the new input system, for example, how to correctly create a virtual mouse for the gamepad and correctly switch between it and the native mouse. The official example from Unity is bad and doesn't work well.

I tried using the new input system a few years ago but I still prefer the old input system. The new input system just feels bloated and if I want to have a more complex input system I can just make a class that handles the input the way I want it to be. Nice video though with good explanations.

Thanks but I rather code. This seems like something that's gonna be deprecated few years from now.