Search Issue Tracker
Fixed in 2019.3.X
Votes
2
Found in
Issue ID
1119015
Regression
No
Progressive CPU and GPU lightmappers produce different lightmap results
Steps to reproduce:
1. Download the CornellBox project and open the CornellBox scene
2. Navigate to the Lighting Settings and make sure that the lightmapper is set to Progressive CPU
3. Bake the lighting and observe the result
4. Navigate to the Lighting Settings and make sure that the lightmapper is set to Progressive GPU
5. Bake the lighting and compare the resulting lightmap with the one produced by CPU PLM
Notes:
- The issue is present in all versions of Unity ranging from 2018.3 to 2019.1
- The most profound differences are in the indirect bounce parts of the resulting lightmap
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2019.3):
GPU lightmapper now supports sub-meshes/material IDs.