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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment