Gating Locomotion

In most experiences, locomotion must coexist with other interactions. To avoid blocking other potential interactions, locomotion should be triggered only after certain requirements are met. This is called gating and is specially important for Hand Locomotion where the hands intentions can be ambiguous.

Given a list of possible interactors, an InteractorGroup prioritizes one interactor and disables the others. This ensures the correct interaction occurs. For example, your hand is near a button, so the Interactor Group enables poke and disables locomotion. There are a multiple types of Interactor Group. Each type uses different criteria to determine the prioritized interactor. To learn about Interactor Groups and how they prioritize interactors, see Interactor Groups.

One particularity of the Locomotion interaction is that in most use-cases it must coexist with Grab interactions, allowing to hold an object while moving around the world. This means that Locomotion interactors and Grab Interactors should not block each other in the same InteractorGroup, but Poke and Ray interactors should. For this particular use case you can use a HoverInteractorsGate

When active, the LocomotionGate component outputs two active states for the Teleport and Turn Interactors to read from based on the wrist roll angle. It requires specific hand poses to enter or exit the active state, and when active it decides which one of the interactors to enable based on the wrist roll. The default Hand Pose for entering locomotion is called the L-Shape (Index and thumb extended; middle, ring and pinky curled) while curling the index finger is the default exit pose.