Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.37f1
2022.3.26f1
2023.2.19f1
6000.0.0b16
Issue ID
UUM-71288
Regression
No
A new Additive Scene cannot be created when an empty Untitled Scene is not dirty
How to reproduce:
1. Delete every Scene from the “Test_UntitledScene.zip“ project (to open the “Untitled“ Scene on launch)(if there are any)
2. Open the “Test_UntitledScene.zip“ project
3. Select the “Do Something That Is Impossible When There Is An Untitled Non Saved Scene“ submenu in the “Test” menu (to add a new scene additively)
4. Observe the Console window
Expected results: Scene is created and no Console errors appear
Actual results: Scene is not created and an “InvalidOperationException“ error appears
Reproducible in: 2021.3.37f1, 2022.3.26f1, 2023.2.19f1, 6000.0.0b16
Reproduced on: Windows 11 Pro (23H2), macOS 14.4.1 (by the reporter)
Not reproduced on: No other environment tested
Note: The method “EditorSceneManager.EnsureUntitledSceneHasBeenSaved“ does not account for the “Dirty“ state not being set, resulting in the Scene being considered “unsaved”
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
- [Build Profile] [VisionOS/iOS/tvOS] - Build Player Library button is getting displayed depending on the selected build target
- EnsureRunningOnMainThread error in TessellationJob.ApplyInset
- MultiColumnListView causes a memory leak when repeatedly shown and hidden
- Position Node with Object Space has a wrong value when there are multiple active GameObjects with the same shader
- [URP][RG] Fullscreen blit is not working when Render Graph is enabled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.