Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2019.3.12f1
2019.4
2021.1
Issue ID
1247466
Regression
No
[macOS] trigger input is not processed on some gamepads
Reproduction steps:
1. Open the project in "SuperInput.zip"
2. Connect a controller to your device
3. Enter Play Mode
4. Try pressing left and right triggers
Expected result: Input is processed and trigger presses are displayed (like with other buttons)
Actual result: Input is not processed when pressing triggers
Reproducible with: 2019.4.12f1, 2020.1.9f1, 2020.2.0b7, 2021.1.0a1.495
Could not test with 2018.4 because references get removed (also getting errors)
Issue reproducible with both Built-in and Input System Package Input
Controllers tested:
Reproducible with:
Razer Serval (tested by the customer)
Nvidia Shield
Not reproducible with:
Dualshock 4
Xbox One
Media-tech (do not know the model)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Resolution Note:
Postponing until further notice due to higher priority needs. We hope to revisit this at a later time.