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
2017.1.0b7
Issue ID
922703
Regression
No
The first time GetButton returns true all other GetAxis reset to zero
Steps to reproduce:
1. Open attached project "922703.zip"
2. Open "test" scene
3. Enter play mode
4. Hold 'A' or 'D' key to alter Horizontal axis value
5. Without releasing the key press Mouse button to trigger Fire1 axis
*Editor pauses*
Actual behavior: the frame when GetButton returns true for the first time in play mode all other GetAxis reset to zero
Expected behavior: axes values are not reset to zero
Notes:
Not reproducible on standalone
In 5.6 axis value keeps growing after resetting it, in 2017 the held key needs to be released and pressed again to alter axis value
GetButton resets axes values only the first time it returned true
Reproducible with: 5.6.1f1, 2017.1.0b10, 2017.2.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment