Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
2
Found in
2018.2.6f1
Issue ID
1080435
Regression
No
Profiler data does not match the numeric data in its Hierarchy
To reproduce:
1. Open the user's attached project
2. Open the Scene "benchmark" and play it
3. Open the Entity Debugger and disable every item that has "AI" in the name except "AISystemPure"
4. Open the Profiler and select the "AISystemPure"
5. Compare the "Time ms" in the Hierarchy and in the graph
Expected result: The Time is the same both in the Graph and in the Hierarchy
Actual result: The Time differs heavily in the Graph from the Hierarchy
Reproduced with: 2018.2.8f1, 2018.3.0b1
Entities package required.
Note: Enabling Others will provide you with the missing timings. As Semaphore waiting /signaling is part of the Others category. Furthermore the timings can differ slightly from the hierarchy due to multiple reasons such as floating point errors, the overhead for the threads context switching.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Add comment