Search Issue Tracker
Duplicate
Votes
0
Found in
6000.2.4f1
6000.3.0b1
Issue ID
UUM-116549
Regression
Yes
“Assertion failed” Error is thrown when UI Debugger Usage Hints field value is changed
Steps to reproduce:
1. Create a project
2. Open UI Toolkit Debugger window (Window > UI Toolkit > Debugger)
3. Press “Pick Element” button and select any window (e.g. Project window)
4. Select first dropdown in the UI Toolkit Debugger window
5. Change Usage Hint value to Everything
6. Observe the Inspector window
Actual results: “Assertion failed
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)” error is thrown
Expected results: No errors or warnings are thrown
Reproducible with versions: 6000.2.0a7, 6000.2.4f1, 6000.3.0b1
Not reproducible with versions: 2021.3.56f1, 2022.3.66f1, 6000.0.57f1, 6000.2.0a6
Tested on (OS): macOS Sequoia 15.4 (M4), Windows 11
Note: Error is also thrown when setting the value back to default value
-
Resolution Note:
The hint causing issues is the "Dynamic Postprocessing" hint, which is tracked in another bug.
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-119522
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
This is a duplicate of issue #UUM-115156