Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.48f1
2021.3.25f1
2022.2.20f1
2023.1.0b17
2023.2.0a15
2023.3.0a3
Issue ID
UUM-35713
Regression
No
Sub-asset gets corrupted when a SpriteAtlas is stored as sub-asset
Reproduction steps:
1. Open the attached “BugRepro” project
2. Click Test > Generate Test Asset
3. In the Project View, select “/Assets/MyAsset.asset“
4. In the Project View, deselect the asset, by clicking anywhere else in the View
5. Enter the Play Mode
6. Exit the Play Mode
7. Repeat 3rd step
8. Observe the warnings in the Console window
9. Repeat 4th step
10. Enter the Play Mode
11. Observe the errors in the Console window
12. Exit the Play Mode
13. Repeat 3rd step
14. Observe the errors in the Console window
Expected result: Storing a SpriteAtlas as a sub-asset does not result in a corrupted asset
Actual result: Storing a SpriteAtlas as a sub-asset results in a corrupted asset
Reproducible with: 2020.3.48f1, 2021.3.25f1, 2022.2.20f1, 2023.1.0b17, 2023.2.0a15
Reproducible on: Ubuntu 23.04, Windows 10
Note: on 2022.2.20f1, 2023.1.0b17, and 2023.2.0a15 the warnings from the 8th step are not shown
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
- Line Brush blue outline appears at incorrect position when painting start of line in Tile Palette
- [URP] All materials render black when building via batchmode or without rendering Scene/Game view in Editor if Decal renderer Technique is set to "Automatic"
- Player Tags list shows extra blank space behind the scrollbar in the "Player Tags" settings window
- Edit Angular Limits gizmo handles are small and easy to miss-click in the Scene view
- Duplicate Player Tag save fails silently with no error or validation message
Resolution Note:
Please note that by design SpriteAtlas should be used with existing workflow and importer. Adding it as sub-asset to another is unsupported.