Search Issue Tracker
Fixed
Fixed in 2022.3.22f1, 2023.2.16f1, 6000.0.0b11
Votes
0
Found in
2022.3.19f1
2023.2.10f1
2023.3.0b7
6000.0.0b11
Issue ID
UUM-63813
Regression
Yes
Invalid sprite atlas asset encountered warning is shown when editing a texture Asset
Reproduction steps:
1. Open the attached “BugRepro” project
2. In the Project window, select the “Assets/sprites/add40” texture Asset
3. In the Inspector window, make any changes to the Asset (e.g. change the Pixel Per Unit property to 120) and press “Apply”
4. Observe the Console window
Expected result: No warnings are shown in the Console
Actual result: “Invalid sprite atlas asset encountered when matching atlas for sprite add40. Please repack all your sprite atlases” warning is shown
Reproducible with: 2022.2.0a16, 2022.3.19f1, 2023.2.10f1, 2023.3.0b7
Not reproducible with: 2021.3.35f1, 2022.2.0a15
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 6000.0.0b11):
Fixed case where invalid sprite atlas asset encountered warning is shown when editing a texture Asset. Fix is available on Unity 6000.0.0b11 and above
Resolution Note (fix version 2023.2.16f1):
Fix for this issue is available on Unity 2023.2.16f1 and above
Resolution Note (fix version 2022.3.22f1):
Fix for this issue is available on Unity 2022.3.22f1 and above