Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
Issue ID
1092442
Regression
Yes
Setting custom bake inputs from the Lightmapping.started callback throws an error on the first bake
Setting custom bake inputs has this check
```if (!GetProgressiveBakingBackendEnabled())
ErrorString("Custom bake inputs will not be processed. Please make sure to enable Baked Global Illumination and select Progressive as the Lightmapper before generating lighting.")```
and that spits out this error if the custom bake inputs are set in the `Lightmapping.started` callback on the first bake after the Editor has been started.
The problem is that when you start the Editor the backend is invalid until the Progressive Lightmapper clears itself (which takes a few Update ticks).
It looks to me that this check should look at `GetLightmapEditorSettings().GetBakeBackend()` (what the user has set) to do the validation and not at `GISceneManager::Get()->GetBakeBackend()` (which will be invalid for the first few ticks and generally is a bit weird, as the pipeline clearing itself could query the backend and is not really expecting to get invalid as a result).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PropertyDrawer gets disposed while still being active when adding a secondary component
- Realtime GI behaves differently when using Unlit (Amplify) and Lit (Shader Graph) shaders in URP
- API Updater strips Unity-owned Custom Attribute references within precompiled DLLs
- [iOS] ListView is flickering when scrolling over the end
- The Aspect Ratio Fitter Component on a Prefab displays a parent-related warning despite the Prefab's inability to have parents when "Envelope Parent" or "Fit In Parent" modes are used
Add comment