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
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
AlexDjenkov
May 26, 2019 06:53
The error occurs in version 2018.3.0b3 for me too
Ruhan-
Feb 02, 2019 07:34
Just as I thought, I didn't have any CCD issues
The same default 5 errors kept being thrown for no reason
Upgraded to Unity 2018.3.4f1 - now console is clean as a whistle!
Hopefully this issue stops reappearing :\ Unity 2018.3 is not the first time it appeared.
I fear it won't be the last..
Ruhan-
Feb 02, 2019 06:51
From Unity 2018.3.4f1 release notes:
"Physics: Added a message with a reference to the Rigidbody component when the CCD mode is incompatible with the kinematic setting. (1064491)"
https://unity3d.com/unity/whats-new/2018.3.4
kexar66
Jan 29, 2019 10:14
We need this to be fixed in 2018.3!
SillyBilly
Jan 25, 2019 16:48
... also, 2018.3.3 doesn't have a fix either, for those looking.
SillyBilly
Jan 25, 2019 16:46
What ASOTELO94 said, this is a real pain in the derrière for us, would be great to see it patched into 2018 soon!
asotelo94
Jan 22, 2019 20:15
I read that this is fixed in Unity 2019.1, but will it be fixed for an 2018 LTS?
kibo_gluk
Jan 20, 2019 17:05
Same here. I had to switch to beta. I tried to fix it in a code. I disabled all objects. I'm doing VR Daydream. I can't go and change their framework!!! So moved to beta. Or stay at your current working one. This is probably why they created Unity Hub.
kibo_gluk
Jan 20, 2019 17:04
Same here. I had to switch to beta. I tried to fix it in a code. I disabled all objects. I'm doing VR Daydream. I can't go and change their framework!!! So moved to beta. Or stay at your current working one. This is probably why they created Unity Hub.
Zullar
Jan 16, 2019 16:24
I have a massive project with many objects and can't find the object throwing this error. Any ideas how to find them?
Thanks.