Search Issue Tracker
By Design
Votes
0
Found in
2020.3.42f1
2021.3.14f1
2022.1.23f1
2022.2.0b16
2023.1.0a19
Issue ID
UUM-19472
Regression
No
Scene Template doesn't create a new Scene when the used Scene Template only contains the Main Camera and Light
Reproduction steps:
# Open the user’s attached project: “SceneTemplateTest”
# Open File → New Scene window
# Select “ThisTemplateDoesntReferenceLighting” as the used template
# Press the “Create” button
# Select the save location for the scene in the prompt window
Expected result: A new scene named “ThisTemplateDoesntReferenceLighting” is created and opened
Actual result: The prompt window for the location is not opened and a scene is not created
Reproducible with: 2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0b16, 2023.1.0a19
Reproducible on: macOS 13.0
Note: The scene is created when the “Load Additively” checkbox is checked
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
1- Prior to version 22.1 each time you would try to instantiate a template wihout cloneable dependencies we would instantiate the scene completely in memory without forcing the user to save the scene on disk. The rationale: this is how the old new scene dowkrlofw would work. And often times user want to be able to create a new scene just to play with it and do not want to polute their project with it.
2- Since 22.1 ALL scene template instantiation even those with cloneable dependencies are done "in memory": we do not force the user to save the scene on disk from the get go. It makes it easier to "fiddle" with scene. When the user actually save the scene using Ctrl + S this is where we save the scene and all cloneable dependencies on disk.