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
-
j_a_quent
Apr 24, 2020 13:14
This for instance does not work:
SceneManager.LoadSceneAsync("level2", LoadSceneMode.Additive);
LightProbes.TetrahedralizeAsync(); -
j_a_quent
Apr 24, 2020 12:48
How is LightProbes.Tetrahedralize supposed to work? I load a scene additively with 2019.3.1f1 and 2020.1.0a23 and it still doesn't do what it is supposed to.
-
Bergquist
Aug 18, 2019 20:34
This is still an issue in Unity 2019.2.0
Please fix.
- Aaron Bergquist
Sr Unity Developer & 3D Art Director -
keeponshading
Feb 25, 2019 22:26
Is there a chance to get a fix for 2018.3.6 + or has someone found a workaround.
-
Jakub_Machowski
Sep 26, 2018 18:07
We have problem still in 2018.2
-
IN_Luke
Jul 25, 2018 09:11
Is there a possible fix for this yet? Finding it extremely difficult to work with multiple scenes and combining light probe groups.
-
pcg
Jul 11, 2018 08:29
Very disappointed to see that the only progess made on this if you can call it that, up to 2018.2 is to include a warning message telling people this aint going to work!
As there is now no option to vote on this due to it being "Postponed" I'm afraid I will have to vote with my wallet and cancel my subscription to Unity Plus. -
amelierosser
Apr 03, 2018 16:06
Fix this...
-
The_Void_Architect
Feb 22, 2018 16:02
Still happening in 2017.3.1f1, hope it gets fixed soon or I will have to change my scenes from additive to single mode...
-
SteveKouts
Feb 15, 2018 06:51
Not fixed in 2017.3.0f3
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
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
- Error "InvalidOperationException: You are trying to read Input using the UnityEngine.Input class, but you have switched active Input handling to Input System package in Player Settings." is present when using UI Toolkit and New Input System
- "Unable to get the list of approved APIs." is thrown when testing the App Packages with Windows App Certification Kit
- [Linux] The mouse wheel input is inverted when scrolling in the Build
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.