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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
This is a duplicate of issue #905832