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
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
Resolution Note (fix version 2019.3):
GPU lightmapper now supports sub-meshes/material IDs.