Search Issue Tracker
Fixed
Fixed in 6000.5.0a7
Votes
0
Found in
6000.5.0a5
Issue ID
UUM-132735
Regression
Yes
[macOS] GameObjects get created as children of selected GameObjects in New Hierarchy
Reproduction steps:
1. Create a new project
2. Select any GameObject in Hierarchy
3. Create any GameObject (e.g. right-click > 3D Object > Cube)
4. Observe newly created GameObject in Hierarchy
Actual result: New GameObject is created as a child of the currently selected GameObject
Expected result: New GameObject is not a child of any GameObject
Reproducible with: 6000.5.0a5
Not reproducible with: 6000.0.66f1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a4
Reproduced on: macOS Sequoia 26.2 (M4)
Not reproduced on: Windows 11
Note: Issue is not reproducible when creating GameObject via GameObject menu
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
Add comment