Search Issue Tracker
In Progress
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 5.0.1):
Fix for this issue is available on 2D Tilemap Extras package 5.0.1 and above