Closed jloehr closed 9 months ago
We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!
Describe the bug
NearInteractionTouchableVolume
stops working in certain situations and set-ups. This is when the volume is touched and the hand is moved into a certain position, so that the PokePointer ray is hitting a different collider in the scene due to its massive range.Below you can see the bug reproduced in the
HandInteractionTouchablesExample
scene. The bug change increases with the amount and size of colliders in the scene:https://user-images.githubusercontent.com/4631548/162165176-79331f1b-e312-4a52-9b6d-7cd1280b4b40.mp4
To reproduce
Steps to reproduce the behavior:
HandInteractionTouchablesExample
scene.Expected behavior
NearInteractionTouchableVolume
works regardless of scene and unrelated collider set-ups. Especially a scene setup, where theNearInteractionTouchableVolume
is enclosed by other colliders.Your setup
Target platform (please complete the following information)
PokePointer
support.Additional context
I do have a fix in the workings, that I'll PR once I have finished some additional tests.