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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 2018.2.17f1):
Works fine in 2018.2.17f1