Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
0
Found in
5.6.5p3
Issue ID
1046181
Regression
No
ActiveScene differs between Editor and Build when loading a new scene
Reproduction steps:
1. Open the attached project.
2. Open and play the MainScene.
3. Click 'LoadScene'.
4. Click 'UnloadScene'.
- Notice that all three cubes are created in the main scene and therefore not destroyed.
5. Build and run the project to any platform.
6. Repeat steps 3 and 4.
- Only one cube will be visible in the scene.
Actual behavior:
- Different behavior between Editor and Build.
Expected behavior:
- Similar behavior between Editor and Build.
Reproduced with:
2018.3.0a1, 2018.2.0b7, 2018.1.4f1, 2017.4.5f1, 2017.3.2f1, 2017.3.2f1, 2017.1.4f1, 5.6.6f2, 5.5.6f1
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 (fix version 2022.1):
Fixed in: 2022.1.0a4
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.8f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.27f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.40f1