Search Issue Tracker
Duplicate
Votes
0
Found in
2018.3.0b3
2019.2.0a2
2019.2.0a9
Issue ID
1143925
Regression
No
Progressive GPU Lightmapper yields different results than Progressive CPU Lightmapper
Steps to reproduce:
1. Open original project "GIBug.zip"
2. Open and compare test_cpu and test_gpu scenes
Expected result: Both scenes lighting should be the same as they were rendered with identical settings
Actual result: Baked light with Progressive GPU differs from lighting baked with Progressive CPU
Reproduced in: 2018.3.12f1, 2019.1.0f1, 2019.2.0a11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Project Auditor Analysis is not marked dirty when the save file is deleted even after reopening the Project Auditor window
- “Shader Graphs” text in the blackboard is hard to see
- "NullReferenceException" error is thrown when changing input field focus via script with custom validation
- The Tables in the Project Auditor’s Assemblies, and Precompiled Assemblies tabs does not scale with the Project Auditor window size which leads to unused empty space and bigger scrollbars in the tables
- Tile Palette button with longer Palette name is misaligned and cut-off when Tile Palette Clipboard overlay is resized
Add comment