Grabbables in Interaction SDK

Grabbable entities in Spatial SDK can be manipulated by a hand or controller. By default, they can be simultaneously manipulated by only a single device at once. Simply add the Grabbable component to an entity to enable grabbing.

To configure some of the grabbing behavior, you can optionally add the IsdkGrabConstraints component to an entity. This component allows you to constrain the transforms or scale of a grabbed object, and lock the object’s position, rotation, and scale attributes.

To enable transform of an entities scale, you will need to enable two-handed transform mode. Don’t enable scale entities that have a Physics component, as the behavior will be unexpected.

Interaction SDK’s IsdkToolkitBridgeSystem automatically adds the grabbable feature to any entity that has both a Spatial SDK Grabbable component and either a mesh or collider component, so you don’t need to make any manual changes to use the feature. However, Interaction SDK’s grabbable feature adds a new movement type called direct, as well as tuning values for responsiveness. To access these features, you’ll need to manually add the IsdkGrabbable component to an entity.

In order for an object to be detected by the Interaction SDK grab system, it must have a Grabbable component and either a Mesh component or a Collider. If both are present, the Collider is used. For improved runtime performance and the ability to use touch-grabs (grabbing an object while your hand or controller is inside it), add collider components instead of relying on mesh component collision. You must use Spatial SDK Collider components, as they are mapped to Interaction SDK’s internal colliders.

This table shows how Spatial SDK colliders map to Interaction SDK’s internal colliders, including the style of grabbing each supports.

If you’ve disabled Interaction SDK’s IsdkToolkitBridgeSystem but want to enable grabbing functionality for an entity, follow these steps.