Search Issue Tracker

Fixed in Unity 2019.1

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

Physics

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 3Secondary functionality broken

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 (59)

  1. 29a0a6c72cf3d87617183a65d1ff80b4?d=mm

    Aqualancer

    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..

  2. 29a0a6c72cf3d87617183a65d1ff80b4?d=mm

    Aqualancer

    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

  3. 613debbacefa127c1e9d55d5c5ad48a7?d=mm

    kexar66

    Jan 29, 2019 10:14

    We need this to be fixed in 2018.3!

  4. 556cdcf58b07a93ad3b49cf356b2319d?d=mm

    SillyBilly

    Jan 25, 2019 16:48

    ... also, 2018.3.3 doesn't have a fix either, for those looking.

  5. 556cdcf58b07a93ad3b49cf356b2319d?d=mm

    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!

  6. 609bc443c10c28ceda670b503d06ec61?d=mm

    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?

  7. 54883a2e042325b35101aff7cf6fceb6?d=mm

    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.

  8. 54883a2e042325b35101aff7cf6fceb6?d=mm

    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.

  9. 783d50c318ea066fe50bde531bf259b3?d=mm

    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.

  10. 783d50c318ea066fe50bde531bf259b3?d=mm

    Zullar

    Jan 16, 2019 04:16

    I have a massive project with many objects and can't find the object throwing this error. Any ideas how to find them?

    Thanks.

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.