Search Issue Tracker
Fixed in 2017.2.X
Votes
1
Found in
5.6.1f1
Issue ID
912158
Regression
No
[OSX] ContactFilter2D.useNormalAngle does not respond to collisions
To reproduce:
1. Download attached project "ContactFilter2D.zip" and open in Unity
2. Open "scene" scene
3. Enter to Play mode
Expected result: In Console window, these messages will start spamming:
useNormalAngle = false: Hit!! Angle = 90
IsFilteringNormalAngle(90) = False
useNormalAngle = true: Hit!! Angle = 90
Actual result: In Console window, only these messages will start spamming:
useNormalAngle = false: Hit!! Angle = 90
IsFilteringNormalAngle(90) = False
And this message will appear only one time:
useNormalAngle = true: Hit!! Angle = 90
Note: This issue appears only on OSX.
Reproduced on Unity 5.6.0p1, 5.6.1p1, 2017.1.0b7 and 2017.2.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment