Search Issue Tracker
Fixed
Fixed in 2021.3.38f1, 2022.3.21f1, 2023.2.10f1, 2023.3.0b5
Votes
0
Found in
2021.3.32f1
2022.3.12f1
2023.2.0b16
2023.3.0a12
Issue ID
UUM-55614
Regression
No
TMP Sprite Asset changes are not detected when a new sprite is added
Reproduction steps:
1. Open the attached project "SPRITENOSAVE"
2. Select “Assets/TX_UI_GamepadControls.png“
3. Open the Sprite Editor window (Window > 2D > Sprite Editor)
4. Select a part of the image and click the “Apply” button
5. Select “SPRITEASSET“
6. Go to the last page of the Sprite Character Table
7. Click on the “Update Sprite Asset” button
8. Observe that the Sprite gets added
9. Save (Ctrl + S)
Expected result: “SPRITEASSET“ is saved and the Inspector window gets refreshed
Actual result: “SPRITEASSET“ is not recognized as changed and is not saved
Reproducible with: 3.0.6 (2021.3.31f1, 2022.3.12f1, 2023.1.19f1), 3.2.0-pre.4 (2021.3.31f1, 2022.3.12f1, 2023.1.19f1, 2023.2.0b16, 2023.3.0a11)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Note: “SPRITEASSET“ can be saved when any other field is edited
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
Add comment