Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a5
Issue ID
1064491
Regression
Yes
"RigidBody::setRigidBodyFlag: kinematic bodies with CCD enabled are not supported!" error thrown during playmode
How to reproduce:
1. Open attached "ErrorRepro" project and "Courtyard" scene
2. Enter playmode and wait for a few seconds
Actual result - Error is thrown: "[Physics.PhysX] RigidBody::setRigidBodyFlag: kinematic bodies with CCD enabled are not supported! CCD will be ignored"
Expected result - If the error is expected, add GameObject context to let users fix the error within the GameObject
Regression introduced with - 2018.3.0a5
Reproducible with - 2018.3.0a7, 2018.3.0a5
Not reproducible with - 2018.3.0a4
Comments (60)
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
SlyTrip
Jan 03, 2019 22:18
Upgrading to the 2019.1 beta resolved this issue for me.
Marrt
Dec 31, 2018 12:41
if you stumble upon this, just make sure that you set your collision mode before setting isKinematic:
thisRigid.collisionDetectionMode = CollisionDetectionMode.Discrete;
thisRigid.isKinematic = true;
TraeMaze
Dec 24, 2018 17:42
Hello everyone. Hope this helps. https://docs.unity3d.com/ScriptReference/Rigidbody-collisionDetectionMode.html
Arkade
Dec 22, 2018 14:34
I've written an Editor script to help you find causal objects in your scene and/or project. HTH:
https://gist.github.com/Arakade/dc1d6623cafaab07aeee92a8a1cf661f
Ak47-forever
Dec 21, 2018 11:09
happen in 2018.3.0f2
Squeyed
Dec 20, 2018 11:17
Same error for me too after upgrading to 2018.3.0f2.
Robko75
Dec 19, 2018 21:14
Guess what: Same error after upgrading to 2018.3.0f2.
mbrindic
Dec 18, 2018 08:05
Same here!
SomeAlexander
Dec 17, 2018 10:31
Same error after upgrading to 2018.3.0f2.
t-kuhn
Dec 17, 2018 09:38
We're also getting this error after upgrading to Unity 2018.3.0f2!