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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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