Search Issue Tracker
Fixed in 1.3.0
Votes
0
Found in [Package]
1.1.0-pre.5
Issue ID
1347829
Regression
No
InputAction.controls are accessed slower when the gamepad/controller is not connected
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode (with the controller connected)
3. Inspect the delay at which the InputAction.controls is accessed
4. Disconnect the controller
5. Inspect the delay again
Expected result: Delay to access the InputAction.controls is insignificant (~0.02ms)
Actual result: Delay to access the InputAction.controls is a lot larger with the gamepad/controller disconnected (~10ms)
Reproducible with: 1.1.0-pre.5 (2019.4.29f1, 2020.3.14f1, 2021.1.16f1, 2021.2.0b4, 2022.1.0a2)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.3.0):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1437.