Search Issue Tracker
Duplicate
Votes
0
Found in
5.6.0p4
Issue ID
925307
Regression
Yes
Capsule Collider bounds return different value when setting properties in different order
Steps to reproduce:
1. Open attached "CapsuleBug.zip"
2. Enter play mode
3. Observe console output - 2 colliders with same setting have different bounds
Expected: The 2 bounds outputs should be the same
Actual: The first collider bounds are calculated incorrectly
Reproduced on 5.6.0f1, 5.6.2p1, 2017.1.0f1, 2017.2.0b1
Regression introduced in: 5.6.0b10
Doesn't reproduce on 5.5.4p1, 5.6.0b1, 5.6.0b8, 5.6.0b9
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
- 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
This is a duplicate of issue #905832