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
-
Ghat-Smith
Dec 13, 2017 21:29
I confirm that it's not fixed in 2017.2. I implemented a temporary solution, detailed in this topic : https://forum.unity.com/threads/how-to-add-update-light-probes-when-using-load-additive.394508/
Hope it will help.
-
castor
Dec 08, 2017 01:23
If this is not fixed, then why is it marked as fixed?
-
kemalakay
Nov 22, 2017 13:53
Lighting team at Unity is well aware about this bug and currently, it is on team's roadmap, it is planned to be addressed during the first quarter of 2018.
Sorry for the inconvenience that this issue causes for you. -
Daerst
Nov 21, 2017 12:59
Here is another closely related (the same?) issue that was reported to be fixed in 2017.3, but could still be reproduced in the latest beta. I contacted the Unity support and they've acknowledged and reopened it.
https://issuetracker.unity3d.com/issues/light-probes-are-not-loaded-when-using-additive-scene-loading -
thepipecat
Nov 13, 2017 19:44
This issue is not fixed.
-
dfarrow
Oct 14, 2017 01:03
I observed this issue on 5.6.2f1. The light probe data used is from the last scene loaded.
-
Infrid
Sep 08, 2017 03:22
I have this in 2017.2 as well. It's basically rendered a whole week of work creating a multi-scene loading engine for smooth loading in VR 100% useless.
Not happy that I'm paying pro for this not to be fixed in a whole year..
-
Polygoat
Aug 24, 2017 07:07
Hitting the same issue in 5.6.2. This is not fixed...
-
SmartCarrion
Aug 02, 2017 20:57
Yup I'm definitely hitting this issue in 2017.1. Planning to try rearchitecting my scenes or something from this thread: https://forum.unity3d.com/threads/light-probes-issue-with-additive-scenes-loading.439790/
-
Simeon
Jul 20, 2017 15:07
Still in Unity 2017.1.0f
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.