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
- 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
This is a duplicate of issue #905832