Search Issue Tracker
Active
Under Consideration for 6000.5.X
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
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
Add comment