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.0.0 (preview 6)
Issue ID
1229316
Regression
No
Binding mouse position on an action will override any other bindings even when not moved
When binding Position of the mouse to an action, the value will always be reported through ReadValue, even if the mouse wasn't moved but the other binding (e.g. a gamepad Thumbstick) was triggered. This is fixed when the Action Type is changed from Value to Pass Through
On the attached project, just open WorkingScene with a gamepad connected. Click play and don't move the mouse. The right pad thumstick will rotate the character. Move the mouse, the character will rotate to point toward the mouse, but now the thumbstick won't work anymore. Changing the Orient action type to "Pass through" on the Input Action Asset called PlayerActions in the Root Folder will fix the problem.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error ‘cannot use casts on l-values’ when a variable is assigned inside a second-level nested if statement before being used in a conversion
- "You cannot save to an invalid folder" warning dialog box is shown when canceling Tile Palette creation
- Global Volume visual details are blurred when Tonemapping mode is set to any other than 'ACES'
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
Add comment