Search Issue Tracker
Active
Under Consideration for 6000.6.X
Fixed in 6000.6.0a2
Won't Fix in 6000.3.X, 6000.4.X, 6000.5.X
Votes
0
Found in
6000.3.3f1
6000.4.0b3
6000.5.0a4
6000.6.0a1
Issue ID
UUM-131952
Regression
No
GameObject pickability cannot be toggled on the new Hierarchy window when ALT is held
How to reproduce:
- Create and open a new project
- Go to Edit → Preferences → General
- Enable the ‘Use new Hierarchy window’ option
- Create a few GameObjects in the Hierarchy
- Parent some GameObjects to other GameObjects
- Expand the parent GameObjects
- Hold ALT and left-click the 'Pick' (hand icon) icon to the left of the parent GameObjects in the Hierarchy
- Observe the Hierarchy
Actual result: The ‘Pick’ functionality is not toggled
Expected result: The ‘Pick’ functionality is toggled just for the parent GameObject
Reproducible in: 6000.3.0a2, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Could not test in: 6000.0.65f1, 6000.3.0a1 (The new Hierarchy was not introduced yet)
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Notes:
- Generally, when ALT is not held, enabling ‘Pick’ on a parent GameObject enables the ‘Pick’ function of all its children GameObjects vs when AlT is held, only selected object is toggled.
- Not reproducible in the old 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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 6000.6.0a2):
Fixed in 6000.6.0a2
Resolution Note (6000.5.X):
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.
Resolution Note (6000.4.X):
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.
Resolution Note (6000.3.X):
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.