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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.