Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0a7
Issue ID
975304
Regression
No
[PLM] Progressive Lightmapper goes OOM with View Prioritization enabled
Steps for reproductıon:
1) Open attached project
2) Ensure that baking backend is set to Progressive Lightmapper
3) Ensure that `View Prioritization` is enabled
4) Start baking
5) Observe that baking goes out of memory
Expected result: Progressive Lightmapper memory usage should not be this high, memory should be released even with `View Prioritization` enabled
Notes:
- Reproducible in all the versions
- Manual baking doesn't go out of memory
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment