Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.43f1
2022.3.45f1
6000.0.17f1
Issue ID
UUM-79146
Regression
No
Deselecting a GameObject in the Hierarchy makes that GameObject unable to be shift-selected until click elsewhere
Steps to reproduce:
- Open a Unity project
- Ensure that there are two or more GameObjects in the Scene Hierarchy (if not, create them)
- Select a first GameObject with left-click
- Select a second GameObject with ctrl + left-click
- Deselect the second GameObject with ctrl + left-click
- Shift + left-click the second GameObject
Actual results: The GameObject is not selected
Expected results: The GameObject is selected (and if applicable, any items between that and the first GameObject are selected too)
Reproducible with versions: 6000.0.17f1, 2022.3.45f1, 2021.3.43f1
Not reproducible with versions: -
Can’t test with versions: -
Tested on (OS):
- MacOS Sonoma 14.5
- Windows 11
Notes:
- You can shift select other GameObjects, just not the GameObject you just deselected.
- This does not seem to occur in other places (such as the Project Window), only in the Hierarchy.
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.