Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0a5
2018.1.1f1
Issue ID
1042624
Regression
Yes
Original sprites are packaged into the build along with Sprite Atlases even when not included as a dependency anywhere
When using Sprite Atlases the original files are included in the build along with the sprite sheet in all cases, even when there are no references to the sprites in prefabs or the scene.
To reproduce:
1. Download attached project "spriteatlas-repro.zip" and open in Unity
2. Open "SampleScene" scene
3. Build project to any target platform
4. Press Window -> Show Build Report
5. Observe that original sprites are packaged into the build along with Sprite Atlases - sprite sheet along with the 3 icon PNG images
Notes:
- This issue appears on both Windows and OSX
- This issue appears on any target platform
Reproduced on Unity 2017.1.0a5, 2017.1.4f1, 2017.2.3p1, 2017.3.2f1, 2017.4.4f1, 2018.1.2f1, 2018.2.0b6 and 2018.3.0a1
Not reproduced on Unity 5.6.5p4 and 2017.1.0a4
Regression on Unity 2017.1.0a5
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
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
Resolution Note:
Sprite Atlases only manage references to the original sprites and don't keep deep copies of the sprite in the object. If you're building with a Sprite Atlas it needs those sprites packaged with it.