Search Issue Tracker
In Progress
Fix In Review for 2.5.3, 3.0.0
Votes
0
Found in [Package]
2.5.2
3.0.0-pre.1
Issue ID
XRIT-114
Regression
No
XRPokeInteractor.m_CurrentPokeTarget not respecting GetValidTargets and target filters
Testing environment
- Unity - 2022.3.9f1
- XRI - 3.0.0-pre.1
When I use a custom
{{TargetFilter}} or extend
{{XRPokeInteractor}} and override the
{{{}GetValidTargets{}}}, the target with the higher priority is not the one selected. Going through the implementation of XRPokeInteractor, it seems like the
{{m_CurrentPokeTarget}} is set by the internal methods, which don't respect the re-prioritized targets or provide means to update the value of
{{{}m_CurrentPokeTarget{}}}. As
{{XRPokeInteractor.CanSelect}} is predicated on this variable, the re-prioritized target is not the one selected.
While I haven't tested this, this also would conflict with
{{InteractableSelectMode.Single}} being set.
My current workaround for this is to override
{{{}XRPokeInteractor.CanSelect{}}}.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 3.0.0):
Fixed an issue where target filters could not influence the prioritized poke interactable.
Resolution Note (fix version 2.5.3):
Fixed an issue where target filters could not influence the prioritized poke interactable.