Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0f3
Issue ID
898172
Regression
No
EditorApplication.playmodeStateChanged is called when scrolling through the Profiler Window
1. Open the Scene scene and run it.
2. Open the Profiler Window, enable it and Pause the game. Notice that console has a log of playmodeStateChanged event firing.
3. Now scroll through frames in the Profiler Window. Notice how console is spammed with the same messages from the playmodeStateChanged handler in Script.cs.
This behavior doesn't let the user to differentiate between real "pause" event and fake ones making editor scripting harder.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment