Search Issue Tracker
Duplicate
Duplicate in 2019.3.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2020.1.0a9
Issue ID
1236310
Regression
No
[PLM] First small lightmap blocks following bigger lightmaps from being scheduled
When progressive updates is enabled, if there is enough memory for a first lightmap (a small one) but not enough memory for one of the other ones (bigger) baking is stuck in an endless loop.
Nothing gets printed in the console and nothing happens.
This bug is reproducible with both CPU and GPU Lightmapper.
On the GPU lightmapper when encountering this bug we don't even fallback to CPULM.
Repro:
You can repro the bug using the archvizpro scene using a 32GB CPU Ram machine, with 4k lightmaps and antialiasing set to at least 4.
The first 512x512 lightmap will get rendered and converged and then you will be stuck in an infinite loop that never starts the 3 other lightmaps which are 4k lightmaps
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
- [macOS] Project fails to load when Virtual Artifacts are Corrupted
- Long scheduler times on main thread when using InstantiateAsync with a singular massive Prefab
- The project hangs upon opening it when importing the "discrete_rank2_vector_v2_0.onnx" file
- Opening the Look Dev hangs the Editor when the window is opened for the first time in the project or after deleting the Library folder
- Look Dev has blurry icons on 4k monitors
This is a duplicate of issue #1199574