Search Issue Tracker
Fixed in 1.3.0
Votes
0
Found in [Package]
1.1.1
Issue ID
1371332
Regression
Yes
UI Navigation stops working after adding two Input Devices to a Scene
Reproduction steps:
1. Open the attached "1371332_2.zip" project
2. Open the "GameScene" Scene
3. Enter the Play mode
4. Press the spacebar key on the keyboard to add a player to the Scene
5. Press the Esc key on the keyboard twice to open and close the UI
6. Press the south button on the controller to add another player to the Scene
7. Press the start button on the controller to open the UI
8. Press the left button on the D-Pad of the controller
Expected result: The red button in the UI is selected
Actual result: The green button in the UI stays selected
Reproducible with: 1.1.1 (2020.3.22f1)
Not reproducible with: 1.1.0-pre.6 (2020.3.22f1)
Could not test with: 1.1.0-pre.6 (2019.4.32f1), 1.1.1 (2019.4.32f1) (Scene freezes), 1.1.0-pre.6 (2021.1.28f1, 2021.2.1f1, 2022.1.0a13), 1.1.1 (2021.1.28f1 2021.2.1f1, 2022.1.0a13) (Multiple console errors)
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 1.3.0):
Fixed in: 1.3.0