Wearables documentation

[madjin]

We can use this open source character creator program to help document parts about the layering system, there are a good handful of open bounties for helping with such too: https://github.com/webaverse-studios/CharacterCreator

There's also many dresser prefabs / apps worth looking into on booth.pm, an indie marketplace many avatar creators use, such as Auto Dresser: https://booth.pm/ja/items/1300847

• Define logic for the wearables system (dress up, dress down, and replace options)
• Additional skeleton for accessories (e.g. scarf, handbag)
• Proposals of format specifications particular for wearables in cooperation with other groups studying 3D interoperability (for example, FBX preferred for skeletal mesh, glTF/USD for metaverse)
• Develop a layering/category system for interchangeable wearables (changing parts of outfit) (Headgear, UpperWear, BottomWear, FullBody, Flat Footwear & Heeled Footwear)
• Develop a tier/category system that groups the different metaverses based on similar characteristics. ie. mesh count, poly count, material count, etc.
• Smart wearables containing music, effects, animations, interactivity. (Examples: a wrist watch that you can use to navigate. Headphones that play music when worn.)
• Look into possible extensions of gltf/usd for describing wearables

[madjin]

Case Study: Voxels Costumer

Voxels has a wearables / layering system with JSON export that would be useful to investigate for interop purposes, basically works by parenting / offsetting the assets to bones.

JSON: https://gist.github.com/madjin/bc8ee04f228d1bf43f60ac9f98155720

Dataset: vox -> glTF

• Blog post: https://mirror.xyz/openvoxels.eth/MVy5cs90cH5ae8GNha1goMQHqFAFOKbzVSHCV_fu5jI
• Snapshot of wearables exported 11-1-22 in vox, svox, and glb formats: https://github.com/M3-org/cryptovoxels-wearables

Converted from proprietary format (.vox) to svox to glTF then encoded the metadata about each wearable into the glTF file itself using glTF-Metadata-CLI

Challenges

Challenge: Different rigs / armature bone names, how will user + wearable know offset if name is different?

We can then test Voxel wearables on other avatars (currently not possible in Voxels but platform open to it)

Metadata

See the finished script here: https://github.com/M3-org/cryptovoxels-wearables/blob/main/scripts/convert_json.sh

Interesting case study via Webaverse: https://hackmd.io/@platote/ryik4slc9#6-Adding-a-hat

[madjin]

Develop a tier/category system that groups the different metaverses based on similar characteristics. ie. mesh count, poly count, material count, etc.

VRChat offers good guidelines for avatar performance: https://docs.vrchat.com/docs/avatar-performance-ranking-system#quest-limits

It's influenced Hyperfy's avatar performance guidelines: https://docs.hyperfy.io/avatars#rank-system

[madjin]

Notes on layering system: https://github.com/gm3/boom-tools/wiki/API-Reference