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
- The Editor becomes unresponsive and memory allocation errors are spammed in the Console when Generating Lightning
- Crash on BatchApplyPropertiesFromSourceAssetDB when opening a specific project
- Scene view Camera cannot be moved with WASD/QE keys when the Right Mouse Button is held down and the Mouse is not moved
- Crash when calling default interface method from virtual method with same name
- [Android] Unity does not include the ".aab" extension for an AppBundle when it is built via script with the buildPlayerOptions.locationPathName = "AppName.apk" and EditorUserBuildSettings.buildAppBundle = true
Add comment