Search Issue Tracker
By Design
Votes
0
Found in
2022.3.14f1
2023.2.2f1
2023.3.0a16
Issue ID
UUM-57617
Regression
No
Lighting data is carried over from one Scene to another when changing Scenes in the Play Mode
How to reproduce:
# Open the “UnityProject.zip“ project
# Open the “SampleScene“
# Enter the Play Mode
# Toggle the button in the Game view
# Repeat step 4 a few times and observe the Game view
Expected result: The lighting data from “Scene_A” is not carried over to “Scene_B“
Actual result: The lighting data from “Scene_A” is carried over to “Scene_B“
Reproducible in: 2022.3.14f1, 2023.2.2f1, 2023.3.0a16
Could not test in: 2021.3.33f1 (There is no Shading in “Scene_A”, for an unknown reason)
Reproduced on: Windows 11 Pro
Not reproduced on: no other environment tested
Note: The issue is only reproducible in Play Mode
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
Thanks for filing this report with us.
After reviewing the reproduction project, it is evident that this behavior is "as designed". You must call LightProbes.Tetrahedralize or LightProbes.TetrahedralizeAsync after loading your scenes to update the global light probes structure to the current scene setup.