Search Issue Tracker
Fixed
Fixed in 2020.3.43f1, 2021.3.17f1, 2022.2.0b10, 2023.1.0a11
Votes
0
Found in
2020.3.35f1
2021.3.5f1
2022.2.0a17
2023.1.0a1
Issue ID
UUM-3535
Regression
No
Highlighter.Highlight does not disappear when the highlighted element disappears from view
How to reproduce:
1. Open the attached "case_1379559.zip" project
2. Open the "SampleScene" Scene
3. Open the HighlighterTest window (Bug > HighlighterTest) and dock it together with the Project window
4. Select the "Directional Light" GameObject in the Hierarchy
5. Make sure that the "Rigidbody 2D" Component is visible in the Inspector
6. Press "Start Highlight" in the HighlighterTest window
7. Press on empty space in the Hierarchy
Expected result: The highlight disappears
Actual result: The highlight does not disappear
Reproducible with: 2019.4.33f1, 2020.3.24f1, 2021.2.5f1, 2022.1.0a16
Note:
- Not reproducible on macOS
- The highlight disappears after closing the window where the highlighted element is
- The highlight disappears after entering Play mode
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 PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
Resolution Note (fix version 2021.3.17f1):
Fixed in: 2021.3.17f1
Resolution Note (fix version 2020.3.43f1):
Fixed in 2020.3.43f1