You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently the Oculus Browser updated its implementation of the WebXR Hands API from this October 2020 draft to this March 2021 draft which changed some fundamental aspects of how hand joints are referenced and how they are oriented in space. For example, joints are no longer referenced via an Array (eg. INDEX_PHALANX_TIP = 9; joints[ 9 ]), but by named Object (eg. joints[ 'index-finger-tip' ]). The joint naming convention itself has also changed. While an evolving API can sometimes be frustrating to support I’m nonetheless very happy to see folks pushing this API forward. It’s still early days, after all.
Handy has been updated to handle the joint referencing changes, and so on. But currently it does not support the joint orientation changes that the API has implemented—this means Handy is temporarily broken. The orientation changes are being addressed within Three.js itself: mrdoob/three.js#21712 Once these updates to Three are complete I’ll incorporate them into Handy and it should work again as intended 👍
The text was updated successfully, but these errors were encountered:
Recently the Oculus Browser updated its implementation of the WebXR Hands API from this October 2020 draft to this March 2021 draft which changed some fundamental aspects of how hand joints are referenced and how they are oriented in space. For example, joints are no longer referenced via an Array (eg.
INDEX_PHALANX_TIP = 9; joints[ 9 ]
), but by named Object (eg.joints[ 'index-finger-tip' ]
). The joint naming convention itself has also changed. While an evolving API can sometimes be frustrating to support I’m nonetheless very happy to see folks pushing this API forward. It’s still early days, after all.Handy has been updated to handle the joint referencing changes, and so on. But currently it does not support the joint orientation changes that the API has implemented—this means Handy is temporarily broken. The orientation changes are being addressed within Three.js itself: mrdoob/three.js#21712 Once these updates to Three are complete I’ll incorporate them into Handy and it should work again as intended 👍
The text was updated successfully, but these errors were encountered: