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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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