Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2021.1
2021.1.0a7
Issue ID
1297228
Regression
No
[UI/UX] "Force stop" and "Cancel" buttons don't disappear after finishing GI bake in the newly created unsaved scene
Steps to repro:
1. Create new project;
2. Open "SampleScene" scene;
3. Select File>New Scene;
4. In the appeared window select "Basic (Built-In)" and click "Create" button;
6. In the newly creted scene press "Generate Lighting" in Ligthing window;
7. Wait until lighting bakes.
Expected result:
After baking "Force stop" and "Cancel" buttons disappear and only "Generate Lighting" button is shown.
OR
"Generate Lighting" button should be grayed out until the user has either dirtied the scene or created the lighting settings asset manually and saved the scene.
Actual result:
"Force stop" and "Cancel" buttons don't disappear after finishing GI bake. See attached video.
Workaround is to either save the newly created scene, add any gameobject and rebake the GI (with saving the scene) or create the new Lighting Settings Asset file, save the scene and rebake.
Notes:
- Reproducible in Versions 2021.1.0a7, 2020.2.0b13, 2020.1.17f1, 2019.4.16f1;
- Not reproducible in Version 2018.4.30f1, because in that Version auto-baking mode was always on; Also in that version the popup window for saving the scene appears after disabling auto and manually rebaking, making the baking to finish properly.
- The issue got introduced with disabling the auto-baking mode for the new scene;
- Although the issue has a little impact on users, as it only happens when baking the empty scene, this might confuse some of the users makign them wondering why the baking didn't properly finish.
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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
Resolution Note (2021.1.X):
This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.