Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2020.1.X
Votes
0
Found in
2017.4
2019.3.7f1
2020.2
Issue ID
1234392
Regression
No
CompositeCollider2D.GenerateGeometry does not regenerate Collider when the composite is TilemapCollider2D
How to reproduce:
1. Open up my attached project
2. Add Playground Scene into Hierarchy and Enter Play Mode
3. Observe the Collider behaviour
Expected result: GenerateGeometry() updates the newly created Tiles Collider geometry and the blue falling block collides with the Tiles
Actual result: GenerateGeometry() does nothing when used in this context, a blue block falls down through the white Tiles and hits the red block down below
Reproduced in: 2017.4.39f1, 2018.4.21f1, 2019.3.9f1, 2020.1.0b5, 2020.2.0a7
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
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
- Material Component has two horizontal lines under it when its foldouts are closed
- Some selected Mesh Renderer Materials lead to Assets folder when pinged
- Editor colors appear darkened out when HDR Display Output is enabled
Resolution Note (fix version 2019.3):
Fixed in 2020.2.0a12.1461_72e8467d6ce5
2D: Added: Add HasTilemapChanges and ProcessTilemapChanges for TilemapCollider2D to immediately process Tilemap changes instead of waiting for batched processing in LateUpdate.
New functionality code example:
private Tilemap tilemap;
if (tilemap.GetComponent<TilemapCollider2D>().HasTilemapChanges())
{
tilemap.GetComponent<TilemapCollider2D>().ProcessTilemapChanges();
}
tilemap.GetComponent<CompositeCollider2D>().GenerateGeometry();