Search Issue Tracker
In Progress
Fixed in 6.0.1
Fix In Review for 5.0.2
Votes
0
Found in [Package]
5.0.1
Issue ID
DANB-1067
Regression
No
AutoTile does not respect "None" Collider Type when placing Tiles automatically
Reproduction steps:
1. Open the attached “IN-107834.zip” project
2. Open the “SampleScene”
3. Open the “Tile Palette” Window (Window > 2D > Tile Palette)
4. Make sure the Active Palette is set as “autotile test”
5. Select the Brush (or press B on the keyboard) and the Tile
6. In the Scene view, draw with a Brush at least a 3x3 area
7. Select the drawn Tilemap and observe the Colliders
Expected result: The centre green Tile does not have any Colliders
Actual result: The centre green Tile has a TilemapCollider
Reproducible with: 4.2.1, 5.0.1 (6000.1.12f1, 6000.2.0b10, 6000.3.0a3)
Couldn’t test with: 6000.0.54f1 (AutoTile functionality not available)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- The green tile - “legacy_atlas_6603.asset”, has its Collider Type set to None
- Placing the tiles manually from the Tileset, makes the colliders react as expected and does not reproduce the issue
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note (fix version 6.0.1):
Fix for this issue is available on 2D Tilemap Extras 6.0.1 and above