Search Issue Tracker
Fixed
Fixed in 2022.3.19f1, 2023.2.8f1, 2023.3.0b5, 7000.0.0a1
Votes
0
Found in
2022.3.15f1
2023.2.3f1
2023.3.0a17
Issue ID
UUM-58154
Regression
No
Tilemap Collider 2D is not updating the Collider shapes when removing Tiles on the Tilemap component
How to reproduce:
1. Open the “Collider2DRepro“ project
2. Open the “Scenes/Regular/Trying New Angles“ scene
3. Enter the Play mode
4. Press the letter ‘K' on the keyboard
5. Press the letter 'A’ on the keyboard
6. Open the “Breakable Blocks“ GameObject in the Inspector
7. Observe the Scene view
Expected result: When the two bottom tiles are set to null (destroyed) they are not detecting collision
Actual result: When the two bottom tiles are set to null (destroyed) they are still detecting collision, and Collider Bounds are still in place
Reproducible with: 2022.3.15f1, 2023.2.3f1, 2023.3.0a17
Could not test with: 2021.3.33f1 (Could not fix the “The type or namespace name 'IntegerField' could not be found“ error message)
Reproducible on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Workaround: Open the “Grid > Breakable Blocks“ GameObject in the Inspector and in the Tilemap Collider 2D Component set Max Tile Change Count to 0
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2023.3.0b5):
Fix for this issue is available on Unity 2023.3.0b5 and above
Resolution Note (fix version 2023.2.8f1):
Fix for this issue is available on Unity 2023.2.8f1 and above
Resolution Note (fix version 2022.3.19f1):
Fix for this issue is available on Unity 2022.3.19f1 and above