Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.1.0a9
2020.1.0a14
Issue ID
1199574
Regression
Yes
[GPU PLM] Neverending bake when progressive updates are on (available vs total memory)
Kuba:
Introduced by the change from total physical memory to available memory used in GPU lightmapper's scheduling logic: https://ono.unity3d.com/unity/unity/pull-request/91177/_/graphics/gi/radeonrays/openclfreememory#comment-831463
[GPU PLM] Neverending bake in ArchViz project when Progressive Updates is on
Steps to repro:
1. Open the attached project and 'AVP6_Desktop' scene;
2. In the Lighting window enable the 'Progressive Updates' checkbox;
3. In the Lighting window press 'Generate Lighting' button.
Actual result:
Baking is stuck and never finishes. The ETA is jumping up and down constantly.
Expected result:
Baking completes successfully.
Notes:
- Reproducible in 2020.1.0a14;
- Not reproducible with 2019.3.0f4;
- Reproducible on Windows with NVIDIA GeForce RTX 2080;
- Reproducible only for the GPU Lightmapper.
- The issue seems to be introduced with the Progressive Updates feature for the GPU Lightmapper.
- Not reproducible when progressive updates are disabled.
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
dgoodman-icf
Aug 19, 2020 16:20
Found in 2020.1.2f1