Search Issue Tracker
Fixed
Fixed in 6000.3.0b2, 6000.4.0a1
Votes
0
Found in
6000.3.0a5
6000.4.0a1
Issue ID
UUM-114511
Regression
No
[Hierarchy V2] Marking objects as static in the Hierarchy window does not match the Inspector workflow
Steps to reproduce:
- Open the attached project
- Open the Test Scene
- Select the "GameObject (1)" GO in the Hierarchy (Nested under "GameObject")
- In the Inspector window, mark the Object as Static
- Expand the Static Drop-Down menu
- Observe, that all flags were enabled
- Unmark the Object as Static in the Inspector window
- In the Hierarchy window, check the Static flag for the "GameObject (1)"
- Check the Static flags in the Inspector again
Actual results: Only the "Contribute GI" static flag was enabled when marking the object as static via the Hierarchy window
Expected results: Marking the object as static in the Hierarchy window enables the same static flags as by doing it via the Inspector window
Reproducible with versions: 6000.3.0a2, 6000.3.0a5
Can’t test with versions: 6000.0.56f1, 6000.1.16f1, 6000.2.1f1, 6000.3.0a1 (Hierarchy V2 not available)
Tested on (OS): macOS 15.6, Ubuntu 24
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