XRPokeFilter is not preventing Near-Far Interactor selects on XRSimpleInteractable

Target Platforms XR
,
1

Hello,

Our team is in the process of updating to XRI 3.0+ from 2.5+ and noticed a potential bug that became apparent with the near-far interactor being more sensitive at registering hover and selects on XRSimpleInteractables than the 2.5X interactors. We are using XRPokeFilters on these interactables which we believe should only allow poke selects. However, it appears Near-Far Interactors are able to hover and subsequently register a select on XRSimpleInteractables well outside their XRPokeFilter collider. Is this supposed to happen? I don’t want to use a separate layer because I still want to be able to use the far-interactor with the TrackedDeviceGraphicsRaycaster also on the GameObject. Making a custom hover filter or extension of the poke filter is an option, but it seemed the base poke filter should be enough.

Thanks,
Alex

2

Hey could you setup a repro project for this? You could also report a bug by doing help → report a bug.

3

Sorry to necro this, but I seem to have the same issue with 3.08.

Using the standard XR Rig, I create a cube with a simple interactable and a poke filter.

It still responds to near/far interactions (hover and select).

As part of my exploration, I specified the select and interaction strength filters on the interactable (to be thorough), but Poke Filter does not implement IXRHoverFilter.

To resolve the issue, I wrote a quick script, added it to my interactable, and set it to the Hover Filter.

No warranties or guarantees here: I am learning this system. :slight_smile: But it works.

 	public class BlockNearFarFilter : MonoBehaviour, IXRHoverFilter
	{
		public bool canProcess => true;

		public bool Process(IXRHoverInteractor interactor, IXRHoverInteractable interactable)
		{
			if (interactor is NearFarInteractor)
			{
				return false;
			}
			return true;
		}
	}