Search Issue Tracker
Active
Under Consideration for 2.2.X
Votes
0
Found in [Package]
2.2.2
Issue ID
ADDR-3811
Regression
Yes
IndexOutOfRangeException occurs when assigning a subasset from a Sprite Atlas to an AssetReferenceAtlasedSprite field if the sprite is in a folder
How to reproduce:
1. Open the attached “IN-87971” project
2. Open the “SampleScene” Scene
3. Create an empty GameObject in the Scene
4. Add the “TestScript” Script from the Assets folder to the GameObject components
5. In the “Defined Atlased Sprite” property input field select the SpriteAtlas in the Assets folder
6. Select any sprite from the Sprite Atlas in the Subasset input field
7. Observe the Console window
Expected result: No errors occur
Actual result: IndexOutOfRangeExcpetion error occurs
Reproducible with: 2.0.3 (2023.3.0a2), 2.2.2 (6000.0.26f1, 6000.1.0a3)
Not reproducible with: 1.22.3 (2021.3.45f1, 2022.3.0f1, 2022.3.52f1)
Reproduced on: Windows 11, macOS (User system)
Not reproduced on: No other environment tested
Note: After doing the reproduction steps, selecting the affected GameObject the property “Defined Atlased Sprite” input field becomes blank, can’t select a Sprite Atlas or a Subasset anymore and more IndexOutOfRangeException errors appear in the Console
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
Add comment