Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XR_HTCX_vive_tracker_interaction rev 3 unsupported paths #1769

Open
amini-allight opened this issue Sep 27, 2023 · 1 comment
Open

XR_HTCX_vive_tracker_interaction rev 3 unsupported paths #1769

amini-allight opened this issue Sep 27, 2023 · 1 comment

Comments

@amini-allight
Copy link

amini-allight commented Sep 27, 2023

This bug report is for SteamVR's OpenXR runtime functionality rather than OpenVR, but I have been instructed to post such bug reports here by a Valve employee in the past.

When I call xrSuggestInteractionProfileBindings to suggest bindings that involve paths from the third revision of XR_HTCX_vive_tracker_interaction I get the following error, or a similar one with a different path:

[Info] - Warning: Provided input path (/user/vive_tracker_htcx/role/left_wrist/input/grip/pose) is not valid for this interaction profile (/interaction_profiles/htc/vive_tracker_htcx)

I also get XR_ERROR_PATH_UNSUPPORTED as a return value from the call. I'm submitting these paths the exact same way as I submit paths from earlier revisions like /user/vive_tracker_htcx/role/chest/input/grip/pose, which work correctly. I believe this is meant to be supported, the patch notes for SteamVR 1.27 reference support for the new revision and xrEnumerateInstanceExtensionProperties returns revision 3 as well.

Platform info:

  • Valve Index headset
  • AMD RX 6900 XT
  • Linux 6.5.4
  • Mesa 23.1.8
  • SteamVR 2.0.2
@a2flo
Copy link

a2flo commented Dec 15, 2023

Sadly this is still an issue on SteamVR 2.1.10 and 2.2.2 (beta).

I've also downgraded to 1.27.5 (temp_v1.27.5 branch) to check this again and this branch strangely also has this issue now.
When I originally tested this with 1.27.4, it did actually work. Seems like something must have gotten reverted between 1.27.4 and 1.27.5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants