Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
Issue ID
1267126
Regression
Yes
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.
Latest issues
- "Upload Symbols Failed" is thrown when Archive validation is being done in Xcode
- Active quality level set on a new Universal 2D project is not the default quality level when creating a new project
- Inspector Open button does nothing when navigating to a different folder with a locked asset
- Pre-generated XML serializers fail to deserialize types that use polymorphism when the Player is built with the IL2CPP scripting backend
- Editor crashes with error "Failed to present D3D11 swapchain due to device reset/removed" and Player freezes when rendering a particle system while using modified URP package on DX11
Add comment