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
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
Add comment