Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f3
Issue ID
951374
Regression
No
ContactFilter2D is checking if triggers are involved rather than checking for the target collider in the isTouching() method
How to reproduce:
1. Open attached Unity project "IsTouchingTest.zip"
2. Load "IsTouchingTest" scene
3. Set Layout to see Scene view
4. Select "Test" in the Hierarchy window
5. Enable "Use Triggers" in the Contact Filter
6. Enter Play mode
Expected Result: "Is Touching" check box is not enabled. Neither of colliders are triggers.
Actual Result: "Is Touching" check box is enabled despite the fact that both colliders are not set as triggers.
Reproducible with: 2018.1.0a1, 2017.3.0b4, 2017.2.0f3, 2017.1.2f1, 5.6.4f1
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
This bug's priority is too low and changing the behaviour comes with a risk and as such we will not be spending time with this in the foreseeable future.