Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.3.0a1
2018.1.0b6
Issue ID
1005672
Regression
Yes
Unchecking a Static flag for an object hierarchy displays an incorrect message
How to reproduce:
1. Open any project
2. Create a game object and add a child game object to it
3. Set Static = true on both game objects
4. Select the parent game object, click on the drop-down next to the "Static" checkbox and remove one of the Static flags
5. Observe the message - a number is shown instead of the name of the flag ("StaticFlagsMessage.jpg")
Expected result: pop-up message "Do you want to disable the Lightmap Static flag for all the child objects as well?"
Actual result: pop-up message "Do you want to disable the -127 flag for all the child objects as well?"
Reproduced with: 2017.3.0a1, 2017.3.1p2, 2018.1.0b9, 2018.2.0a2
Not reproducible with: 2017.2.1p4
Fixed in: 2018.2.0a4
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