Orion Interaction layer crash (Gravity shadow state)

[Merk]

Hello. I googled and searched the topics on this forums, but I could not find anyone with my problem.
I am using leap + Oculus + Unity. Also Orion with the interaction Manager.
Followed the instructions and didn't have a problem initially, but now 2 out 3 times when I try to grab/touch a simple cube that I have assigned with an Interaction behaviour script this error happens and my game pauses.
Any ideas/input from the Leap team?

Gravity shadow state must match actual gravity state.
Assertion failed. Values are not equal.
Expected: True == False
UnityEngine.Assertions.Assert:AreEqual(Boolean, Boolean, String)
Leap.Unity.Interaction.InteractionBehaviour:Validate() (at Assets/LeapMotionModules/InteractionEngine/Scripts/Validation/InteractionBehaviourValidation.cs:26)
Leap.Unity.Interaction.ActivityManager:Validate() (at Assets/LeapMotionModules/InteractionEngine/Scripts/Validation/ActivityManagerValidation.cs:21)
Leap.Unity.Interaction.InteractionManager:Validate() (at Assets/LeapMotionModules/InteractionEngine/Scripts/Validation/InteractionManagerValidation.cs:25)
Leap.Unity.Interaction.InteractionManager:LateUpdate() (at Assets/LeapMotionModules/InteractionEngine/Scripts/InteractionManager.cs:677)

[Joe_Ward]

Are you doing anything with gravity or other rigid body settings at runtime?

[Merk]

I really just have a bunch of cubes laying in a box that the user can pick up and throw around. Default Unity 3d cubes with rigidbody and gravity (non-kinematic).
One other thing that happens in my scene is a crane that picks up one of the cubes (onCollision) which i code as
1)create fixedjoint on crane
2)joint.connectedbody = cube

It would be a hint if Unity crashed when the user and the crane reach for the same cube, but that happens even when the crane is away.
And it's not consistent. Sometimes it happens the moment I put my hand in the box and sometimes it requires some intense wiggling of my hand in the box with the cubes to replicate the error.
But in general it happens 9/10 times.

[alexmarcolina]

For the interaction material that the object is using, what MoveTo controller is it using?

[alexmarcolina]

Actually scratch that, I can replicate it too in the example scene! Looks like it is a slight delay in a state transition that is being caught by the auto-validator. From what i can see, the state always corrects itself quickly enough (which is why you are not getting FLOODED by errors) and so is not a critical error. And so, my recommended temp-fix is to go into InteractionBehaviourValidation.cs and comment out the assert on line 26!

Also remember, as a side note, to disable Auto-Validation once you are finished debugging, since it can slow down the game significantly.

[Merk]

Thanks! Haha, first thing I saw was "FLOODED by errors" . Great I will try disabling Auto-Validate and comment the error and see where that leads.