Search Issue Tracker
Fixed in 2017.1.X
Votes
1
Found in
5.6.0b3
Issue ID
865250
Regression
No
Collider.ClosestPoint & ComputePenetration return incorrect result when a collider has it's centre offset with non-zero rotation
Reproduction steps:
1. Open the attached project
2. Select the Cube game object in the hierarchy
3. Under the "BoxCollider" component, move the y axis to -1.5
4. Rotate the Y axis of the cube by 45 degrees and Z axis by 60 degrees.
Result: the line is not drawn correctly, there is a gap between it and the point it's supposed to be touching
Note, this does not happen with any other collider than BoxCollider
Reproducible on 5.6.0b2, 5.6.0b3
Tested on Windows 10
Fixed in: 2017.1.0b2
Backported to: 5.6.1p1
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
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- Constant console errors when using Min/Max Slider in PlayMode
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- [Linux] AutoLocale log is logged when opening a project
hippocoder
Jul 02, 2017 13:47
Still buggy
Evaldas_Unity
May 19, 2017 07:54
Hello everyone : )
I have edited the issue tracker to clear up the confusion on where this is fixed.
Once it updates, it should say where it was fixed and where it was backported under the reproduced versions.
Evaldas
Unity QA
Simeon
Apr 12, 2017 20:49
Confirmed, still exists in 5.6.0f3
judgementAlex
Apr 06, 2017 05:31
Currently seeing this bug in 5.6.0f3
TH_Unity
Mar 11, 2017 14:27
The bug is not yet fixed!
When you offset the center of the BoxCollider and then apply rotation to the transform, the point calculated is still in the wrong place.
TH_Unity
Jan 23, 2017 17:13
This bug still exists in 5.6.0b4