Search Issue Tracker
Fixed in 2017.1.0f3
Votes
0
Found in
Issue ID
923670
Regression
No
[Auto][PLM] Lightmap indices of 4K Lightmaps are assigned incorrectly
4K Lightmaps look corrupted when generating lighting with Progressive Lightmapper in auto mode
Steps for reproduction:
1) Download the project below and open the scene `s1`
or
Create lightmap static cube and plane with a baked light
2) Ensure that lightmap resolution is higher than 70 and lightmap size is set to 4096
3) Generate lighting
4) Observe the bug
Notes:
- Not a regression, it was always like that since the introduction of progressive lightmapper
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment