Aligning with Webaverse on this

[madjin]

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

• App: Create animation factory webaverse/app#2533
• App: Create state machine for animations webaverse/app#2532
• Animations / Cleanup : Need to confirm list of used animations  webaverse/app#2524
• App: Avatar.js should be broken up to better separate concerns webaverse/app#2519
• Refactor avatar animation/rendering webaverse/app#2456
• Animation: Test System for Animation Blends webaverse/app#2547

I think studying and documenting Webaverse implementation for avatars, wearables, and animation interop is a good path

[madjin]

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

[madjin]

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

• Animation : Emote animations webaverse/app#2656
• Animations: pull out/put away webaverse/app#2638
• Animations: get pulled by hookshot webaverse/app#2627
• optimise sprite rendering webaverse/app#2619

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