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
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Add comment