Search Issue Tracker
Fixed in 2018.2.17f1
Votes
1
Found in
2017.1.0f3
Issue ID
946565
Regression
No
PlayMode Test Runner remains in the Play mode if InitTestScene is unloaded using SceneManager.UnloadSceneAsync
Reproduction steps:
1. Open the attached project "PlayModeTestFreeze.zip";
2. Open the Test Runner window (Window -> Test Runner);
3. Select the Play Mode tab in the Test Runner window;
4. Expand "PlayModeTestFreeze", "Assembly-CSharp.dll", and "UnloadSceneFreeze" so that the "Freeze" test is visible;
5. Run the "Freeze" test by double-clicking on it;
Expected results: After the scene unloading, the play mode should be ended.
Actual: The test session does not end and Unity remains in play mode.
Reproduced on: 5.6.3p2, 2017.1.1f1, 2017.2.0b9, 2017.3.0a6.
Note: the same behaviour occurs when either SceneManager.UnloadSceneAsync or SceneManager.UnloadScene is used.
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
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- 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
Resolution Note (fix version 2018.2.17f1):
Works fine in 2018.2.17f1