Search Issue Tracker
Fixed
Fixed in 2020.3.37f1, 2021.3.7f1, 2022.1.7f1
Votes
0
Found in
2020.3.34f1
2021.3.3f1
2022.1.1f1
Issue ID
UUM-916
Regression
No
Assigning a lighting data asset causes the lightmaps to be unloaded for all scenes except the active one
With multiple scenes opened in Unity. Assigning a lighting data asset in the lighting window tab, causes the lightmaps for the other scenes to be unloaded in the editor 3D view. Bug discovered while investigating that other issue: https://fogbugz.unity3d.com/f/cases/1347479/
Steps to reproduce:
You can use the project from https://fogbugz.unity3d.com/f/cases/1347479/: https://bugs.unity3d.com/fogfiles/134xxxx/1347479_icgk96oqsg6rrk77/ (but it is reproducible as long as you open at least 2 scenes in additive mode the editor)
- Open additively at least 2 scenes
- Bake lighting
- Go to Lighting Window / Baked Lightmaps / Lighting data asset field
- In the Lighting Data Asset field click on button on the right to open the "Select Lighting Data Asset" popup. Click on the currently assigned lighting data asset
- Now all baked lighting data has disappeared for the other scene. For instance the lightmaps list is now shorter and in the editor view gameobjects of the other scene have lost their lightmaps.
Expected behaviour: assigning the same file in the Lighting Data Asset field should not change anything
Reproducible with 2022.2.a01, 2022.1.b1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Incorrect ScrollToItem behavior when called on a deattached ListView
- Zooming in/out in Scene View window on the display the zoom takes place in does not work
- Changing Game View resolution when there are 2 Game View Windows on 2 different displays makes the view stretched
- Maximising Game view window on one display makes black bars appear on another display
- Creating a 3D Object when using 2 monitors and 2 Game View Windows on different monitors the created 3D Object only appears on one of them
Resolution Note (fix version 2022.1.7f1):
Fixed in 2022.1.7f1