Search Issue Tracker
Fixed
Fixed in 2021.3.37f1, 2022.3.22f1, 2023.2.14f1, 6000.0.0b11
Votes
0
Found in
2021.3.35f1
2022.3.19f1
2023.2.9f1
2023.3.0b6
6000.0.0b11
Issue ID
UUM-62818
Regression
No
"Automatic" Slice Type produces different results and "ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection." error is thrown when it was previously undone
How to reproduce:
1. Open the “Dungeon“ project
2. In the Project window select the “Assets/DummySprites/Characters/Player/Death.png” Asset
3. In the Inspector window select “Open Sprite Editor”
4. Execute a Slice with an “Automatic” Type
5. Observe the slices
6. Undo this action by pressing Ctrl + “Z” key combination
7. Repeat steps 4-5
Expected result: Slices are distributed evenly throughout all the sprites of the character
Actual result: Only 5 slices are created and the “ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection." error is thrown
Reproduced with: 2021.3.35f1, 2022.3.19f1, 2023.2.9f1, 2023.3.0b6
Reproduced on: Windows 10 (by reporter), Windows 11
Not reproduced on: No other environment tested
Notes:
1. Could not reproduce in a new project using the same Asset
2. Full error is provided in the internal comments
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2023.2.14f1):
Fix for this issue is available on Unity 2023.2.14f1 and above
Resolution Note (fix version 2022.3.22f1):
Fix for this issue will be available on Unity 2022.3.22f1 and above
Resolution Note (fix version 2021.3.37f1):
Fix for this issue will be available on Unity 2021.3.37f1 and above