Search Issue Tracker
Fixed in 5.0.0-preview.1
Votes
0
Found in [Package]
0.4.0-preview.4
Issue ID
1156539
Regression
No
Profile Analyzer - top marker bar doesn't match calls list
Using Profile Analyzer v 0.4.0. The details regarding a marker in the "Top 10 markers window" don't match what I see in the calls list, the timings are different.
0.5.0 has improved UI to make it clearer what differences appear between the marker table and the top 10.
The top 10 is for the frame with median of overall frame duration.
Each marker in the table shows the median value of the frame where that specific marker is at its median value (which can be a different frame to the top 10 section).
Tooltips now make this clearer.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- OnTriggerExit2D when disabling a GameObject
- [DirectX12] FrameTimingManager does not return useful data
- [GPU PLM] High resolution lightmap bake keeps on restarting when Progressive Updates flag is enabled
- Use legacy light probe sample counts is enabled for newly created projects
- Prefab is marked as unsaved if LayoutGroup components are attached to it when saving the Prefab manually
Resolution Note (fix version 5.0.0-preview.1):
This is working as expected, but the feedback on the UI is very useful and indicates it could be improved.
The Top 10 Marker bar shows the marker value on the median frame. This frame is the one with the median total frame time.
The comparison graph shows the median of all the samples over all the frames.
So these two may not match.
If you switch to the single view there are two columns.
'Median' is the median value of the marker over all frames (same as the comparison view).
'At Median Frame' is the value of the marker on the 'median frame' with the median overall frame time. (same as seen in the top 10 view)
If you click on the frame time graphs and choose "Select Median Frame" for both data sets, then the values will all match.