Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.5f1
2019.1.0a1
2019.2.0a1
Issue ID
1135638
Regression
No
SpiteAtlas does not change when its associated "Object for Packing" texture is modified by a custom AssetPostprocessor script
How to reproduce:
1. Open the attached project "case_1135638-SpriteAtlasUpdateBug_1" and the scene "SampleScene"
2. Create a Sprite Atlas asset in the Project Window
3. Attach "MyTexture" to the "Objects for Packing" list of the created Sprite Atlas' in the Inspector
4. Click the "Pack Preview" button
5. Right-click "MyTexture" in the Project Window and select "Reimport" from the context menu
6. Click the "Pack Preview" button again in the Sprite Atlas' inspector
7. Observe the Sprite Atlas' preview image in the Inspector
8. Enter Play Mode and observe the sprite texture drawn in Game View
Expected result: the "Pack Preview" button updates the Sprite Atlas with the reimported texture. The texture used by the Sprite Renderer in the scene does not change when in Play Mode
Actual result: the Sprite Atlas is not updated after reimporting "MyTexture" or pressing "Pack Preview". The Sprite Renderer in the scene uses the version of MyTexture before the reimport when in Play Mode
Reproducible with: 2017.4.23f1, 2018.3.9f1, 2019.1.0b7, 2019.2.0a8
Note: when reimporting "MyTexture" it is changed by a custom AssetPostprocessor but the applied changes are not seen in the SpriteAtlas as mentioned
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
Add comment