Search Issue Tracker
Fixed in 2019.3.X
Won't Fix in 5.6.X
Votes
45
Found in
5.3.4f1
Issue ID
825492
Regression
No
[MSE] Additively loaded scenes use light probe data from first loaded scene
Steps to reproduce:
1. Open attached project "825492.zip"
2. Inspect all of the scenes, notice that each has lightprobes baked individually
3. Open scene "Scene_A" and drop "Scene_B" to hierarchy to enable MSE
4. Move green light of scene "Scene_A" and notice that light probes of "Scene_B" uses light of "Scene_A" but whole group of scenes use probe position of "Scene_B"
Reproduced with: 5.3.6p2, 5.4.0p4, 5.5.0b1
-
ksfox
Jul 20, 2017 02:46
I think this is still a problem in 5.6.1f1
-
dishmop
Jul 08, 2017 14:33
Addendum to last comment - I am not using realtime GI - I am just using normal old fashioned baked lighting.
-
dishmop
Jul 08, 2017 14:32
I still have this issue in 5.6.2f1 - this should not be marked as fixed.
-
Simeon
Jun 19, 2017 14:03
Still Found in Unity 5.6.1f1
-
eDmitriy
May 28, 2017 07:11
5.6.1.p1 - still have this bug
-
DavidMarchessault
Apr 12, 2017 15:46
I second this, it is two major built-in systems not compatible with each other. Unless it changed through versions, it seems that the lightprobe data is not the first one loaded but the last scene loaded now. But it still corrupts the lighting of other scenes
-
sanmn19
Feb 03, 2017 09:18
Please fix this bug. It's been there since a year. It's almost impossible to build realtime GI enabled games using this. How can you expect us to make games using enlighten when such a critical bug is there in the system?
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2019.3):
This issue has been fixed with introducing the light probe merging feature for additively loaded scenes: https://docs.unity3d.com/ScriptReference/LightProbes.Tetrahedralize.html. If you still can reproduce it after applying this feature, feel free to reopen the case.