Search Issue Tracker
By Design
Votes
0
Found in
2018.3.1f1
Issue ID
1117222
Regression
No
GPU Lightmapper bug
1. What happened
High geometry density such as trees and foliage on modified terrain result in unusable lightmap results when using GPU progressive lightmapper.
2. How we can reproduce it using the example you attached
Simply open up the project and switch to "Baked Lightmap" Scene mode. Issue will be immediately obvious. To reproduce, you can clear the lighting data and re-bake using the provided settings.
There are 2 examples: dense foliage on flat terrain, and dense foliage on complex terrain. While the complex terrain one is unusable in any capacity, even the flat terrain example shows some "square-pattern" artifacting from the bake process.
The final issue in the development enviroment is outlined in this Unity Forum thread:
https://forum.unity.com/threads/gpu-lightmapper-bug-corrupts-lightmap-near-the-end-of-bake.612445/
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Resolution Note:
This issue is caused by the lack of Double Sided GI support in GPU lightmapper in Unity 2018.3. Double Sided GI support for GPU PLM will be made available in Unity 2019.1.