If you thought this was going to be a comedy gag, then that’ll depend on your idea of comedy. If you’re ever making a game in Unity and you are primarily building it for joysticks, do not use their system.

Where the Input system, as a whole, really screeches to a halt is the very reason that I diverged from it completely. You can, of course work around this, as you can see here.īut that’s not the worst of it. And if they misspell a key, it’s going to frustrate them even more that their game isn’t working right. The second is that it breaks down from a usability standpoint, since all key names have to be known to your users. God help your users if they’re playing a 2 player game. The first is that your player has to leave the game and restart any time you want to change the controls. There are a few problems with that, though. In theory, the InputManager is the rebinding solution Unity offers, with the standalone launcher having a tab to change these values. If you game doesn’t have any controls that you would want to rebind, such as anything for mobile, games with a very limited command set, or games which require 1-to-1 mapping to make sense, then using that is perfectly fine. Reading input directly is great when you’re working within the editor, because you don’t necessarily want actions to be rebound. It’s split into 2 systems: raw input reading of keys through Input.GetKey/Down/Up() functions and the InputManager’s axis reading.

If you’ve ever used Unit圓D’s input system, you probably know it’s one of the most okay systems ever.

Unity3d using an xbox controller on mac