Search Issue Tracker
Feature Request
Feature Request in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.2.15f1
6000.3.2f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131325
Regression
No
Hidden objects count is not displayed when multiple objects are hidden in the Scene view
How to reproduce:
1. Create and open a new project
2. In the Hierarchy create 10 Cube GameObjects
3. In the Hierarchy hide all Cube GameObjects using the Eye icon
4. In the Scene view, observe Eye icon in the top right
Actual result: “10” is displayed next to the Eye icon
Expected result: No number is displayed next to the Eye icon
Reproducible with: 2023.1.0a1, 6000.0.65f1, 6000.2.15f1, 6000.3.2f1, 6000.4.0b3, 6000.5.0a4
Reproducible on: macOS Tahoe 26.1
Not reproducible on: no other environments tested
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
Thank you for sharing your idea with Unity.
We reviewed your report and determined that it's a feature request rather than a bug. We've logged this request in our system so it can be evaluated for future roadmap planning. We created a ticket to implement an improvement in that direction in the upcoming versions of the Editor.
We will close this case as a feature request. While we can't guarantee timelines, your feedback is important and helps us prioritize enhancements. If you have additional context or use cases, please share them.
Resolution Note (6000.5.X):
Thank you for sharing your idea with Unity.
We reviewed your report and determined that it's a feature request rather than a bug. We've logged this request in our system so it can be evaluated for future roadmap planning. We created a ticket to implement an improvement in that direction in the upcoming versions of the Editor.
We will close this case as a feature request. While we can't guarantee timelines, your feedback is important and helps us prioritize enhancements. If you have additional context or use cases, please share them.