Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.33f1
6000.0.6f1
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-73661
Regression
No
The sprite draw calls are batched in the Player when the Sprite Atlas is uploaded from an AssetBundle and the Sprite Atlas Mode is set to Disabled
How to reproduce:
1. Open the “Atlas_AssetBundle_Test“ project
2. Open the “AssetBundle1“ scene
3. Set “Edit > Project Settings > Editor > Sprite Atlas > Mode“ to "Sprite Atlas v2 - Enabled"
4. Build and Run
5. Close the Player
6. Set “Edit > Project Settings > Editor > Sprite Atlas > Mode“ to "Disabled"
7. Build and Run
8. Connect the Frame Debugger to the Player
9. Observe the “RenderLoop.Draw“
Expected result: The sprite draw calls are not batched
Actual result: The sprite draw calls are batched
Reproducible with: 2022.3.33f1, 6000.0.6f1
Could not test with: 2021.3.39f1 (Could not resolve the sprites not showing in the Player)
Reproducible on: macOS 14.5 (Intel), Windows 11 (User’s)
Not reproducible on: No other environments tested
Workaround: After performing a Clean Build the sprite draw calls work as expected, until building with “Edit > Project Settings > Editor > Sprite Atlas > Mode“ set to "Sprite Atlas v2 - Enabled" again
Note: Not reproducible in the Editor
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 JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note:
There are no fixes planned for this Bug