Search Issue Tracker
Fixed
Fixed in 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Votes
2
Found in
6000.2.4f1
6000.3.0a6
6000.4.0a1
Issue ID
UUM-117081
Regression
No
UI Toolkit input becomes unresponsive when the UIDocument GameObject is destroyed
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Repeatedly click the Button with text “Toggle UI B (SetActive)“
Expected result: Button always reacts to clicks
Actual result: UI input becomes unresponsive
Reproducible with: 6000.0.57f1, 6000.2.4f1, 6000.3.0a6
Reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2, macOS (user reported)
Not reproducible on: No other environment tested
Notes:
- Issue seems related to “captured = this.GetCapturingDocument(pointerId, out capturingDocument);”
- PointerDeviceState.s_PlayerPanelWithSoftPointerCapture doesn't seem to be reset correctly when the UIDocument is destroyed
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture memory does not get released when using Direct3D12 Graphics API
- Element background colors change places in Game window after reopening UI Builder
- Unity Theme can't be changed when any compilation errors are thrown
- Editor layout does not save custom Editor windows when they are declared using file-scoped namespaces
- Crash on VFXManager::CollectShadowCullResults when opening a specific scene
Add comment