Search Issue Tracker
Fixed
Fixed in 6000.1.0a9, 7000.0.0a1
Votes
0
Found in
6000.0.26f1
6000.1.0a3
Issue ID
UUM-87102
Regression
Yes
Rigidbody2D.Cast does not detect collisions when 'Is Trigger' property is enabled
Reproduction steps:
1. Open the attached “Physics2DBug.zip” project
2. Open the “SampleScene”
3. Enter the Play mode
4. Select the “Bullet” GameObject from the Hierarchy
5. In the Inspector, find the “Circle Collider 2D” Component
6. Enable the “Is Trigger” property
7. Observe the Game view
Expected result: The green circle disappears after collision
Actual result: The green circle flies over the collider
Reproducible with: 2023.1.0a19, 6000.0.26f1, 6000.1.0a3
Not reproducible with: 2021.3.46f1, 2022.3.52f1, 2023.1.0a18
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Note:
- Enabling Gizmos in the Game view shows point of collision (before ‘Is Trigger’ is enabled)
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