Surface hand meshes

[m-alkalbani]

We discussed the possibility of surfacing engine/platform agnostic skinned hand meshes from the WebXR Device API in our previous F2F (as part of the Hand Input Module).

This would make it easier for developers to get started with hand tracking experiences and adds more consistency in terms of visuals and performance across devices and browsers. Do we have this already? If I remember correctly there wasn't many challenges or objections in doing this but it would be great if we can revisit it and figure out next steps.

/facetoface

[Maksims]

Would that be provided in form of raw vertex/index buffers, so engines can interpret them into own rendering formats as required?

[cabanier]

The OpenXR API referenced in that session returns similar model files that are in the input profiles repository.
I'm unsure how that would make it easier for developers since its fairly easy to fetch data in a web browser.

[mkeblx]

One reference, on AndroidXR there is a an extension for getting a personalized hand mesh, which would be different than the input profiles model. It has some positives and potential negatives.

This extension is intended to provide vertex and index buffers for the mesh of a personalized representation of the user's hands.

https://developer.android.com/develop/xr/openxr/extensions/XR_ANDROID_hand_mesh

--
One additional (minor) use case, would be an installed PWA used offline, which would still be able to load hand models. (This could also be handled with caching the models, etc.)

[AdaRoseCannon]

/agenda sorry didn't get to it during the face to face