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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2019.3):
GPU lightmapper now supports sub-meshes/material IDs.