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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment