Search Issue Tracker
Fixed
Fixed in 1.5.0
Votes
2
Found in [Package]
1.3.0
1.5.0
Issue ID
ISXB-223
Regression
No
Controllers with gyroscope inputs always become the current Gamepad when they are connected
How to reproduce:
# Open the attached project "InputSystem_Controller_Noisy.zip"
# Open the "Entry" Scene
# Connect a controller with a gyroscope
# Enter the Play mode
# Move the mouse
Expected result: The device tracked by update time is the mouse
Actual result: The device tracked by update time is always the controller with a gyroscope
Reproducible with: 1.3.0 (2019.4.40f1, 2020.3.36f1, 2021.3.4f1, 2022.1.5f1, 2022.2.0a17)
Note:
- Tested using PlayStation 5 controller
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 1.5.0):
Fixed in: Input System 1.5.0