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
- Crash when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
- Artifacts appear on GameObjects when using the WebGL Player on Silicon macOS
- Only the icon of the disabled child GameObject is faded when a parent GameObject is a Prefab
Add comment