Gamepad Input separate trigger axes?

[Vchat20]

So playing around with trying some older DirectX 8/DirectInput games on the Deck. Working beautifully so far except for one glaring issue and this is a constant for any modern Xinput based controller on older games like this: The L and R triggers are a combined axis but many of these games want separate L and R analog trigger axes. Best I can tell in the controller configurations this cannot be resolved. Anyone have a better idea here or maybe an option I'm missing in the controller configuration?

[austinp_valve]

In gamepad emulation modes we are emulating the behavior of an Xbox360/One controller depending on the API for whatever provides the best game compatibility. Unfortunately, both Xbox 360 and Xbox One controllers show up with the combined trigger axis via Direct Input.

[Vchat20]

Originally posted by austinp_valve:

In gamepad emulation modes we are emulating the behavior of an Xbox360/One controller depending on the API for whatever provides the best game compatibility. Unfortunately, both Xbox 360 and Xbox One controllers show up with the combined trigger axis via Direct Input.

Thank you. Good to know. In the interim I guess I'll be looking for a shim/wrapper of some sort.

I know it is probably a very niche use, but any chance this functionality could be added natively?

[R.Wut]

I just ran into the same issue. It would help if the trigger axis could be remapped so you could for example map the left trigger to the right joystick up/down axis.

[Man's Best Friend]

Having the option to emulate a generic Direct Input controller rather than specifically an Xbox style one would be great for cases like this. Direct Input allows for so much more than just what a standard controller has. 8 axes, 128 buttons, full POV, whatever that last one means.

[R.Wut]

After some more fiddling I managed to map the left trigger to right joystick up by disabling the analog output on the trigger itself and add it back as a command on the soft pull option. The only problem left now is that it only maps the positive range of the joystick axis instead of the full range.