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
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
- FrameTimingManager.GetLatestTimings adds background time to the next focused frame when the Player is unfocused
- PropertyDrawer gets disposed while still being active when adding a secondary component
- Realtime GI behaves differently when using Unlit (Amplify) and Lit (Shader Graph) shaders in URP
- API Updater strips Unity-owned Custom Attribute references within precompiled DLLs
Add comment