Search Issue Tracker
Fixed
Fixed in 5.0.1
Votes
0
Found in [Package]
4.3.0
Issue ID
DANB-1001
Regression
No
“ArgumentOutOfRangeException” error thrown when changing “Used Textures” to “0” in Inspector window for Auto Tile
Steps to reproduce:
1. Create new Unity project
2. In Project window create Auto Tile (Right-click > Create > 2D > Tiles > Auto Tile)
3. In Inspector window > User Textures numeric field write “100”
4. In same numeric field change “100” to “0”
5. Press Enter
6. Observe the Console window
Actual results: Error - ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index - is thrown in the Console window
Expected results: No errors
Reproducible with versions: 6000.1.4f1, 6000.2.0b3
Can’t test with versions: 6000.0.49f1 (no Auto Tile available)
Tested on (OS): MacBook Pro, 2021, Sequoia 15.5 (M1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 5.0.1):
Fix for this issue is available on 2D Tilemap Extras package 5.0.1 and above