Aligning with Webaverse on this
Closed this issue · 2 comments
When working on avatar interop problems I always circle back to Webaverse solving the hard parts
Here's a handful of recent and related issues being worked on the main app
- webaverse/app#2533
- webaverse/app#2532
- webaverse/app#2524
- webaverse/app#2519
- webaverse/app#2456
- webaverse/app#2547
I think studying and documenting Webaverse implementation for avatars, wearables, and animation interop is a good path
The blender gltf exporter now has support for exporting animation only glTF files:
KhronosGroup/glTF-Blender-IO#1582
Source: omigroup/gltf-extensions#44
Related article: https://www.polygonalmind.com/blog-posts/export-a-gltfglb-with-several-animations
more recent open source case studies avatar interop group can study
perhaps we can do a show segment about how engineers thinks about solving any of them?
compatibility and extensibility are details that are very often taken into consideration early in the project
or maybe we can go through closed issues of open source projects related to avatar interop?
content by makers for makers / how it's made would be interesting for the audience that is 1% making stuff for the 99% rest