Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1p2
Issue ID
941887
Regression
No
[PLM] Directional maps are different between Enlighten and Progressive Lightmapper when there are overlapping lights
Directional maps are different between Enlighten and Progressive Lightmapper when there are overlapping lights
To reproduce:
1) Open attached project
2) Open Global Maps in Lighting tab (it's already set to auto build, so if there's nothing there, wait a bit)
Expected: The results between old default and Progressive don't differ too much
Actual: Progressive looks like it has no depth and just overlays two spheres
Tested in 5.5.2f1, 5.5.4p4 vs 5.6.3p2, 2017.3.0a6
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
- 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
Resolution Note:
The Progressive lightmapper is producing the correct result.
Since this issue is isolated to the Enlighten backend we are not going to spend resources on fixing this ATM. I suggest instead using the Progressive Lightmapper, which since 18.1 is also the default lightmapper.