Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
preview.1 - 0.6.0
Issue ID
1229233
Regression
No
Profile Analyzer - Total time for multiselection of frames is displayed in miliseconds when microsecond units are selected
How to reproduce:
1. Create a new Unity project
2. Import the Profile Analyzer package
3. Capture and pull some data from the Unity Profiler
4. Drag a selection over the frame view to select multiple frames
5. Hover the mouse over the selection to see the total time for selected frames
6. In the Filters section change the Units to 'Microseconds'
7. Hover the mouse over the selection again and see the total time
Expected result: total time for selected frames is displayed in microseconds
Actual result: total time for selected frames is displayed in milliseconds
Reproducible with: 2018.4.19f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a4
Could not test with: 2017.4.38f1(package unavailable)
Reproducible with package versions: preview.1 - 0.5.0, preview.1 - 0.6.0
Could not test with package versions: preview.6 - 0.4.0(total time for selected frames is not shown)
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
- Unable to navigate in the Scene when the Readme.cs script of an Asset exists in the project
- Directional Lights impact Sprites they should not impact when the GameObjects are on different Rendering Layers
- Custom Scene view Context Menu does not bypass the ordinary Context Menu shortcut
- Style Sheets cannot be referenced in a Theme Style Sheet file when the folder that contains the Style Sheet has a pound ("#") symbol in it's name
- FontEngine.LoadFontFace fails with Invalid_File_Path when the file path contains Turkish characters
Resolution Note (fix version 0.7.0-preview.1):
Added the time in specified units (milliseconds in this case), before the time rounded to a more readable units in brackets