Search Issue Tracker
Duplicate
Votes
0
Found in
2019.4
2019.4.0f1
2020.2
Issue ID
1262789
Regression
No
Collision geometry is not applied correctly to a Tilemap when Composite Collider's 2D "Geometry Type" is set to Polygons
How to reproduce:
1. Open the user's attached "TilemapCollisionBug.zip" project
2. Open the "SampleScene" Scene (Assets folder)
3. Make sure the Scene view is visible
4. Expand the "Grid" GameObject in the Hierarchy window
5. Select the "Tilemap (2)" GameObject in the Hierarchy window
6. Observe the Scene view
Expected result: Correct collision geometry is applied to the Tilemap, no tiles are left without a collider and there are no holes in the collider
Actual result: Two colliders appear on the Tilemap, as the Tilemap gets wider the collider gets more inconsistent leaving the lower part of the Tilemap without a collider and
eventually leaving a hole in the center of the Tilemap
Reproducible with: 2019.4.5f1, 2020.1.0b16, 2020.2.0a18
Could not test with: 2018.4.25f1 (When downgraded, it can be seen that the geometry collision is applied correctly, but after unchecking "Used By Composite" and then checking it again, no geometry collision is applied at all)
Notes:
- The issue is not reproducible if the Composite Collider's 2D "Geometry Type" property is set to Outlines
- The issue is not reproducible if the Tilemap Collider's 2D "Used By Composite" property is unchecked
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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
This is a duplicate of issue #1274172