[Feature request] Improved Joystick/Gamepad Support

[JebKerman91]

Improved Joystick/Gamepad support

The current joystick support is extremely limited:

• only one device can be selected
• pitch and roll control axes cannot be reassigned
• the throttle control axis must be assigned from a fixed drop down menu (Z, RZ axes) without any feedback on whether the selection is as the user intended

Many modern HOTAS implementations separated the stick and throttle in different devices, each independently connected via USB.

Examples include the common Thrustmaster Warthog HOTAS, and many stick/throttle devices manufactured by others, that can normally be combined with each other. With the current implementation it is also not possible to use rudder pedals, since in almost all cases these are a separate device.

Wishlist - essentials:

• ability to assign throttle, pitch, roll and rudder axes to any compatible joystick/HID device, even separate ones

Wishlist - nice to have:

• ability to have a feedback on the current input, e.g. axis position of any assigned axis, button status
• ability to search for an input based when pressing the corresponding assigned button (might not be useful if the number of standardized assignments is low)
• ability to assign RCS movements (rotation pitch, roll and yaw, as well as translation axes) to buttons
• ability to assign wheel brakes to either buttons or axes
• ability to set a button of a detected HID device as a custom shift modifier to be used (as made possible e.g. in Digital Combat Simulator's setup menu), to be used when it's desired to assign multiple commands to a single physical button
  • in general DCS's control setup implementation currently represents the gold standard in feedback provided to the user, flexibility and responsiveness

[TheGondos]

I have a prototype with a graph based joystick configuration UI. I'll see if I can make a video to get some feedback on it, it should cover all your requirements.

[Urwumpe]

I have a prototype with a graph based joystick configuration UI. I'll see if I can make a video to get some feedback on it, it should cover all your requirements.

Can you make it at least partially reusable in the sense, that certain key modifier assignment must not be repeated all the time in the graph?

I think having a dedicated "logical key" for directing keypresses to a MFD might make sense.

[JebKerman91]

I have a prototype with a graph based joystick configuration UI. I'll see if I can make a video to get some feedback on it, it should cover all your requirements.

This sounds extremely intriguing - I'm looking forward to seeing it!

[TheGondos]

Sorry no vid, google fucks are not satisfied with my 64 characters long password + email OTP validation, they now want my phone number. No siree Bob...
You can look here if you want to have an example