DescentDevelopers / DescentDevelopers/Descent3
[Runtime Issue]: XBox Controller registers triggers as [-1, 1] axes instead of [0, 1]
- Dominant language
- C++
- Stars
- 3k
- Forks
- 285
- PR merge metrics
- No merged PRs in 30d
Description
### Build Version
87f6ef00
### Operating System Environment
- [ ] Microsoft Windows (32-bit)
- [ ] Microsoft Windows (64-bit)
- [X] 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)
- [X] ARM64 (64-bit; sometimes called AArch64)
- [ ] Other (RISC V, PPC...)
### Game Modes Affected
- [X] 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_
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.