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
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
Add comment