I'm trying to set up Su-25T controls with a wireless X360 controller for a friend to try and convince him to invest into a proper HOTAS (so... for the greater good, hopefully).

Because of some XInput witchcraft, the game recognizes both triggers as two separate axes. I need one of the three:

1. a way to force DCS to use (the obsolete) DirectInput - one of its 'drawbacks' was that the triggers were technically a single axis

2. a mapper of sorts that would remap a genuine gamepad to a non-genuine that just happens to treat both triggers as one axis

3. a way to configure axes in DCS so that get 50% output when NO input on axis is given (I tried a custom user-generated curve with a value of 50 at 0, but it still effectively started with a value of 0 - am I doing it wrong?)

Does anyone have any solution to any one of those? Other solutions are, of course, welcome...

And yes, with proper curvature, deadzones and modifiers, it's surprisingly flyable, and has more commands mapped than my T16000M TWCS

EDIT: found a workaround to #3... For future generations, the way to do this is:

1. assign both triggers to rudder

2. in axis tune options, invert the left trigger and set both to sliders, set any deadzone

3. find the saved config file in your home folder and manually set the deadzone to -1 for both triggers