Sounds like it could possibly be firmware related. On VRX please make sure that your device is using the latest firmware 829 with Snapdragon Spaces Services 0.18.0. Please note that the combination of a higher Snapdragon Spaces plugin with a lower services version is not recommended and may cause some issues. As of now we still recommend using 0.17.0 plugin with the latest VRX firmware 829 until there is a software update for VRX with 0.19.1 services.
Awesome - thanks for the update Simon!
Just following up on this. The bug that prevented use of XR Hands has been fixed in Snapdragon Spaces 0.21.0.
Please note that for VRX the recommended Plugin version is still 0.19.1, meaning the 0.21.0 SDK should only be used with A3 at the moment.
Thanks Simon, I guess ill just use the QCHT one for now.
We found a bug in the Snapdragon Spaces Services that is going to prevent the use of XR Hands via OpenXR. We have a fix scheduled that is likely going to be shipped with Snapdragon Spaces 0.21.0.
Unfortunately, we can't provide information on how to set up XRHands since it is not officially supported by Snapdragon Spaces.
I think that the challenge consists of getting the hands data coming from QCHT from the runtime via OpenXR into a format that works for XRHands and its subsystem.
In case you would like to use our solution QCHTI instead, please refer to Hand Tracking Overview (qualcomm.com)
Hey, I am using the AR3, with spaces 0.19.1, also not having any luck making it work, is there any specific setup i should follow?
I've not had any luck getting XRHands (OpenXR data hands) to work on the VRX - I assume due to the update that Simon mentions - but I've had them working perfectly fine on our reference design headsets, so can only assume the VRX will also work fine after the Lenovo firmware update :)
Hi Ahmed.
Are you on VRX or A3? Your device needs Snapdragon Spaces Services 0.19.1 which are only available for A3 at the moment until there is a firmware update from Lenovo for VRX.
If you are asking about the Unity implementation side of XR Hands with Spaces - unfortunately we do not have documentation for it as it is not officially supported but given the OpenXR standard it should work regardless.
Perhaps Matt can fill you in on some specifics of their use of XR Hands.
Our hand tracking team suggested to look at https://docs.spaces.qualcomm.com/unity/handtracking/XRHandController.html#interaction-profiles as guidance on getting OpenXR interaction data into Unity's input system. Other than that, there should not be much more needed.
I'll check if we can provide documentation for XRHands usage in the future.
Hello, So if i have a seen with XR hands setup, what should i do in order for it to work with spaces?, i updated the services and the SDK to 0.19, and am using the Lenovo development kit
Hmm nevermind, it seems this was a headset issue, we've seen hands working via OpenXR on some other hardware. Thanks anyway!
Hey, are there any more updates on this now that 0.19.1 is released?
I'm still struggling to get Qualcomm hands via the regular OpenXR route. All the examples still seem to show using the QCHT extensions, rather than base Unity stuff.
Hi Matt,
the hand tracking extension made it into the 0.18.0 release. Unfortunately, this release is not a public one that can be downloaded on our dev portal.
We will be reaching out to internal contacts at Ultraleap to continue.
The next public release is 0.19.0 which is scheduled in ~1 month and can be downloaded from our dev portal.
Hey, are there any updates on this release?
Matt. filer
Hey!
Are there any plans to support XRHands through Snapdragon Spaces any time soon? We currently rely on XRHands for our entire project, so the QCHT manager for hand data is incompatible with our setup.
Cheers.