Describe the problem
In an XRController world, we essentially had a 1-to-1 mapping of a set of select action mappings to each controller, which then bubbled down to every interactor of a specific handedness. This led to us needing to use the same set of mappings for both near and far interaction, which was fine but nonoptimal.
Describe the solution you'd like
With the move to assignable IXRInputButtonReaders in XRI3, we should be able to separate out the actions for far interaction vs near interaction. Far rays typically default to more of an "airtap" while near grab interactors should listen for "grasp".
Describe the problem
In an
XRControllerworld, we essentially had a 1-to-1 mapping of a set of select action mappings to each controller, which then bubbled down to every interactor of a specific handedness. This led to us needing to use the same set of mappings for both near and far interaction, which was fine but nonoptimal.Describe the solution you'd like
With the move to assignable
IXRInputButtonReaders in XRI3, we should be able to separate out the actions for far interaction vs near interaction. Far rays typically default to more of an "airtap" while near grab interactors should listen for "grasp".