Search Issue Tracker
Fixed in 1.0.3
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1244416
Regression
No
[Profile Analyzer] Timings in Marker Summary all show 0.00ms when marker frame timing is below 0.01ms
How to reproduce:
1. Open attached "ProfileAnalyzer" project
2. Open Profile Analyzer (Window->Analysis->Profile Analyzer)
3. Load in user's attached "capture.pdata" data
4. Right-click on the frame view and press "Order by Frame Duration"
5. Select the last 9 frames
6. Enter 'FireAn' into the Name Filter in the Filter section of Profile Analyzer
7. Select "Animators.FireAnimationEventsAndBehaviours" marker in the Marker Details list
Expected result: In the Marker Summary numbers represent what the graphs show
Actual result: All of the numbers in the Marker Summary show 0.00 even if bars show that they have different values
Reproducible with: 0.6.0-preview.1 (2018.4.23f1, 2019.3.14f1, 2020.1.0b9, 2020.2.0a11)
Could not test with: 0.4.0-preview.3, 0.4.0-preview.6 because the data files are in a different version (Incorrect file version), 2017.4.40f1 unable to install Profile Analyzer
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.0.3):
Fixed in Profile Analyzer 1.0.3
Improved time precision is in the Tooltip, hover on the timing to get the precise timing