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
- “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
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
Resolution Note (fix version 2019.3):
GPU lightmapper now supports sub-meshes/material IDs.