Search Issue Tracker
Duplicate
Duplicate in 3.4.X
Votes
1
Found in [Package]
2.6.3
3.1.0-pre.1
3.4.0
Issue ID
XRIT-222
Regression
No
[HandsDemoScene] Unusable wrist menu buttons
Wrist menus are inoperable in HandsDemoScene from XRI package samples. To make a wrist button appear you must point your fingers away from you, with your thumb pointing down. This is uncomfortable, and it means the wrist button faces away from your other hand, which makes it nearly impossible to select via raycast. And I could not poke the wrist button because it is inside my real-world hand.
Note: This is a bug using Hand Interaction Profile and does not reproduce using Meta Aim Hand
Steps to reproduce:
1. From the attached repro project, open HandsDemoScene using Unity 6000.0.
2. Build and run on Quest.
3. Hold your open hands in front of you in various orientations until the wrist menu button appears.
4. Poke the wrist menu button.
5. Raycast select the wrist menu button.
Actual results:
To make a wrist button appear you must point your fingers away from you, with your thumb pointing down.
The button appears inside your physical hand, which prevents you from selecting the button via poke.
The button faces away from your body, making it difficult to position your other hand such that it is in view of the HMD while making a pinch gesture for raycast.
Expected results:
The wrist menu button should appear when your palm is facing you, probably with your fingers pointing somewhat upward.
It should be easy to invoke the wrist menu by selecting the wrist button, either via poke or raycast.
Reproducible with versions:
- Occurs in XRI 3.4.0 but is slightly improved
- XRI 3.1.0-pre.1 + Unity 6000.0.29f1 + Quest 3
- XRI 3.1.0-pre.1 + 2022.3 + Quest 2
- XRI 2.6.3 + Unity 2021.3.45f1 + Quest 3
Not reproducible with versions:
Can’t test with versions:
Tested on (OS): Quest using OpenXR
Notes:
- Many users might not realize wrist menus are part of this demo due to low discoverability (i.e. button appears only during very awkward and specific gesture, feature barely mentioned in documentation).
-
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.
We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.
Thank you for helping us improve Unity! -
Resolution Note (3.4.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.
We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.
Thank you for helping us improve Unity!
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
This is a duplicate of issue #XRIT-241