Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
0
Found in
2018.3.9f1
2019.1.0b7
2019.2.0a7
Issue ID
1136260
Regression
Yes
[Profiler] Profiler chart doesn't scale anymore based on highest visible peak
Steps to reproduce:
1. Create new project
2. Open profiler and enter playmode
- Notice that CPU profiler doesn't scale based on highest visible peak - instead it always shows 0 - 66 ms range
Same issue happens with GPU profiler too.
Reproduced with: 2018.3.9f1, 2019.1.0b7, 2018.2.0a7
Not reproducible: 2018.3.8f1, 2019.1.0b6, 2018.2.0a6
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
Add comment