Search Issue Tracker
Active
Votes
0
Found in
2021.3.45f1
2022.3.51f1
6000.0.24f1
6000.1.0a1
Issue ID
UUM-85334
Regression
No
PlayModeStateChange.ExitingPlayMode is not logged when Play Mode is exited due to recompilation
Reproduction steps:
1. Open the attached “BugRepro” project
2. In the Preferences window General tab (Edit > Preferences… > General), set Script Changes While Playing to “Stop Playing And Recompile”
3. In the Console window, expand the Clear dropdown menu and disable “Clear on Recompile”
4. Enter Play Mode
5. Open “Assets/PlayModeUtils” script using a code editor
6. In the code editor, delete line 11
7. Save the changes to the script to cause a recompilation
8. Observe the Console window
Expected result: “1) Exit Play Mode” and “2) Enter Edit Mode” messages are logged
Actual result: Only the “2) Enter Edit Mode” message is logged
Reproducible with: 2021.3.45f1, 2022.3.51f1, 6000.0.24f1, 6000.1.0a1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Errors are thrown when clicking "Refresh Virtual Offset Debug"
- 2D Renderer Breaks When Animating Material Property with MaterialPropertyBlock
- PlayModeStateChange.ExitingPlayMode is not logged when Play Mode is exited due to recompilation
- Crash on `anonymous namespace'::PrepareTreesAndWriteWindParamsJobData::Execute when entering Play Mode on a specific project
- Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
Add comment