Search Issue Tracker
Fixed
Fixed in 2022.2.0b8, 2023.1.0a6
Unknown (hidden) 2022.3.X
Votes
0
Found in
2022.2.0a18
Issue ID
UUM-6642
Regression
Yes
[Sprite Atlas] Asset Preview window does not update when packing preview after modifying objects for packing or packing settings
Reproduction steps:
1. Open the attached “SpriteAtlasPreview.zip“ project
2. Select the “SpriteAtlas“ asset in the Project window
3. In the Inspector add a new object to the “Objects for Packing” list
4. Click “Pack Preview” and observe the Asset Preview window
5. Remove an old object from the “Objects for Packing” list
6. Click “Pack Preview” and observe the Asset Preview window
Expected result: The Asset Preview window is updated in steps 4 and 6
Actual result: The Asset Preview window is not updated in steps 4 and/or 6
Reproducible with: 2022.2.0a6, 2022.2.0a18, 2023.1.0a1
Not reproducible with: 2020.3.36f1, 2021.3.5f1, 2022.1.7f1, 2022.2.0a5
Reproduced on: Windows 11, macOS Monterey 12.0.1 (Intel)
Workaround: Reimport the Sprite Atlas asset
Note: At first, the issue was only when adding or removing objects for packing. In the current trunk (2023.1.0a1), it's reproducible by changing most packing settings
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
- The Scrollbar becomes unusable when adding Elements to the List
- "One or more data file missing for baking set NewScene Baking Set. Cannot load shared data." error in Player when a specific project is built
- Choosing new HDR Colour using RGB values breaks colour on Intensity Selectors
- Rendering/Decal Layer Mask options are different inside Prefab Mode and outside Prefab Mode when the project is upgraded to Unity 6
- Incorrect Realtime GI Light Probes baking when more than one Light Probe Group is used and "Baked Global Illumination" is enabled
Resolution Note (fix version 2023.1.0a6):
Fix for this issue will be available on Unity 2023.1.0a6 and above
Resolution Note (fix version 2022.2.0b8):
Fix for this issue is available on Unity 2022.2.0b8 and above