Search Issue Tracker
Fixed
Votes
0
Found in
5.3.1p3
Issue ID
763194
Regression
Yes
EventSystem Update does not ignore disabled objects
Reproduction steps:
1) Open users attached project and proceed to scene "TestCanvas".
2) Open profiler window and head into playmode.
Expected result: Cpu usage should stay way bellow 1 ms.
Actual result: Cpu usage depending on profiling from 5 to 30 ms.
IMPORTANT (Images attached below)
Note0: Without deep profiling Cpu usage hovers around 5ms.
Note1: When deep profiling is enabled whilst still in playmode this usage magically vanishes.
Note2: When deep profiling is enabled before going into playmode Cpu usage skyrockets from 5 to 30ms.
Note3: This calls in last screenshot ignore the fact that objects are disabled in hierarchy.
Reproduced with: 5.4.0b3 5.3.2p1 5.2.4f1
Does not reproduce: 5.1.4f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Rigidbody2D.Slide API does not have the needed configuration when creating a 2D Top-Down character controller
- Opening reference for "Playables"component redirects to a missing page
- Sprite Renderer image is changed when switching Mask Interaction and changing Sprite to a shared Sprite
- An unsigned integer is not compared with an integer correctly in player when using IL2CPP backend
- Graphical artifacts are being rendered in Scenes that are loaded during run-time when GPU Resident Drawer is turned on
Add comment