Search Issue Tracker
By Design
Votes
0
Found in
2020.3
2020.3.7f1
2021.1
2021.2
Issue ID
1335647
Regression
No
Environment changes are not saved into the Scene Template when lighting is not generated
How to reproduce:
1. Create a new project
2. Open the Environment Lighting settings (Window->Rendering->Lighting Settings->Environment)
3. Change Realtime Shadow Color (or any other setting)
4. Save the Scene and Save it as a Template (File->Save as Scene Template...)
5. Create a new Scene using the newly created Scene Template
Expected results: Environment settings are saved to the Scene Template
Actual results: Environment settings are not saved to the Scene Template
Reproducible with: 2020.3.9f1, 2021.1.8f1, 2021.2.0a17
Could not test with: 2019.4.27f1 and earlier because Scene Template creation was not yet available
Note:
- Generating Lighting will save the Environment changes to the Scene Template
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note (2022.1.X):
Scene Template can only track dependencies of a scene if those are available through the AssetDatabase. In the current workflow, until the user presses Generate Lighting the LigthingData doesn't exist.
If the user Generates the lighting those dependencies will be available.