Breaking Bug in Unity 5.2.2p4 and 5.3

[TakuanDaikon]

Reported on the Daikon Forge forums at http://www.daikonforge.com/forums/threads/breaking-bug-in-unity-5-2-2p4-and-5-3.2455/

If you've upgraded to Unity 5.2.2p4 (or 5.3) you may have noticed that dfcontrols stop receiving all input. This is caused by a change to Unity's rigidbody system. From the patch notes:
(702967) - Physics: Setting Rigidbody.detectCollisions to false also affects queries now (e.g. Physics.RaycastAll).
The problem is that dfgui adds a rigidbody to every control (invisible in the editor) at runtime, and sets detectCollisions to false. The notes in dfcontrol give this reason for adding the rigidbody:

// Add a kinematic rigidbody at runtime to make moving controls and
// updating the collider less expensive (in theory, not conclusive)

Removing the block that adds the rigidbody fixes the bug. While removing the single line that sets detectCollisions should also work, it seems like a less robust fix. But you can play around and see what works best for you.

Hopefully this post will help someone else out there who's still using dfgui.

[mtfuji25]

Hello @TakuanDaikon
Can you please let me know which code snippet should I remove?
And also which script file should I edit?
Thanks