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
A pack is just a simple text file with a .pack file extension that is a list of URLs, on per line, pointing to avatar or scene URLs on any existing hub on the web.
I imagine serving directing through Github as raw file might not be feasible though and more importantly that the rigging might not be compatible.
The text was updated successfully, but these errors were encountered:
We could write a script that reads the json file and generate a pack file, how to create the jsdelivr url is explained in the README in this repo. That's the easy part.
Hubs avatars system doesn't use the same skeleton so you will have no animations on the avatar for sure without a custom modification of the hubs client.
I just tested uploading a glb in a hubs instance, hubs didn't configure the meshopt decoder, so you would need a change for that in hubs client as well.
The hubs ik-controller component is using LeftEye, RightEye, Head, Neck, LeftHand, RightHand, Spine bone names, that's actually the same name as in the mixamo skeleton, so some movement of the avatar may work, but probably will be weird.
For a more heavy customization that play specific animation inside the glb, you can look at Hubs-Foundation/hubs#6428 but in my glitch example we use external fbx animation files, not animation embedded in the avatar glb.
For a bitECS implementation I have no idea.
I'm thinking of https://hubs.mozilla.com/docs/hubs-cloud-asset-packs.html which says
I imagine serving directing through Github as raw file might not be feasible though and more importantly that the rigging might not be compatible.
The text was updated successfully, but these errors were encountered: