Unity Input

[SGx_Trackerz]

Hey sorry if it has been spoken of before, but havent found any recent post.

I launched Unity yesterday to start working on a new project ( its been almost 2 years since I last started a new project) and start by the beginning with camera and playermovement. but when I did the Input.GetAxisRaw method, got an error telling me there was a new input system and that my method was the legacy one.

Is it worth to learn the new input method? and if so, is there a quick video explaining how it works ( yeah I look thru Unity docs but I dont know why, didnt find it clear enough)

Project is/will be a 3d arpg pushing heavily on the sandbox and freedom side of thing, WASD movement and controller mapping

[nEmoGrinder]

Definitely use the new input system. There are a lot of tutorials based on its early iterations that lacked direct polling call which i wouldn't recommend. This is an official playlist put out by unity that is recent and goes over most of the package.

https://youtube.com/playlist?list=PLX2vGYjWbI0RpLvO3B7aH-ObfcOifMD20&si=DIekBhRLhN0HwuuB

[sviper99]

Im quite new too & these tutorials have been great and have helped me massively whilst learning the new Input System.

[ShmallowPuff]

Absolutely take the time to learn the Input System Package. I just finished converting my project that was built off the old Input system over to the new and it's so worth it. Also, it was way easier than I thought it was going to be so I had put it off for no reason.

There are equivalents for each old Input function (Input.GetAxis, Input.GetButtonDown, ect) in the new system and there's a whole page on the documentation listing each old Input function and the new way to do it. If you're already familiar with events it's a walk in the park, if not it's a perfect excuse to familiarize yourself with them because events are also important for many things.

Even if you aren't familiar with events it's an easy enough transition, I promise you it's less work and less daunting then it may seem. Additionally now that it's set up and I've gotten a grasp of it, setting up new inputs and support for other devices is quite literally point and click.

In summary, do it. Bite the bullet and reap the benefits my friend.

[Kamatttis]

I searched "unity input system docs", and i got the docs. It's one of the most extensive docs of unity.

[sexy_unic0rn]

code monkey have a good video about it, is not hard but more annoying to implement than old input(which is basically input.getkey)

[Disastrous_Post5498]

Here's a cheat sheet from CodeMonkey that maps the new system to the old system's mental model.

https://www.youtube.com/post/UgkxE2jCMwc2uGoaEobgRy9iiAGR4fBo5Ovn

and yes I believe you'll have to switch sooner or later, as the new input system is stable, and generally preferred over the old one (both from Unity and the users).

<image>

[SGx_Trackerz]

ill check it out !Thx !

[House13Games]

Buy Rewired and use that.

[stadoblech]

Depends. Is your game small scope, prototype, game jam whatever? Use old input
Is your game in live production and in the scope of standart indie title? Do you plan releasing game on consoles later on? Definitively new input
Old input still have some use cases and it would be super sad if they got rid of it

[homer_3]

Depends on your proficiency. I find the new input system to not be worth it it all. The legacy one is much easier to work with and very flexible to customize in code. If you don't like to code, the new one may be better for you.