Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.5.0p1
Issue ID
860750
Regression
Yes
Unloading Scene destroys runtime created objects, when the same scene has been loaded multiple times additively
To reproduce:
1. Open project that i attached "unloadScene.zip"
2. Open "TestCase1" scene, and play it.
3. Look at the Hierarchy. "TestObject" got destroyed, only "SCENE obj" is left.
4. Stop the "Play mode".
5. In "TestCase1" select "Script" object in Hierarchy. In "Test Script" component, "Scene 2 Name" change from "EmptyScene1" to "EmptyScene2".
6. Play scene again.
7. In hierarchy "TestObject" is not destroyed.
Actual result: When multiple copies of the same scene are loaded using "LoadSceneAsync" and one of them is unloaded using "UnloadSceneAsync" or "UnloadScene", it also destroys runtime created objects.
Expected result: When "UnloadSceneAsync", or "UnloadScene" is called, it only destroys objects which were associated with that scene.
//Reproduces when game object is created with "new GameObject", or with "Instantiate".
Reproduced with: 5.5.0f3, 5.6.0b1
Not reproduced with: 5.4.2f1 //In 5.4 there was only "UnloadScene" but not "UnloadSceneAsync", although the description is the same.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment