Bug #14015
With multiple joysticks, game does not correctly remember which buttons are assigned on which joystick
0%
Description
Version 1.2.2.1622 (64 bit, Steam version, no mods)
Windows 7 64-bit
Replicating the problem:
1. You will need two joysticks or joystick-like devices. In my case, I used a Saitek X52 joystick and Saitek rudder pedals, which the system treats the same as a joystick.
2. Ensure both are detected by the game (try to assign buttons or axes in the input settings).
3. Assign a joystick button to a control, e.g. assign a button as the "staging" control.
4. Take note of name of the button which was assigned, e.g. "Joystick1Button1", and verify that it works in game.
5. Restart the game (rebooting the computer is possibly needed to reproduce the problem).
6. At this point, the control will still have the same name in the input settings (i.e. "Joystick1Button1"), but Joystick1 may have become Joystick2, and vice versa, meaning the control settings will no longer work properly in game. You can test to see if the problem has occurred by trying to re-assign the button - if you reassign the button and it detects the button as being on a different joystick (i.e. it was "Joystick1Button1", now it is "Joystick2Button1"), the problem has occurred.
Notes:
This problem does not seem to happen with joystick axis controls, only buttons. If you assign an axis, then restart, the axis will still be assigned to the correct joystick even if its number has changed. Issue can be game affecting if you do not realise it has occurred until you are already in game.
Workaround:
Manually verify the controls every time you start the game, and reassign them all if necessary.
History
#1
Updated by pba almost 7 years ago
Updated by Hello,
I can confirm this specific bug. In my case i use a joystick on mac osx, and have multiple other, virtual joysticks assigned by ControllerMate, an application for wiring controls to virtual joysticks.
The behavior above (wrongly mapped buttons) happens to me as well.
In addition to that, after adding a new joystick the control axis of different previews/new joysticks are mixed up.
My version is also 1.2.2.1622 (OSXPlayer). The Axis are not mixed up when not changing the number of joysticks.
The wrongly mapped button-names make reference to a Joystick which according to settings.cfg `INPUT_DEVICES` should not exist
Unfortunately the current beta version crashes on me during startup, but i have found no changes to control input setup in the changelog anyways.
Tag: Could you add a platform mac tag to this ticket?
#2
Updated by Manwith_Noname almost 7 years ago
Updated by I'm not sure if it's a consequence of trying to address this issue or if something broke by mistake but the situation is worse in 1.3. Now, assigning multiple controllers no longer appends an ID number to the controller. So effectively, all "button 1" assignments are triggered by the corresponding button on each controller. As mentioned above, it used to attribute...
"Joystick1Button1"
...to the assignment, now it registers simply...
"JoystickButton1"