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
- A memory leak occurs in Play mode when using Direct3D12 Graphics API
- Crash on GfxDeviceD3D12Base::DrawBuffersCommon when rendering 60 real-time lights in the far distance
- Black artifacts appear in the Scene view when moving the mouse with the Scene and Device Simulator windows open
- [OculusXR][GLES] Render pass validation errors on Quest devices when Multi Pass is selected using OpenGLES if HDR or MSAA camera settings differ from URP asset
- Extended component titles exceed the window's display boundaries
Add comment