Search Issue Tracker
Fixed
Votes
1
Found in
2017.4
2019.3.5f1
2020.2
Issue ID
1228716
Regression
No
Generated Lightmap has visual artifacts when using Progressive CPU/GPU Lightmapper
How to reproduce:
1. Open the attached project's "case_1228716-Project.zip" Scene labeled "test2"
2. Open the Lighting Settings (Window->Rendering->Lighting Settings)
3. In the Lighting Window, select the Progressive CPU/GPU Lightmapper
4. Press "Generate Lighting"
5. Wait for the Lightmap baking to finish
6. Observe the Scene View
Expected result: Generated Lightmap doesn't have any artifacts
Actual result: Generated Lightmap has visual artifacts
Reproducible with: 2017.4.19f1, 2018.4.20f1, 2019.3.6f1, 2020.1.0b3, 2020.2.0a5
Note: Using Enlighten Lightmapper doesn't reproduce the issue
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This is not a bug. The artifacts are caused by the invalid GI texels produced by the shadow casting plane's backface. To fix this issue you need to enable the double-sided GI support on the material inspector. This feature is supported by both CPU and GPU Progressive Lightmappers.
Steps to fix the issue:
1. Create the new material and assign it to the 'Plane' gameobject (shadow caster);
2. In the material Inspector enable "Double Sided Global Illumination" checkbox;
3. Rebake the GI either with CPU or GPU Lightmapper.
Attaching the screenshot, fixed project and resolving the case by design.