Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.2.0a1
2018.2.16f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1103878
Regression
No
Collisions miscalculated when Tilemap Collider is used
Steps to reproduce:
1. Open Project "TilemapCollider2D Bug"
2. Drag the GameObject with Cirle Collider 2D outside the area with red Tiles present
3. Enter the Play Mode
4. In Scene View drag the GameObject on the red area with various speeds and from different sides.
Expected Results: Collider is triggered immediately on Collision and Collision is only calculated if there is a Collider on a Tile
Actual Results: Collider is not always triggered on Collision or Collision is calculated with no Collider Present
Reproducible with: 2017.4.17f1, 2018.3.1f1, 2019.1.0a13, 2019.2.0a1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
There's currently a limitation of 64 points (32 manifolds each with 2 points) for our contact point reporting. That limit will be removed.