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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment