Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1229023
Regression
Yes
[Profile Analyzer] Frame Control value overlaps with drop-down list when Units are set to Microseconds
Reproduction steps:
1. Open attached project "ProfileAnalyze.zip"
2. In Profile Analyzer window, Load "case_1229216-capture.pdata"
3. In Profile Analyzer window, set Units to "Microseconds"
4. Observe Frame Control
Expected result: Time is displayed correctly
Actual result: Time overlaps
Reproducible with: 2019.3.0a3, 2019.3.7f1, 2020.1.0b3, 2020.2.0a4
Not reproducible with: 2018.4.19f1, 2019.3.0a2
Could not test with: 2017.4.38f1 (package version unavailable)
Reproducible with package versions: 0.4.0-preview.3, 0.6.0-preview.1
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):
Frame Control values no longer overlap when units are set to Microseconds