Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.1.X, 2019.2.X
Votes
0
Found in
2019.1.0a1
2019.1.0f2
2019.2.0a1
Issue ID
1148573
Regression
Yes
Tilemap's collider is offset on the X-axis when using Isometric Tilemap
Reproduction steps:
1. Open the attached project named "Case_1148573"
2. Open the Sample Scene and select the Tilemap gameObject
3. Observe the Tilemap's collider
Expected result: Tile's collider matches the grid ( Snapshot_1148573_V1 )
Actual result: Tile's collider is offset on the X-axis ( Snapshot_1148573_V2 )
Reproducible with: 2019.1.0a1, 2019.1.0f2, 2019.2.0a13
Not reproducible with: 2018.3.14f1
Could not test with: 2017.4
Notes:
1. Isometric Tilemap was not available in 2017.4
2. Tile's Collider Type is set to "Grid"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment