Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.3.X
Votes
0
Found in
2021.2.11f1
Issue ID
1402404
Regression
No
[2D][Sprite] Mismatch in Secondary Texture order for sprites in scene causes draw batching to break
[2D][Sprite] Mismatch in Secondary Texture order for sprites in scene causes draw batching to break
Repro steps:
- Open SampleScene, enter playmode, observe Frame Debug shows 2-3 draw calls with Axe sprite on a different call than the rest (meaning the batch is broken)
- Disable Axe gameobject or switch the Secondary Texture order of Axe sprite in Sprite Editor
- Enter playmode again and observe Frame Debug shows only 1 draw call and all sprites are batched
Expected result: Batch should not be broken when sprites in scene have different Secondary Texture order
Actual result: Batch is broken when sprites in scene have different Secondary Texture order
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
- Crash on __pthread_kill when initializing Vuplex WebView while entering the Play Mode
- Crash on FindSurface when adding a custom Renderer Feature to a 2D Renderer Data Asset
- [Android] [Vulkan] [UI Toolkit] Application crashes when the device is rotated when it has UI Toolkit TextField on Vulkan devices
- Crash on DualThreadAllocator<DynamicHeapAllocator>::TryDeallocate when opening a specific project
- Crash on memset_repstos when pressing a UI button while in Play Mode
Resolution Note (fix version 2022.2):
Fix for this issue is available on Unity 2022.2.0a12 and above
Resolution Note (fix version 2021.3):
Fix for this issue is available on Unity 2021.3.4f1 and above