IssueSyncBot
commented
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 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 problem
The view area of Hololens 1/ 2 is a lot smaller than the perceivable area of the player. This means he can perform interactions with his hand and accidentially move outside of the view area without noticing the Lens losing track of the hand. Currently this leads to just dropping the current interaction. Interactions like scaling therefore mean to aim at the corresponding handle again and drag again It also leads to additional carefulness due to a certain threshold awareness, reducing the used interaction space even further (The player tries to avoid loss of control and keeps his hand even closer to the center)
Describe the solution you'd like
A hand interaction should not be canceled immediately. The user should be given a configurable amount of time to move his hand back into the perceivable space. If the hand pose still matches the last one, the interaction can carry on. Accompanied with an indication of the tracking loss, the user can use more of his interaction space and does not lose too many of his ongoing interactions. Furthermore he learns more about the spacial limitations by not de- but exceeding the borders of the view area.
Describe alternatives you've considered
none
Additional context
Add any other context or screenshots about the feature request here.