Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
1
Found in
2019.3.10f1
2019.4
2020.1.0b2
2020.2
2020.2.0f1
2021.1
2021.2
Issue ID
1303344
Regression
Yes
Raycast does not hit BoxCollider2D with RigidBody2D when it's rotated 180 degrees
How to reproduce:
1. Open the attached project ("Raycasttry.zip")
2. Load "SampleScene"
3. Enter Play mode
4. In the Scene View drag "GameObject" so the ray touches the upper side of the rectangle
5. Rotate one of the rectangles 180 on the Z-axis
6. In the Scene View drag "GameObject" so the ray touches the upper side of the rectangle
Expected results: The ray turns green because the BoxCollider2D was hit
Actual results: The ray stays red because the BoxCollider2D was not hit
Reproducible with: 2019.3.10f1, 2019.4.18f1, 2020.1.0b2, 2020.1.17f1, 2020.2.3f1, 2021.1.0b3, 2021.2.0a2
Not reproducible with: 2018.4.31f1, 2019.3.9f1, 2020.1.0a1, 2020.1.0b1
Note: Object must have both BoxCollider2D and RigidBody 2D components
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