Bug #21007
Joystick buttons in input mapping screen do not show which joystick they belong to
0%
Description
I run two joysticks - a flight stick (4 axis, 7 buttons, hat) and a game pad (4 axis, 12 buttons, hat) (the exacts are irrelevant to this issue except that they're different models, and both use the Windows Generic DInput USB game controller interface) When you map a joystick button to a button input, it only says [joystickbutton#] This is a problem because the input maps between gamepad and flight stick can be VERY different
This is an old Unaddressed problem, dating back as long as there's been game controller support.
Disclosure: I was an Experimentals team member and may have raised this in the past
History
#1 Updated by drdeath over 4 years ago
- Platform Linux added
This Issue still persists. I managed to get a button assignment to Joystick1Button1 once, but was never able to reproduce this behaviour. When the config file is manually edited to contain e.g. Joystick1Button1 or Joystick0Button1, the game interprets it correctly.