Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.4.4
1.5.1
1.6.1
Issue ID
ISXB-559
Regression
No
UI menu elements are not affected by the cursor input in Play Mode when using the controller and cursor at the same time
How to reproduce:
1. Open the "IN_40194" project
2. Connect Xbox One controller
3. Open the "AppLoader" Scene
4. Enter the Play Mode
5. In the Game view on the Xbox controller press "A" -> "A" -> "Start"
6. Navigate with the joystick through the menu
7. Navigate with the cursor through the menu
Expected result: UI elements are affected by the cursor input and by the joystick
Actual result: UI elements are affected only by the joystick input
Reproducible with: 1.4.4, 1.5.1, 1.6.1 (2022.3.3f1, 2023.1.1f1, 2023.2.0a20)
Couldn't test with: 2021.3.27 (due to an error in the Console)
Note: not reproducible in the Player (tested Windows Standalone and WebGL)
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
- 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
Resolution Note:
After analysis this comes from the usage of the Addressable package.
The InputAction asset is duplicated at runtime.
Here is a post that explain it https://discussions.unity.com/t/duplicate-scriptable-object-issue-and-how-to-avoid/857164
To fix it in your project you should put the inputactions asset in an addressable and ensure that the defaults scenes doesn't use it directly.