Search Issue Tracker
Fixed in 5.5.2
Votes
1
Found in
5.5.0f3
Issue ID
874937
Regression
No
Bake Visibility job failure
To reproduce:
1. Open attached project;
2. Open "E1M1-Tutorial10" scene;
3. Bake lights.
Expected result: Editor doesn't freeze when baking.
Actual result: baking stops at 6/16 Bake Visibility on 5.5.0f3 and 7/17 Bake Visibility on 5.6.0b6; Editor freezes.
Reproducible on versions: 5.5.0f3, 5.6.0b6.
Couldn't test on older versions due to project scale. Couldn't reproduce on a small scale.
Note: when baking lights, Unity uses almost 100% of CPU, it is almost impossible to work with computer and the Editor.
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
- [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
rsofia
Jun 06, 2017 23:12
Same thing happened in Unity 5.6.0f3: baking gets stuck on 7/17 Bake Visibility and Unity uses 100% of CPU when baking. Editor didn't freeze, though.