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

useXRInportSourceState fails to update when hand exit view, built-in hand are duplicated. #360

Open
geyang opened this issue Oct 6, 2024 · 2 comments

Comments

@geyang
Copy link

geyang commented Oct 6, 2024

To reproduce:

  1. on the vision pro, open the first example on this page (the room): https://pmndrs.github.io/xr/docs/getting-started/examples
  2. move your hand out of view, then back. A second hand instance shall appear, frozen at the last location where the hand existed tracking range.

Now, if you call useXRInputSource("hand", "left"), the post.data array remains unchanged since VisionPro lost tracking.

IMG_0321

@bbohlender
Copy link
Collaborator

@geyang, thank you for reporting. I will investigate. Unfortunately, I cannot debug because I don't own a Vision Pro. Will contact you once I think I found a resolution so you can confirm, if thats possible :)

@geyang
Copy link
Author

geyang commented Oct 6, 2024

I made a custom Hand component this morning that resolves this issue for our production system. Not sure why the useXRInputSource hook is providing stale states though. The bug remains.

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