Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X
Votes
0
Found in
2017.2.0b8
Issue ID
945332
Regression
Yes
Moving a Collider via script does not update its position if it was disabled on start and enabled after
Reproduction steps:
1. Open the attached project "test mesh move.zip";
2. Open the test.unity scene;
3. Select "a rock" game object and make sure that Mesh Collider is disabled;
4. Enter a play mode;
5. Enable the Mesh Collider and select "Drop Object on it";
6. Then select "Move it" to move the object and drop another object.
Expected: both times physics should work the same - falling object should hit the static object and then fall.
Actual: after moving object, its position is not updated and the object falls like there is no obstacle.
Reproduced on: 2017.2.0b9, 2017.3.0a6.
Not reproduced on: 2017.1.0p5, 5.6.3p2.
Regression firstly introduced: 2017.2.
Note: physics work if the Collider is enabled on start.
Issue is fixed on: 2017.3.0b6.
Comments (3)
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
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
nitzanwilnai
May 03, 2019 07:41
Happening again on 2018.3.13f1
FaberVi
Jun 25, 2018 11:10
Same Bug on Unity 2018.1.6f1.
Supergeek
Feb 14, 2018 15:40
Probably related issue:
https://issuetracker.unity3d.com/issues/colliders-are-not-updating-to-match-attached-gameobject-location
Which is not fixed in 2017.3.1f1.