open-ecosystem-development / OpenXR-SDK

Apache License 2.0
2 stars 3 forks source link

Only the controller with "/user/hand/left" path works #3

Closed MortimerGoro closed 2 years ago

MortimerGoro commented 3 years ago

SDK: hvrsdk-openxr-3.0.0.33.zip

When using the 6DOF kit dual controllers only the controller with "/user/hand/left" path seems to be available. And it's associated with the physical right controller instead of the left one

MortimerGoro commented 3 years ago

I updated to 3.5.0.67 and now it's able to detect both controllers. However, "/user/hand/left" seems to be still attached to the right controller, so I have to invert controller modes in my local code.

fwei-io commented 3 years ago

VR Team - the preliminarily finding is it is not an issue: we suggest sharing your code implementation. The virtual fence/border in version 3.5.0.67 is based on the key information obtained by the OpenXR interface, and the left and right hand key press events are valid.

@MortimerGoro please share your findings/log/implementation. Thanks.

fwei-io commented 3 years ago

@VR Team please see https://github.com/hms-ecosystem/OpenXR-SDK/issues/4 last comment

MortimerGoro commented 3 years ago

Could you share the link to download the 6DOF demo? I need it to test if the paths are working correctly using that demo and see the differences with our code

I also added instructions to build Firefox Reality here: https://github.com/hms-ecosystem/OpenXR-SDK/issues/16 Let me know if you have any questions.

fwei-io commented 3 years ago

@MortimerGoro please rebuild, test and share the findings, thanks.

MortimerGoro commented 3 years ago

I have seen this comment in the SDK demo version I have:

 /* Attention!!!:
 In this demo, index 0 represents the left hand.
 But in the latest released SDK version, 0 represents the right hand. This is a bug that will be solved in the future.
 If you want to get the left hand action data with the latest released SDK, you should use Info.subactionPath = LRPath[1].
 And get the right hand action data with the latest released SDK by using: Info.subactionPath = LRPath[0].
 */

So I'll wait until this is fixed in the next SDK version and continue using the workaround for now

lzhangcs commented 2 years ago

issue cannot be reproduced.