next »

[Bernie]

While it's easy to set up gamepad axes in the Input Manager Unity games come with, I really don't want to use it and am working on an in-game solution. This works pretty well for gamepad buttons and keyboard keys so far, but detecting a gamepad analog stick axis seems to be a problem.

The reason for this is that the axis setup of my no-name gamepad differs from the axis setup of my ps4 controller, so making these customizable would be really good.

My 'if all fails' solution is setting up a few axes in the Input Manager and checking those, but that's kind of a messy way to do this.

The question is, can I detect gamepad axes via scripts without using any 3rd party plugins and without the Input Manager?

[bateleur]

I don't know of a way to avoid using Input Manager entirely, but you can solve the specific problem you describe by using Input.GetJoystickNames and then altering config based on the results.

[Bernie]

Thanks! You're right, there aren't really any other options. I'll make it automatically set the gamepad analog stick axes by default with the GetJoystickNames function and add a way to optionally set them manually for when that fails. It seems like only the first 5 axes are ever used by the analog sticks, making it not too much of a chore to code.

[Orymus]

As a side note, Unity is giving access to its new experimental input system as part of its 2018 cadence. You might want to take a peak if you, like most, are unsatisfied with the previous Input manager.

[Bernie]

It's good that they're finally tackling that. I'm staying on version 5.6 deliberately for my current game, but I'll keep it in mind for future projects.

[Orymus]

The new Unity module for input, I believe, is standalone, so in theory, it may be backwards-compatible.
That being said, I don't think it goes further back than 2018.1 or something.
Oh well!