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
3
Found in [Package]
1.1.0-preview.2
Issue ID
1306392
Regression
No
[macOS] Input from an an Xbox Elite S2 controller is not registered
How to reproduce:
1. Create a new Unity project
2. Install the Input System package
3. Go to Window > Analysis > Input Debugger
4. Connect an Xbox Elite S2 controller to the computer and double-click on it in the Input Debug window
5. Try moving around the joystick or pressing buttons on the gamepad while observing the respective values under Controls (Editor State)
Expected results: input from the gamepad is registered
Actual results: input from the gamepad is not registered
Reproducible with: Input System 1.1.0-preview.2 (2020.2.2f1)
Couldn't test with: 2018.4 (no longer tested with Input System), 2019.4, 2021.1, 2021.2 as we don't have access to an Xbox Elite S2 controller
Notes:
- Tested with macOS 10.15.17
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
- Basic UI Toolkit panels do not render when using URP+RenderGraph+D3D12
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
Resolution Note:
Postponing until further notice due to higher priority needs. We hope to revisit this at a later time.