Search Issue Tracker
By Design
Votes
1
Found in
2017.4
2018.4
2019.2
2019.3
2019.3.0b3
2020.1
Issue ID
1185856
Regression
No
SaveScene is triggered on starting play mode even if the scene is not dirtied
To reproduce:
1. Open attached project
2. Open Project Settings, select "Editor" and enable "Enter Play Mode Options (Experimental)" setting. Keep "Reload Domain" and "Reload Scene" unticked.
3. Open Scene "Transform_30000"
4. Play and stop the scene a few times
Actual: SaveScene is called on each start of the play mode, no matter the state of the scene
Expected: On second and further launches, as the scene was not dirtied, it shouldn't spend time on saving a backup again
Reproduced in 2017.4.0f1, 2019.3.0b3, 2020.1.0a9
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:
The scene file is saved along with instanceID remapping information which is needed when reloading the scene when exiting Play mode. Closing it as a bug and moving it to our internal optimization backlog as we want to tacle this optimization as part of a larger refactoring. We will be using this bug reports test setup when picking up the task.