UPDATED January 23rd 2014 at 16:00 GMT.Choosing controls for players
On the game's OPTIONS page you can now choose which controller, if any, each player should be using. Player #1 can use mouse+keyboard, controller 1 or controller 2. Player #2 needs to be on either controller 1 or controller 2 or can optionally be completely deactivated.Default controller setup
The default controller bindings are this:
Left stick: Move
Right stick: Aim
Left Shoulder: Transfer
Right Shoulder: Fire
D-Pad: Switch droids
If these aren't working for you though, you can now reconfigure the setup yourself. Have a look in the game's folder in your user home directory (on Windows that's C:\Users\<YOU>\.<GAME-NAME> ) and you should find a file called "controls.txt". You can open it up with any text editor (like Notepad for example).Binding controls to controller sticks and buttons
Up to two controllers are supported. Each line must start "controller1" or
"controller2" followed by a dot "." then either "axis", "button" or "pad" and another dot ".". For "axis" or "button" a number follows indicating the index of the axis or button.
Axes can be assigned one of these values:moveX
controls the horizontal movement of the player-moveX
same but with the direction reversedmoveY
controls the vertical movement of the player-moveY
same but with the direction reversedaimX
controls the horizontal aiming direction of the player-aimX
same but with the direction reversedaimY
controls the vertical aiming direction of the player-aimY
same but with the direction reversedfireaxis
as a firebutton whenever there is any movement
Buttons can be assigned one of these values:firebutton
switches to the next droid in the squadprevious
to the previous droid in the squadstart
start button, for spawning the second playerback
back button, saves and exits the game
So for example, for regular Xbox 360 controllers, what you probably want is this:
You can't bind the same axis or button twice and case is important throughout so "aimY" will work but "aimy" or "Aimy" won't.
Any of the axis values can be reversed if that's needed for your controller, so if moving the left stick to the left makes the droid go right, you need to rebind the movement axis to "-moveX".
If you're having trouble finding the right axis or button numbers for your particular controller then - while the game is running, press CTRL+F7 which'll copy some controller diagnostics into your clipboard. Then quit the game, open up Notepad or some other text editor and hit PASTE. The resulting file should make it easy to see how many axes and buttons your controller reports to the system.
Case is always
important in everything in controls.txt. So "moveX" is right, "movex" is wrong, "AUTO" is right, "auto" is wrong, and so on.Lefty controller setup
If you prefer the left stick to aim and the right stick to move, you can edit the controls.txt and swap wherever it says "moveX" or "moveY" with wherever it says "aimX" and "aimY". So for a Xbox 360 controller, it'd look this like for the Controller 1 lines:
controller1.axis.0=aimYChoosing which devices act as Controller 1 & 2 in-game
When controls.txt is first created (or any time you delete it and run the game, which'll re-create it) the game will write some lines into the file that show you what devices were found on your system that might
be controllers. Usually this should detect any actual controllers but might also detect some mice, graphics tablets or other unusual input devices.
Here's an example of the kind of thing you might see in your controls.txt file:
device2=Controller (Gamepad F310)
device1=Wacom Graphics Tablet
device0=Controller (XBOX 360 For Windows)
In the example, the game found 3 devices that might work as controllers: an actual Xbox controller, a Logitech controller and a Wacom tablet that obviously won't work well for the game at all.
You shouldn't try to change these lines, it won't do anything. If you need to set which devices act as controllers, you need to look for these two lines:
These lines tell the game that it should just try to automatically work out which of those 3 devices should be treated as Controller 1 and Controller 2 in game. The game always tries to pick sensibly from this list but sometimes you might need or want to change which of your input devices the game should be trying to use.
To override that setting, just change "AUTO" to one of the "device" labels we saw above.
So in the example, maybe you want the Logitech F310 gamepad to be Controller 1 in-game and the Xbox device to be Controller 2. You would change the above two lines to say:
controller1=device2Disabling some or all controllers
If for some reason you want to disable a particular controller slot entirely - or both - perhaps some device on your system interferes with the game running properly and you don't have a controller to point the game at instead. Just edit one or both of those two lines again, like this: