daemon3000
commented
8 years ago My advice is to not use the Input Adapter at all, it's obsolete. Initially it was meant to solve the following issues:
- Abstract away the fact that the XBox 360 controller has different buttons codes on each OS.
- Allow you use use the DPAD and triggers as buttons instead of axes.
For point 1 it's much better to have a menu in your game where each player can rebind their buttons. Configure the game for the Windows XBox 360 drivers and let users on Mac and Linux rebind the buttons and axes. The added bonus with this solution is that the player can use any gamepad they want not just the XBox 360 one.
For point 2 you now have the Analog Button axis type which can convert any stick/trigger to button input.
If you don't want to allow the players to rebind the buttons you can also do it this way:
- Make three XBox 360 configurations, one for each OS, and set them up to receive input from Joystick 1 for player One.
- Write a script that runs at the start of the game and does the following:
- For each of the other three players, clone player One's configurations and change the axis properties so it receives input from Joystick 2, Joystick 3 and Joystick 4. Look at the CloneControllerConfiguration.cs script to get an idea on how to do it.
- Check what platform you run on and assign the corresponding configuration to each player.
oservieres
This is a non-critical question. Mostly for curiosity.
This is my configuration :
My final purpose : make the game work with 4 controllers on Windows, Linux and Mac. Right now, the game works fine on Windows. It may also work correctly on other platforms with only one controller : the one defined in the Input Adapter. But I guess that the 3 other controllers are not gonna work.
At first I thought that I could use 4 input Adapters, each one assigned to a specific player, but it's a singleton.
So I'm quite stuck here.