Search Issue Tracker
Fixed
Fixed in 2021.3.22f1, 2022.2.4f1, 2023.1.0b3, 2023.2.0a1
Votes
0
Found in
2022.2.2f1
2023.1.0a24
2023.2.0a1
Issue ID
UUM-22208
Regression
Yes
Collider Gizmos are not visible when a child GameObject is selected
How to reproduce:
1. Open the project “IN_26045”
2. Open the “SampleScene” Scene in Scenes
3. Select any “cube” GameObject in the “GameObject” GameObject root
Expected result: BoxCollider Gizmos are visible
Actual result: BoxCollider Gizmos are not visible
Reproducible with: 2022.2.0a1, 2022.2.2f1, 2023.1.0a24
Not reproducible with: 2020.3.43f1, 2021.3.16f1, 2022.1.0a16
Reproducible on: Windows 10 Pro
Note: reproducible with other GameObject and their colliders
Workaround: select the parent GameObejct and then selecting child GameObejcts will allow collision Gizmos to appear visible until other GameObjects are selected
Comments (3)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Milionario
Mar 29, 2023 23:17
This is NOT FIXED on 2021.3.21f1 LTS!!!
shaimaytav
Feb 09, 2023 16:08
I'm having the exact same problem.
abandon_games
Feb 03, 2023 13:23
I'm having this same issue in 2021.3.18f1 - I select a child object that has a collider I get no gizmo, I select its parent then the gizmo appears