[Runtime Issue]: XBox Controller registers triggers as [-1, 1] axes instead of [0, 1]

[tophyr]

Build Version

87f6ef0

Operating System Environment

• Microsoft Windows (32-bit)
• Microsoft Windows (64-bit)
• Mac OS X
• Linux (specify distribution and version below)

CPU Environment

• x86 (32-bit Intel/AMD)
• x86_64 (64-bit Intel/AMD)
• ARM (32-bit)
• ARM64 (64-bit; sometimes called AArch64)
• Other (RISC V, PPC...)

Game Modes Affected

• Single player
• Anarchy
• Hyper-Anarchy
• Robo-Anarchy
• Team Anarchy
• Capture the Flag
• Bounty
• Entropy
• Hoard
• Monsterball
• Cooperative

Game Environment

No response

Description

XBox Controller's "trigger buttons" are continuous-value controls, which are detected (somewhat sensibly) as joystick axes in the game. However, the game assumes that the axis range is both positive and negative, when in reality the trigger should be mapped as a positive-only axis. The result of this is that an untouched trigger is always detected as being the maximally-negative value.

Regression Status

No response

Steps to Reproduce

No response

Can confirm it also happens on Linux x86_64

[Lgt2x]

I have an early draft for analog trigger support over at #600 . I don't have an XBox controller at hand but could reproduce with another gamepad (in my case Gamecube controller with adapter). It may need some tuning but the basics should work, if one of you wants to give it a try.