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
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
nathansisler
Oct 03, 2018 01:18
Updated to .3.0b3 and getting this
nathansisler
Oct 03, 2018 01:18
Updated to .3.0b3 and getting this
A567W
Oct 01, 2018 01:57
Set the collision detection mode to "Discrete" or "Continuous Speculative" on the objects Rigidbody to get rid of the error.
A567W
Oct 01, 2018 01:25
Getting same error in 2018.3.0b3
A567W
Sep 27, 2018 07:10
Getting same error in 2018.3.0b2
thelebaron
Sep 24, 2018 15:59
Occurs in 2018.3.0b2
Immu
Sep 20, 2018 15:09
Same issue here with 2018.3.0b1
Does that mean that 'Fixed in Unity 2018.3', is that up to date with that statement ? We're completely in the blur here.
Hagen
Sep 20, 2018 00:14
Same issue here with 2018.3.0b1
HugoTremblay
Sep 19, 2018 00:21
I get the same error in my project.
Zilby
Sep 18, 2018 05:39
Getting same error in 2018.3.0b1