Search Issue Tracker
By Design
Votes
0
Found in
5.6.1f1
Issue ID
921128
Regression
Yes
[MSE] Lighting settings don't change when editing multiple scenes and new Active Scene is selected
To reproduce:
1. Open attached project "Lighting Test.zip".
2. Open Lighting settings window, and observe that "Scene_1" and "Scene_2" have different Lighting settings.
3. Open "Scene_1", and add "Scene_2" into hierarchy, to have multiple scenes.
4. Set active scene to "Scene_2".
Expected result: Lighting settings should display all settings of the new active scene.
Actual result: After changing active scene, settings of the first scene are shown. (only Realtime and Mixed Lighting settings are shown correctly, of the new Active Scene)
Reproducible: 5.6.0b2, 5.6.2f1, 2017.1.0b10, 2017.2.0a4
Not reproducible: 5.5.4p1, 5.6.0b1
Workaround:
Remove or Unload the 1st scene, to see Lighting settings of a new Active Scene.
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