Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2018.4.1f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1174524
Regression
No
Subtractive Mixed Lighting used with a Static Shadows Only Object changes when reloading the Scene or entering Play Mode
How to reproduce:
1. Open user-submitted project (SubtractiveStaticShadowOccluder)
2. Open the SampleScene
3. Open the Lighting Settings window and generate lighting
4. Enter Play Mode or save, switch to another scene and switch back
5. See the Scene view
Expected result: the lighting has not changed after entering Play Mode or reloading the Scene; static shadow occluder throws a grey shadow
Actual result: the lighting has changed after entering Play Mode or reloading the scene; static shadow occluder throws a red shadow
Reproducible with: 2017.4.31f1, 2018.4.6f1, 2019.1.14f1, 2019.2.1f1, 2019.3.0a12
Notes:
- Reproduces even if the occluder is set as a SSD which receives GI from light probes
- The issue only happens if the 'Scale In Lightmap' value of the shadow occluder's object is 0
- The issue only happens if the 'Auto Generate' checkbox in the lighting settings is unchecked
- Workaround: set the 'Scale in Lightmap' value of the shadow occluder to a minuscule value(e.g. 0.0001)
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):
SSDs were not written into the Lighting Data Asset, because they are not "baked". However, they influence GI, so they must be marked as such when evaluating shadow casters. This information was ignored, because the Lighting Data Asset is responsible for recreating the state when reloading the scene in the Editor.
Fixed in 2020.1.0a14
Resolution Note (fix version 2018.4):
Fixed in 2018.4.18f1