Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
7
Found in
2018.3.6f1
2018.3.8f1
2019.1.0b3
2019.2.0a4
Issue ID
1136275
Regression
Yes
Frame Debugger breaks Editor windows when cycling through drawcalls with Dynamic Batching enabled
How to reproduce:
1. Open user-submitted project (FrameDebuggerGlitch) and 'SampleScene' scene
2. Check that the 'Dynamic Batching' option in Project Settings > Player is enabled
3. Open Window > Analysis > Frame Debugger and enable it
4. Cycle through the drawcalls
Expected result: no graphical glitches occur
Actual result: Editor windows start visually breaking
Reproducible with: 2018.3.6f1, 2018.3.9f1, 2019.1.0b3, 2019.1.0b7, 2019.2.0a4, 2019.2.0a8
Not reproducible with: 2017.4.23f1, 2018.3.5f1, 2019.1.0b2, 2019.2.0a3
Notes:
Issue does not reproduce when there is no 'Draw Dynamic' drawcall present
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment