Search Issue Tracker
Fixed
Fixed in 1.4.4
Votes
0
Found in [Package]
1.4.0
Issue ID
DSTR-1025
Regression
Yes
Editor gets stuck in the temporary playmode tests Scene when playmode tests are ran
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Open the Test Runner Window (Window > General > Test Runner)
4. Run the PlayMode Tests (“Run All” button from the PlayMode tab in the Test Runner Window)
5. Observe the Game View
Expected result: The Editor returns to the previous Scene with a Cube GameObject in the middle
Actual result: “All tests succeeded“ is seen in the Game View without the ability to return to the original Scene
Reproducible with: 2023.3.0a16, 2023.3.0b6
Not reproducible with: 2021.3.35f1, 2022.3.19f1, 2023.2.9f1, 2023.3.0a15
Reproducible on: M1 MacOS 14.2, Windows 11 (User’s platform)
Not reproducible on: No other environment tested
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
- Default value in the Script is not assigned when applying the UI Toolkit ObjectField
- Private field value assignment via Script is not applied when you enter the Play Mode for the first time after the change
- There is an ability to switch to VisionOS module even though the installation of the module has failed
- Shrinking the Search Window makes the bottom elements dissapear
- Shrinking the Search Window flips scroll bar direction
Resolution Note (fix version 1.4.4):
The playmode contoller is now set and cleaned up correctly, ensuring that the scene is displayed correctly after a test run.