Anata Call 11-22-22

hologram + m3/weba initial call

present: jin, arashi, hongzi

M3/Weba + Hologram team meeting taking place in
https://hyperfy.io/anata

12:30 pt on monday established as weekly m3 + holo meet time

Jin showing someone from hologram team

• various links
• dework, github, grant proposal, etc.

Jin: we want to sync everything

• demo'd all the json from all the tokens
• live TD (?) is a big file
• team released more organized files
  • hologram not sure if they have latest one
  • they have one updated 6 days ago
  • jin: the one that hounds shared

This drive link has image assets of traits:
https://drive.google.com/drive/folders/1VEbionHPVwBhj7GCJF7GWvTsUXZYW-I4

Jin: we have all traits here. turned them into github issues. we have some duplicates

Jin: wondering if we were to kind of figure out which traits overlap and which don't, that will help us prevent duplication of effort

• ex) some things are for both masc and fem models. like weapons – if we already have someone working on that, it overall helps to know so we don't have to re-make things twice over
• jin: order of operations. we should do planning. figure out and tag issues on the github as to which ones are both masc and fem and which one are gender specific
  • this is per trait
  • not designed for overall view yet, but could be

Jin: has anata setup in webaMMO dework. invited me (arashi) and others on the team to te dework space for it

• review of dework
  • looking at tasks, wanting to be able to make subtasks

Jin: clothing. ex) some are just fem. some are both fem and masc.

Hologram: clothes we can all share. body sizes are

• jin: clothes will be whole topic in itself
• jin: start with body and whatever we can do to re use traits that are provided

Jin: webaverse got started on some hats

• moved that to in progress
• jin wondering if we should label things on github more
• jin: we should share base meshes first. get that out of the way, take care of proportions

Hologram: right now just a list of traits shared by two genders, right? I was going to write a script to get all the traits. I can just do one for female one for male and one for shared

jin: wants arashi to see what is re useable

• ex) figma. katana's reused a lot
  • if someone works on just weapons then my rec is that they kind of work on things that are re useable

jin: lets post WIP screenshots somewhere. github is like – we can post in github issues under comments, WIP stuff. dework is also fine. i don tthink comments will send over tho

jin: best if we kept it to github

hologram: we have a google drive for art. every time when a model is generated, we usually just use discord – put screenshot, concept design, get live feedback. i guess right now if we do it, anata channel. we can do weekly aggregation

• jin: that would be cool. we can just meet up and have all screenshots ready to share and go over

hologram: if 1 week – after i share trait list. lets make sure shared traits we don't run into each other. we can – in the beginning of the week, we can say here is model list or trait list, then if we finish we can share with you and vice versa.

• jin: okay, cool. i like this identifying what we will tackle at the beginning of each week. i can prioritize things on the weba side that will really help us out

jin: notice anything else in collection that is worth noting?

• holo: some of actual appearance –
  • jin: tricky. tools we are planning to generate these. take in metadata from tokens. if metadata is pointing to things that don't look the same… i think we should use the metadata as source of truth for first iteration, get thru traits, then we can solve for derivatives of each trait
    • holo: this makes sense. mark as we go
    • holo: do you guys have an assembly pipeline? traits first then model assembly… is that the plan?
      • jin: yes. unity pipeline for this. and blender. they both work the same way. basically set it up in hierarchy and you can import your json and do all the attachments and then rig and create previews
        • holo: this is helpful

holo: we have blender pipeline. each model is pretty much 1:1 tho. i would say for the first few models, few dozen – on our end, we are doing manual assembly. one is to understand complexity better. two… not that many traits shared among models. not great for time saving. a lot of manual assembly

• jin: that makes sense, this is the right way to go about it. kinda forced to do this manually, take good notes on things we might have to deal with later

holo: one other thing about weapon. i think anata team wants weapons to be equipable. like you can press E and use the weapon. i dont know how to do this. do you hae standard for this?

• jin: there is a way of doing that which is pretty easy. i've got a bunch of repos here as to examples like – here's a sword for example. metaverse file. its just a bunch of json describing for example an attachment point and the offset to such and key values as to animations
  • holo: got it, this is cool
  • jin: for testing, we could literally drag and drop the folder into webaverse and it will automatically be there to pick up and test with

holo: no special treatment on artist side?

• jin: no i think when we are ready for the final deployment, they would be exported kind of at the orgin point rather than attached to the character so it can be picked up and whatnot

holo: we will… (inaudible). later on it wont be separate object. we could have a way to detach and save as separate model

• jin: can imagine them as separate NFTs in a way. like unbundled loot

jin: ya'll doin fem or masc?

• holo: we are doing females now
  • jin: okay cool. alrighty well, we can focus on masc… i think that's all we need to cover for now.