Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2020.1.4f1
2020.2
Issue ID
1274736
Regression
No
Progressive lightmapper and Enlighten Baked GI results don't match
Reproduction steps:
1. Open attached project "Progressive.zip"
2. Open scene "Scene1", in Scene View, examine GameObjects
3. Open scene "Scene2", in Scene View, examine GameObjects
Expected result: No visual differences
Actual result: Visual differences
Reproducible with: 2018.4.27f1, 2019.4.10f1, 2020.1.5f1, 2020.2.0b2
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 throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
Resolution Note:
The way Enlighten and Progressive Lightmappers generate GI, is fundamentally different. That's one of the reasons why there are differences in output. Enlighten uses as many bounces as needed to reach convergence, which is defined by a threshold value.
Progressive lightmappers use a fixed number of bounces that you can define in the UI. The higher the number, the more paths the lightmapper will create. This will result in longer baking times, but a brighter/more realistic output. In 2020.2, we now allow users to set up to 100 bounces, as opposed to the previous maximum of 4.
While you can always boost the Albedo and Indirect Intensity values, doing so will result in non-PBR compliant lighting. Instead, we'd recommend increasing the light intensity and the bounce count.