Search Issue Tracker
Fixed
Fixed in 6000.0.41f1, 6000.1.0b9, 6000.2.0a5, 7000.0.0a1
Votes
0
Found in
2022.3.14f1
2023.2.0f1
2023.3.0a15
6000.0.37f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-56687
Regression
No
[2D] Collider2D.Cast does not respect the collision matrix
Steps to reproduce:
1. Open the attached user's project "IssueReproducible.zip"
2. Open "SampleScene.unity"
3. Enter Play Mode
4. Observe Console Window
Expected Result: Collider2D.Cast respects collision matrix
Actual Result: Collider2D.Cast does not respect the collision matrix
Reproducible with: 2022.3.14f1, 2023.2.0f1, 2023.3.0a15
Could not test on 2021.3.32f1 due to scripting errors and missing definitions
Testing Environment: Windows 10
Not reproducible on: No other environment tested
Notes:
-Related forum thread: [https://forum.unity.com/threads/collider2d-cast-does-not-seem-to-respect-collider2d-excludelayers.1518301/]
-The Collider2D.Cast method, specifically the overload that does not take a ContactFilter2D, should adhere to the collider's collision rules, including the collision layer matrix and overrides like excludeLayer.
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note (fix version 6000.2.0a5):
Fix for this issue is available on Unity 6000.2.0a5 and above
Resolution Note (fix version 6000.0.41f1):
Fix for this issue is available on Unity 6000.0.41f1 and above