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
- [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
Add comment