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 [Package]
1.1.0-preview.3
Issue ID
1352117
Regression
Yes
Keyboard Input is ignored when the second Binding of the same InputAction is set to minimal value
Steps to reproduce:
1. Open the attached project "input.zip"
2. Open Scenes/SampleScene
3. Select the GameObject in the Hierarchy window
4. Double-Click on the Rz [Generic USB Joystick] in the Inspector window
5. Set Binding Path to your controllers analog stick
6. Enter the Play Mode
7. Hold the analog stick down to set Input value to -1
8. Press W key
9. Observe the Input value in the Inspector window
Expected result: Input value changes from -1 to 1
Actual result: Input value stays -1
Reproducible with: 1.1.0-preview.3 (2019.4.30f1, 2020.3.17f1, 2021.1.19f1), 1.1.0-pre.6 (2019.4.30f1, 2020.3.17f1, 2021.1.19f1, 2021.2.0b9, 2022.1.0a6)
Not reproducible with: 1.0.2 (2019.4.30f1, 2020.3.17f1, 2021.1.19f1)
Comments (1)
-
pitchblende
Aug 30, 2021 22:05
Watching.
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:
Will now be fixed as part of future development effort to implement proper racing wheel support.