Search Issue Tracker
Won't Fix
Won't Fix in 1.21.X
Votes
0
Found in [Package]
1.21.19
Issue ID
ADDR-3599
Regression
Yes
The addressable sprite asset is duplicated in multiple asset bundles when the "Include in Build" checkbox is toggled off
Reproduction steps:
1. Open the attached “TilemapAddr” project
2. Open “Assets/Addresable/SpriteAtlas.spriteatlasv2” and make sure that "Include in Build" checkbox is toggled off in the Inspector
3. Open the Addressable Groups window from Window > Asset Management > Addressables > Groups
4. Build the addressables from Build > New Build > Default Build Script
5. Open the Addressable Report window from Window > Asset Management > Addressables > Addressables Report
6. Observe the last Addressables Report
Expected Result: No warnings are shown in Addressables Report and Sprite1.png is not duplicated in multiple asset bundles
Actual result: The warning message “1 Duplicate Assets were detected in the build.“ appears and Sprite1.png is copied in multiple asset bundles
Reproducible with: 1.19.19 (2022.1.0a13), 1.21.19 (2022.3.16f1, 2023.2.4f1), 2.0.6 (2023.2.4f1, 2023.3.0a19)
Not reproducible with: 1.19.19 (2022.1.0a12), 1.21.19 (2021.3.33f1)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.21.X):
This is working as intended. There are steps that can be taken to eliminate the duplicated data from the sprite and its atlas. If there is a need to include the entire atlas in the build and the "Include in Build" option is enabled, the atlas itself must be added to an addressables group in order to be included but not duplicated among all of the groups that have objects that reference it.
If the atlas does not have "Include in Build" enabled, each sprite that is included in the build will create a copy of its pixels from the atlas and include that data. If the same sprite ends up in multiple bundles, then the pixel data will be duplicated. To fix this, mark the sprites as addressables and put them into a separate group.