Search Issue Tracker
Not Reproducible
Votes
2
Found in [Package]
1.7.0
1.8.0-pre.1
1.8.0-pre.2
Issue ID
ISXB-735
Regression
No
UI input is not interactive when re-entering the Play Mode
Reproduction steps:
1. Open the attached “UITK_Input_Bug_Repro_Project.zip” project
2. Open the “Assets/UITK Input Bug Example.unity” Scene
3. Enter the Play Mode
4. Interact with the button and slider in the Game view
5. Exit the Play Mode
6. Enter the Play Mode
7. Interact with the button and slider in the Game view
Expected result: After re-entering Play Mode, the button and slider are interactive
Actual result: After re-entering Play Mode, the button and slider become unresponsive
Reproducible with: 1.7.0, 1.8.0-pre.1 (2023.2.0a16, 2023.2.5f1, 2023.3.0a14), 1.8.0-pre.2 (2023.2.0a16, 2023.2.5f1, 2023.3.0b2)
Couldn't test with: 1.7.0, 1.8.0-pre.1, 1.8.0-pre.2 (2021.3.34f1, 2022.3.17f1, 2023.2.0a15)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- Make sure that domain reload is disabled in "Configurable Enter Play Mode"
- The regression is in the Editor versions and not the package itself
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:
This issue no longer reproduces within the current Unity 6 release (6000.0.5f1) using the latest 1.8.2 InputSystem package.
It appears to have been fixed by some other Input and UI improvements. If you are still encountering this issue in the current releases please re-open this bug.