Search Issue Tracker
Duplicate
Votes
1
Found in
2022.2.0b3
Issue ID
UUM-13905
Regression
No
BatchRendererGroup draws have poor thread load balancing in some cases
A user on the forum reports that BatchRendererGroup is taking longer than GameObjects for their workload. The issue seems to be that even though BRG is taking less time per draw, the work is poorly balanced across threads and it takes longer for the thread to finish compared to GameObjects.
Forum post: [https://forum.unity.com/threads/new-batchrenderergroup-api-for-2022-1.1230669/page-3#post-8362923]
Repro project: [https://drive.google.com/drive/folders/1jSzeAgL9FlBtcRWOEDyZefqk5ykTUOVb?usp=sharing]
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [tvOS] Project crashes on startup on Apple TV simulator (both X86_64 and ARM64 architectures)
- Context menus open on a different monitor when there are three monitors used
- Crash on Umbra::QueryExt::queryStaticShadowCasters when opening a specific project
- Crash on GfxDeviceD3D12Base::DrawBuffersCommon when opening a specific project
- Shader variants are recompiled while Building when the Platform is switched and changed back after the first Build
Resolution Note:
This issue is fixed in 2022.2.0b15 and later.
Duplicate of another internal issue: UUM-16378: BatchRendererGroup performs poorly because of locking during draw command processing