Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Metal Editor view repaint causes geometry explosion randomly
Metal Editor has multiple views and each of them has a separate queue for GPU command buffer submission.
Last time I tested the behavior years ago, it seems the submitted command buffers were still finishing in submission order despite multiple queues,
but seems something might have changed recently.
Metal uses the command buffer completion handler/framecounter tracking to figure out latest safe resource, so if submissions are finished out of order in some situations, it can cause one-off geometry explosions to happen when repainting the views, typically outside of playmode, but known to cause occasional instability issues with SRP graphics playmode tests.
During original Metal Editor implementation era (macOS 10.11-10.12), the drivers were super picky on how to implement updates for multiple Metal layers, resulting into kernel panics otherwise. I quickly tested the possibility of using a single command queue on current OS, but seeing overall worse performance than with multiple queues
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- New input system Windows native backend gets stuck in infinite loop when USB HID device with 0xFFFF usage max is plugged in
- Superluminal fails to resolve symbols after mono upgrade
- Windows Standalone player builds with Mono scripting backend don't run on fresh windows installs
- RootEditor predicate for GameObjects disables Drag and Drop in the Scene View
- Slider OnValueChanged event is not called when changing value from the Inspector