Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.1.0f1
Issue ID
923684
Regression
No
[PLM] Atlas packing of lightmaps is not optimized
Progressive lightmapper unnecessarily splits UV charts into multiple lightmaps
Steps for reproduction:
1) Open the scene `LightmapSplit`
2) Choose Progressive Lightmapper as the baking backend and generate the lighting
3) Observe that there are two intensity and directional lightmaps
4) Change the baking backend to Enlighten and generate the lighting again
5) Observe that there are only one intensity and directional lightmaps
Notes:
- Even though there is enough space in the first lightmap layout, UV charts are split into a second lightmap
- This issue becomes an important problem when working with lots of geometry
- Atlas packing is correctly handled in Enlighten
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Postponed against feature work.