Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a6
Issue ID
1168943
Regression
Yes
[FrameDebugger] Most of the draw calls in its slider are jammed into one corner
To reproduce:
1) Create a new project
2) (Optional, but betters the visibility) Create a couple of cubes to increase amount of draw calls
3) Open Frame Debugger and enable
4) Scroll through the slider
Expected: Each draw call is separated equally through the slider
Actual: About 75-90% of draw calls (depending of their amount) are in the last 10% bit of slider
Reproduced in 2019.3.0a6, 2019.3.0a9
Not reproduced in 2019.3.0a5, 2019.2.0b9
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
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0a11