Search Issue Tracker
Fixed in 2018.4.2f1
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
1
Found in
2018.3.0a3
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1136349
Regression
Yes
Sprite Atlases are packed by entering Play Mode when Sprite Packer Mode is set to "Enabled for builds"
1. Open the attached 'sprite.zip' project
2. Go to Project tab -> 'sprites' folder and duplicate some sprites (select sprite and press Ctrl + D)
3. Enter Play Mode and observe the popped up window
Expected result: Sprite Atlases are packed just for builds
Actual result: Sprite Atlases are packed by entering the Play Mode
Reproducible: 2018.3.0a5, 2018.3.11f1, 2019.1.0b9, 2019.2.0a10
Not reproducible: 2017.4.0f1, 2017.4.24f1, 2018.3.0a2
Comments (2)
-
Peter77
May 16, 2019 05:20
It's fixed in Unity 2019.3.0a2 according to the changelog:
https://unity3d.com/unity/alpha/2019.3.0a2 -
joaobsneto
Apr 29, 2019 18:23
Was it fixed in 2018?
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2018.4.2f1):
Fixed in: 2019.3.0a1
Backported to: 2018.4.2f1, 2019.1.4f1, 2019.2.0b4