Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.1.X, 2017.2.X, 2017.3.X
Votes
1
Found in
2017.1.1p3
Issue ID
957044
Regression
Yes
Setting Collider.enabled to False in Animation does not disable the Collider
Steps to reproduce:
1.Open attached “ColliderAnimation.zip” Unity project
2.Open scene “Test"
4.Select “Collider Parent” object in Hierarchy
5.Enter Play mode (with Gizmos enabled)
Expected results:
Collider disappears after it is disabled in Animation
Actual results:
Collider does not disappear after it was disabled in Animation and is stuck in the position it was disabled in until it is re-enabled again
Reproduced in: 2017.3.0b4, 2017.2.0f3, 2017.1.2f1, 2017.1.1p3, 2017.1.1p2
Didn’t reproduce in: 2017.1.1p1, 5.6.4f1, 5.5.5f1
Regression introduced in: 2017.1.1p2
Comments (2)
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
- Unity Version Control window during "Create workspace" updates only when the mouse is moved
- Crash on AudioMixer::GetFloat when entering Play Mode in a specific project
- Test assembly files are not generated when using a local package included in a subdirectory
- URP Terrain Shaders are always included when building on any target platform
- Multiple errors thrown and Scene/Game view is not rendered when Lighting Override Mask is set to the same layer as the Volume
paxtonmason
Oct 20, 2017 01:14
This is a serious issue for our team. Can we get a patch release?
Rennan24
Oct 12, 2017 15:52
Would really like to see this fixed soon, Especially since 2017.2 looks really nice and this bug is kinda preventing me from upgrading. Hopefully in the next 2017.2 patch release the Unity team squashes this bug :D