Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
5.6.1f1
Issue ID
935301
Regression
No
Lighting Data Asset is instantiated from another scene when duplicating scene
Reproduction steps:
1. Create and open a new project (or use the attached);
2. Change the default light from Directional to Area (baked only), change its color (ex: blue).
3. In Lighting window, click on Generate Lighting -> notice the Lightmap created, with blue faces of your cube visible.
4. In Project window, duplicate the scene (ctrl+D)
5. In the new scene, change the color of the light (ex: red).
6. In Lighting window, click on Generate Lighting -> notice the Lightmap created, with red faces of your cube visible.
7. Open the first scene -> notice your lightmap has disappeared.
Expected results: both scenes will have their specific lightmaps.
Actual results: the original first scene lightmap disappears after baking the second one.
Reproduced on: 5.5.3p3, 5.6.1f1, 2017.1.0p2, 2017.2.0b5, 2017.3.0a2.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment