Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0b4
2019.2.0b7
Issue ID
1163991
Regression
Yes
[Editor] Visibility state is not being saved while working in multiple scenes
Visibility state for GameObjects is not being saved after removing or unloading the additive scene
Steps to repro:
1. Create a new project
2. Add to scenes to the hierarchy
3. Hide GameObjects in the additive scene
4. Click on burger button next to scene name
and Save the scene
5. Again click burger button and remove the scene
6. Open scene
Actual Result:
The visual state is not being saved on additive scene
Expected Result:
The visual state is saved for the scene
Occurs on:
2019.3.0a7, 2019.2.0b7, 2019.1.4f1, 2019.1.0b4
Works with:
2019.1.0b3
Environment:
Windows 10 and MacOS 10.14
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