We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The WebXR hand tracking API explainer recommends using fillPoses and fillJointRadii as a way of reducing the number of javascript objects created per-frame while updating tracked hand models: https://github.com/immersive-web/webxr-hand-input/blob/main/explainer.md#efficiently-obtaining-hand-poses
fillPoses
fillJointRadii
WebXRHand still uses the inefficient method:
Babylon.js/src/XR/features/WebXRHandTracking.ts
Line 347 in 3a9e132
In order for BabylonNative to maintain support, we will want to get BabylonJS/BabylonNative#773 closed first.
The text was updated successfully, but these errors were encountered:
Hi @rgerd - will you be implementing this? Should I assign you?
Sorry, something went wrong.
@RaananW Yes I'm working on it now. Thanks!
RaananW
rgerd
Successfully merging a pull request may close this issue.
The WebXR hand tracking API explainer recommends using
fillPoses
andfillJointRadii
as a way of reducing the number of javascript objects created per-frame while updating tracked hand models:https://github.com/immersive-web/webxr-hand-input/blob/main/explainer.md#efficiently-obtaining-hand-poses
WebXRHand still uses the inefficient method:
Babylon.js/src/XR/features/WebXRHandTracking.ts
Line 347 in 3a9e132
In order for BabylonNative to maintain support, we will want to get BabylonJS/BabylonNative#773 closed first.
The text was updated successfully, but these errors were encountered: