M3 Anata 11-14-22 Call Notes

Anata hyperfy world
https://hyperfy.io/anata

• initialization of a war room for this project

Jin, Ahad, GuiltyRegicide, Arashi present

High Level

50/50 in milestones based on –

• half up front half later

• and another team

• hologram … havent made group chat yet

  • they will take masc or fem; we (m3) will take the other
  • jin dont really care which one but leaning fem

• the hyperfy world for it linked above is like our war base for this

  • help visualize
  • help plan
  • etc

• blender and unity methods for assembling

• jin put a Figma in the world (can click to open)

  • traits listed
    • we want to go in order of whatever we have that's the most re-useable right now
    • jin has live 2d files
    • downloaded all zips for live 2d files
      • this gives us layers to get clothings, sigils – hair is something vroid studio will be fastest in, can draw / paint hair

• ahad wants to know if we have to model stuff ourselves

  • jin says maybe

• weba mmo multi sig potentially to be used for anata funds

• ahad: propose to me in terms of the payment then we can shake hands. is multi sig 2 / 3? (yes)

  • ahad wants to add himself and make it 3/4 for signing
  • jin arashi npec ahad as signers
  • this is fair, 2 ppl on each side
  • jin: lmk addr to add for signing

• ahad: what is timeline

  • jin: 6 months ish
  • ahad: target 3 to 4 months. do some expectations management
    • i was in a lot of background converstaion to help get this grant

• ahad: will get some reasonable expectations set for timeline

  • by the end of 4 months we need at least 1 iteration of everything done

• ahad asking guilty to the conversation

• ahad: lets establish workflow

  • which traits first
  • thinks guilty and jin should establish this workflow

• jin: we really need PSD files

  • noticing some of the data is not accurate
  • anata #'s not returning the right things? ex) anata # XXXX is not matching up with actual anata XXXX

• jin: 2000 total VRMs. we're doing half

• guilty: first thoughts:

  • ahad: wants guilty to look at everything, scope it out, come up with a high level ballpark. what do we need to do it in 3 to 4 months with minimal workload on you. wants guilty focused on high level management and not bogged down in trenches of small details
  • ahad: establish quality and style. then you get the team who can do it and execute without you doing too much grunt work

• guilty: what is end product

  • jin: create traits, put them into program, generate VRMs from it. blender + unity tools to do that
  • jin: we start with bases. get as many bases for either masc or fem. start with whatever is re useable from 2d files first.
  • jin: live 2d reuseable – find a way to crawl all this metadata and generate a way for us to make checklists to effectively project manage
  • jin: noticed tech wings. a lot of wings are simple recolors. things like this would be nice to prioritize first
  • jin: absorb all of what they have on their opensea page. check collection out, see what comes to mind
  • jin: chatting with hologram team to share notes good idea

• guilty: this will need every trick in the book (looking at the collection)

• jin: look at similarity of oni masks. things like that will be helpful.

• guilty: never been more thankful about nft collections re using collections than right now

  • this is going to be a shit ton of work

• jin: imo we can go off jsut metadata. for alpha release, we create festival mask oni. and that's it. iterate in version 2

• guilty: we are on the right track here. a crucial step is: how many unique assets are needed for the MVP?

  • having this information will help us formulate the approach / plan

• jin: wants to base things off metadata. this is how generator will work. adding additional metadata will complicate things

  • jin thinks sigils will be made easy cause we already have transparent png for them
    • can imagine them as emote
    • or in animated previews
    • guilty: single plane just kind of behind them

• guilty: sigils seem like low hanging fruit

• jin: models or base meshes, doesnt matter where we start. if artists are good at certain things let them run with it, let them. we need to create base first and make sure our base and hologram base has enough similarity to work together

• guilty: do they have different eye shapes? or are they they same

  • not sure but good question (jin). they all look similar

• guilty: 3 main areas of meat

  • hair
  • clothing
  • props

• jin: weapons will be fun and easy. about 145 weapons

• guilty: do we have access to talk to hologram artists

  • ahad: they dont have 3d artist
  • guilty: maybe talk to creator of anata collection traits? seeing patterns of repeating elements but then renamed as a separate thing. perhaps they could help with that
  • jin: they are trying to find the PSD files from the artist. we should ping them again on that. can also talk to artist
  • jin: first i want to see PSD files and layers they are using. this would tell us a lot

• jin: weapons shared amongst male and female

• jin: just by traits, we're looking at – shit they have a lot of hair – and a lot of clothes.

• iteration 1 should focus on attachments and rigging

• guilty: if we're doing this in wave, 1st wave def be actual model stuff. then we can work on auxillary things like props and effects later

• jin: 998 that each team will do

• jin: if we add up all the traits, we can add up how much work gets split according to that

• jin: meat of this is the clothing. look at all the variations in clothing and sex specific clothing

• jin: good to go thru everything and to see what assets are shared between masc and fem so that we know we have to comm with hologram on such

  • ex) plug suit wetwork trait seems to be applicable to both sexes

• jin other high level things to note

• ahad jumping off call: wants guilty to keep high level view of this and delegate; reiterates to guilty to not get stuck in details and particulars. have someone else manage on lower granular level and manage this at a higher level

• jin: other than this war room i have a hackmd book going on anata here: https://hackmd.io/@XR/anata

  • also created github with all json and live 2d links

• guilty: so we're building this generator. a crucial tool that might need to be created is gonna be – do we have an auto vrm exporter?

  • jin: yes
  • guilty: great

• guilty: what about hair physics?

  • jin: if you can export separately from vroid studio hair with bones … i think yes we will. its a bit tricky … you would want to do that after generation / rigging
  • hair kind of intermediate step after rigging and weighting

• guilty: vrm does support its own version of hair physics bones. it might be something to look at

  • jin: yeah spring bones are great
  • guilty: internal weba character creator: we're doing it in code where separate hair armature will be attached with each individual hair. then it all exports into the end result. not sure if we want to do something similar
    • jin: an artist who has a wacom tablet and vroid studio will be able to do hair no problem

• vroid studio: "combined hair mesh" if you uncheck this the hair becomes separate? should be able to export separate hair with bones and weights?

• guilty: what about importing models into vroid?

  • jin: not happening unless we make it a vroid
  • would need to make all bases in vroid

• guilty: if we are hiring artists, we could potentially have them make custom base (? not really sure what he means)

  • jin: we could but what is the benefit?

• guilty: with this large of a project, the timeline is crazy tight

  • jin: i mentioned that but its all good. im sure as we post progress the community will value quality over something that is rushed
    • guilty: that is hopefully and correct, hopefully will prove true

• guilty: i have a grasp on this. i need time to ruminate. let it digest and process

• jin: wants to find a way to quickly populate a checklist

  • oniforce repo. i have some basic guidlines
  • checklist for everything. works good in github issue.

• jin: taking traits and creating tasks for each category, similar to oniforce. also made it made convenient cause you can click task to go straight into ref art. really increases its project management usefulness

• jin: will figure out how much the split will be. gonna do a bit of data mining and organizing.

• arashi will start finding assets that will give us a long chain of re-useability

  • screenshot a lot of stuff
  • ex) weapons. a lot of katan's. a few variations of katans – ho wmany of these katan traits are gonna be useful then?

• jin: anything you (arashi) notice paste it in figma and coordinate there. dont wanna spam ahad and guilty cause they busy af