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
- 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