Search Issue Tracker
Fixed in 2021.1.X
Votes
1
Found in
2018.3.5f1
2018.4.6f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1177698
Regression
Yes
Rigidbody Collision Detection mode cannot be updated after setting the isKinematic field to true then false during runtime
How to reproduce:
1. Open user's attached project ("RigidBodyCollisionDetectionChange.zip") using the EnvIronman VM (more information in Edit)
2. Open the sample scene
3. Enter Play mode
4. Observe where the green Cube GameObjects collide
Expected result: Green Cube GameObjects collide exactly like the red Cube GameObjects
Actual result: Green Cube GameObjects collide exactly like the blue Cube GameObjects
Reproducible with: 2018.4.7f1, 2019.1.14f1, 2019.2.2f1, 2019.3.0a12, 2020.1.0a1
Notes:
The Inspector window displays the Collision Detection mode as expected.
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
- [iOS] Crash on ScriptingGCHandle::Acquire when calling RequestUserAuthorization without using yield for pending authorization
- Particle is not visible in RenderTexture when Renderer's material is set to Default-Particle and Camera's BG Alpha is set 0
- [Physics] Character Joint jumps around when following Kinetic Rigidbody
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
Resolution Note (fix version 2021.1):
CCD type is restored to specified Collision Detection type in Rigidbody Inspector when isKinematic is toggled from true to false