Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2017.4.0f1
2018.4.0a1
2019.1.0a1
2019.1.6f1
2019.2.0a1
2019.3.0a1
Issue ID
1162291
Regression
No
CompositeCollider2D produces incorrect polygon collision normals for collision-detection
How to reproduce:
1. Open the attached project ("steel-flood.zip")
2. In the Hierarchy Window click on the "RoomsFactory" object
3. Observe the collider in the Scene Window
4. Enter Play Mode and using the arrow keys on the keyboard move to the right
5. Observe the Player's movement
Expected result: the player object walks on a flat surface and doesn't fall through the collider when walking to the left
Actual result: the player object walks on a ramp-like surface and falls through the collider when walking to the left
Reproduced in: 2019.3.0a6, 2019.2.0b6, 2019.1.7f1, 2018.4.2f1, 2017.4.28f1
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