Search Issue Tracker
Duplicate
Duplicate in 2022.2.X
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
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
Resolution Note (2022.2.X):
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