Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.2.2f1
Issue ID
1087988
Regression
No
[LightProbes] Additively loading Light Probes when using Realtime GI causes probe values to rest to ambient
Version 2018.2.10f1 (674aa5a67ed5)
Thu, 20 Sep 2018 09:27:53 GMT
Branch: 2018.2/release
Repro:
01 - Clone and update the following repo: https://ono.unity3d.com/test-data/gi-tests/AdditiveLighting -r 48ac9a071d3b
02 - Open the Scene TESTSCENES/MASTER.unity
03 - Generate lighting for the current Scene constellation.
04 - Save all Scenes to write references to Scene files
05 - Look at the lovely red lighting in the red plane's light probes. So hot. So red. Mmmmm.
06 - Unload the Scene Red_PlaneWithProbes from the Unity Hierarchy.
07 - Load Red_PlaneWithProbes again.
Observe:
Light Probes that were unloaded and reloaded now fall back to the ambient colour coming from the Skybox.
Expected:
As the Lighting Data asset has not been unloaded or replaced, these Light Probes should recover the red indirect they had before. Infact, if you rebake the Scene using BakedGI, this is the behaviour you get.
What's even more unexpecteder is that if you Save All after the lighting generation (Realtime GI) and then close the Scene. Repoen and then do the unload/reload from the repro steps above, you _do_ get the expected behavior.
I can't even...
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
Add comment