Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2021.2
Issue ID
1344958
Regression
No
CustomCollider2D doesn't use the Collider2D.Offset property for its PhysicsShape2D.
Reproduction steps:
1. Open the attached project "CustomColliderOffset.zip"
2. Open the "SampleScene" scene
3. Select the "CustomShape" GameObject
4. Adjust the "Offset" property on the "CustomCollider2D" component
Expected result: All the shapes in both the Game/Scene views moves with the offset
Actual result: The shapes do not move with the offset
NOTE: There is an additional minor and cosmetic issue that is also fixed under this bug report because it didn't really justify the additional overhead of a full bug report. If you notice in the screenshot attached, the Polygon Shape isn't the correct color (it's purple and not green). This is due to some specific issue when drawing the previous shape in the test project (Edge shape). This has also been fixed as can be verified by seeing all shapes are drawn in the gizmo colour (green).
Reproducible with: 2021.2.0b1, 2022.1.0a1
Not reproducible with: Feature landed in 2021.2.0b1
Reproducible with: All Editors
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