Search Issue Tracker
Duplicate
Votes
0
Found in
2018.4
2019.2
2019.2.11f1
2019.3
2020.1
Issue ID
1197293
Regression
No
Rigidbody's Collision Detection is not changed to Continuous when changing it in a Script after toggling the Is Kinematic option
When enabling the Is Kinematic option in the Rigidbody's Component it changes the Collision Detection to Continuous Speculative. Changing it back to Continuous in a Script affects only the value in the Inspector. When changed, the Sphere's Path doesn't match Continuous Collision Detection Path taken by another Sphere but matches the Continuous Speculative one.
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode
3. Inspect the Spheres in the Game View
Expected result: Gameobjects which have Continuous Collision Detection on their Rigidbodies("PlayerSphereContinuous" and "PlayerSphereSwitchedContinuous") travel the ramp with the same path.
Actual result: "PlayerSphereSwitchedContinuous" follows the path of a GameObject with a Continuous Speculative Collision Detection. ("PlayerSphereSpeculative")
Reproducible in: 2018.4.13f1, 2019.2.13f1, 2019.3.0b11, 2020.1.0a13
Couldn't test with Unity 2017.4.34f1 (Unity crashes while downgrading the project)
Notes:
1. GameObject's Rigidbody's Collision Detection appears to be changed only in the Editor's Inspector
2. If "PlayerSphereSwitchedContinuous" GameObject's Rigidbody's Collision Detection is set to Continuous Speculative before entering Play Mode it follows the correct path when switching the Collision Detection to Continuous during Runtime
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
This is a duplicate of issue #1177698