Morphs creation (Copy/Move/Delete/Rename/Backup morphs tool done)

[TetoTheSquirrelFox]

So, I try to help by making tools to create like morphs (or muscle if I can figure how it works).

But I had to answer few questions first :

• What is the scope ?
• When can the user create morphs ?
• Where are tools on the panel, are they available all the time ?
• When can we lunch ?

So what I think about that:

• To be able to create good morphs that can be used everywhere, user must starts with the basic shape of one of the 4 big types available in MB-Lab : male, female, anime male, anime female. So, to start with something, I created a “Base female f_NO01” (file characters_config.json) that has no phenotype, no race, and is the base model that used Manuel.
• I also gave to this model a basic albedo.png that looks like clay. Not very good, but well...
• Then I gave it no morphs, no phenotype, nothing. So it’s the most basic model we can have.
• I also created dedicated directory for this type (\data\presets\none_female_base) with no file.
• For me it’s the model user must use to make his own morphs for all female models (realistic female here)

You can see the content in characters_config here:
"f_no01": {
"description": "Generate a base female character for creating morphs",
"template_model": "MBLab_human_female",
"name": "f_no01",
"label": "Base female (F_NO01) (AGPL3)",
...
"texture_sclera_mask" : "sclera_mask.png",
"morphs_extra_file": "",
"shared_morphs_file": "",
"shared_morphs_extra_file": "",
"bounding_boxes_file": "human_female_bbox.json",
...
"vertexgroup_base_file": "human_female_vgroups_base.json",
"vertexgroup_muscle_file": "human_female_vgroups_muscles.json"
}

Problem is that some morphs could be very specific to a race or a phenotype, and could not work properly in all models for a reason. So I decided that user could use the model he wants, and create his own morphs while other morphs are already used. To assure that, I put the “morphs editor” in the Pre-Finalized State session (gui_status == "ACTIVE_SESSION") and put it between “random generator” and “measures”. So, for the user who chooses “F_NO01” he can create, and for the others he can use other morphs as well.

So, as MB_Lab is not designed to create bodies from scratch, but more to use what it is available, I tried to be as simple as possible, while let the user to have the most useful tool to create new morphs.

So now here are the problems I’m facing :

• Let’s take the model f_ca01 in characters_config.json. Few lines are dedicated to the morphs.
  "name": "f_ca01",
  "morphs_extra_file": "",
  "shared_morphs_file": "human_female_morphs.json",
  "shared_morphs_extra_file": "human_female_morphs_extra.json",
• shared_morphs_file & shared_morphs_extra_file are basic morphs shared by all phenotype from female Caucasian. (extra_files is for fantasy, basically). Here it’s simple, all females share the same files. But it could be something else.
• f_ca01 allows to use morphs that are dedicated to the type (female Caucasian) and the files need to be in the proper format for its name: “f_ca01_whatever_optionalWhatever.json”
• More important: under those files, a same morph is split in two, for minimum values and maximum. Each morph end with _min or _max, so the engine can construct the final morph, from 0 to 1 (0,5 is the model before morphing).
• morphs_extra_file: I think that the intent was to allow user morphs shared buy a whole type?
• So under the directory \data\morphs you have 2 types of files, the ones who are dedicated to a whole range of human (male, female, anime male, anime female) and the others dedicated to types, and it seems that we can add all files we want if they are properly named.

At first, the tool would have looked like this (on the panel):

• Create base model → copy all vertex from actual model shown, whatever it is.
• Load base model → Load an old model.
• Load work-in-progress → Load a model for a morph in progress.
• Reset models → reload work-in-progress model.
• Morph type → a list where we can choose if the morph will be for one type in particular or for a whole range.
• Body type → Male or female.
• Type name → (for example) an02
• Type name extra → none or a name like the pseudo of the author.
• Morph name → A name for the morph.
• Min or Max → the target morph is for min values or max.
• Save work-in-progress → Save all actual model as a work-in-progress.
• Quick save → No dialog, take the name, add _min or _max, and _000 (or _001, _002, …) and save the morph, aka the vertices that are their location changed.
• Save final morph: Same thing, but we have to choose min and max files, and the file is properly saved in the dedicated directory.

But, first I wanted to have my own models, copies of the ones used by the engine, but after a while I started to think that it was not good. The engine is complex, and I should keep a coherence with it. The model the user is working on is linked to the engine, so let’s keep it that way. And the engine has already many useful tools like reset, loading, saving…
So, if the user wants making morphs from base model, no problem, he can use the “reset character” button. If he wants to create while character already has morphs applied, he can use ‘import/export character”.

So now the tool looks like this :

• Morph type → a list where we can choose if the morph will be for one type in particular or for a whole range.
• Body type → Male or female.
• Type name → (for example) an02
• Type name extra → none or a name like the pseudo of the author.
• Morph name → A name for the morph.
• Min or Max → the target morph is for min values or max.
• Load work-in-progress → Load a model for a morph in progress.
• Save work in progress→ No dialog, take the name, add _min or _max, and _000 (or _001, _002, …) and save the morph, aka the vertices that are their location changed.
• Save final morph: Same thing, but we have to choose min and max files, and the file is properly saved in the dedicated directory.

The workflow would look like this :

• I choose for what type the morph is for. → Type name = as01
• Morphs are already existing for the model, so I write my pseudo for save files → Type name extra = Teto
• Morph is for this model → Morph type = dedicated
• For female → Body type = female
• I’m sculpting for min values → Min or Max = min.
• I do my stuff → Save work-in-progress 4 or 5 times.
• It’s done, same thing for Max values.
• It’s done. Save the morph. The file name is automatic, I just have to choose the proper file for min and max values. The file is saved in the dedicated directory. If the file already exists, the morph is added in the file. If the name of the morph already exists, the new one replaces the old one.

I’m working on it now, and if you agree, I’d like to make a morph.py dedicated for this, so the changes in other .py files would be minimal. I’d like to talk about the work in progress here too.

[animate1978]

Quite impressive! I will have to read this over again as I only read through it once but so far what I see I like.

Of course making a new morph Python script would be ideal.

We can make this a project for the next version perhaps?

[TetoTheSquirrelFox]

Thanks. ^^

About a new project, why not, but I'd like to be sure that what I'm doing goes somewhere. For now I'll change the existing python files to "prepare" the creation tools, and will post the changes here.

[TetoTheSquirrelFox]

Now, first thing to do is to store a copy of the body (all vertices to be more specific) because after sculpting the morph, I need to compare with a base, and as the actual body has changed, I need an untouched body to compare with.

But I can't write body_as_a_base = actual_body, I suppose, and I must something like body_as_a_base = actual_body.duplicate() and make a real copy, not an instance. I'll on this tomorrow. And I think that will help me for comparing 2 body objects.

By the way, about the classes I'm modifying : the changed code is always between
#Teto
and
#End Teto
So when it will be done, I will be able to send the files to you and it will be easy (I guess) to change the files in master. Please tell me if I'm wrong.

[Noizirom]

I'm not sure, but you might want to make a bmesh copy to sculpt, then bake it back to the original mesh. I do think that you can obtain the un_modified coordinates the same way you access the "current" coordinates, but I've never actually used those.

…

On Mon, Jan 13, 2020, 3:43 PM TetoTheSquirrelFox ***@***.***> wrote: [image: image] <https://user-images.githubusercontent.com/59537161/72289918-6cdc1b00-364c-11ea-80cd-6db8925675e0.png> Now, first thing to do is to store a copy of the body (all vertices to be more specific) because after sculpting the morph, I need to compare with a base, and as the actual body has changed, I need an untouched body to compare with. But I can't write body_as_a_base = actual_body, I suppose, and I must something like body_as_a_base = actual_body.duplicate() and make a real copy, not an instance. I'll on this tomorrow. And I think that will help me for comparing 2 body objects. By the way, about the classes I'm modifying : the changed code is always between #Teto and #End Teto So when it will be done, I will be able to send the files to you and it will be easy (I guess) to change the files in master. Please tell me if I'm wrong. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#226?email_source=notifications&email_token=AKYHC3XRPNKH7TUN4GVU4MTQ5TG63A5CNFSM4KFX5YB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI2G24Q#issuecomment-573861234>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKYHC3UFGXVKB2TBDEANNQLQ5TG63ANCNFSM4KFX5YBQ> .

[TetoTheSquirrelFox]

No no, it's waaaaay simpler than that. ^^
Actually I want to make a copy of the vertices of the shown model. And a python program already exists for this (it writes in a file, I just want to make a special object that stores the vertices).
After that, user does his thing with Blender sculpt tools (without touching the number/name/id of vertices of course).
And at the end the tool checks just the differences between the base and the sculpted, then write them in a json file in order to be a regular morph.

So no, I don't "touch" anything in the model, I just check the differences between 2 states of a same model that is entirely handled by the engine (which is complex, like, really complex).

[Noizirom]

A file called co_to_js.py will put vertices of a selected object into a .json file. https://github.com/Noizirom/Blender-Python-Tool

…

On Wed, Jan 15, 2020, 2:26 PM TetoTheSquirrelFox ***@***.***> wrote: No no, it's waaaaay simpler than that. ^^ Actually I want to make a copy of the vertices of the shown model. And a python program already exists for this (it writes in a file, I just want to make a special object that stores the vertices). After that, user does his thing with Blender sculpt tools (without touching the number/name/id of vertices of course). And at the end the tool checks just the differences between the base and the sculpted, then write them in a json file in order to be a regular morph. So no, I don't "touch" anything in the model, I just check the differences between 2 states of a same model that is entirely handled by the engine (which is complex, like, really complex). — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#226?email_source=notifications&email_token=AKYHC3UUCKPIWAQQWLWM64TQ55PNDA5CNFSM4KFX5YB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJBQEBA#issuecomment-574816772>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKYHC3RET2UVD2APDZ6UUITQ55PNDANCNFSM4KFX5YBQ> .

[Noizirom]

I'm not quite sure what your asking , being that you've already found an addon for this.

…

On Wed, Jan 15, 2020, 6:37 PM Zion Hill Hill ***@***.***> wrote: A file called co_to_js.py will put vertices of a selected object into a .json file. https://github.com/Noizirom/Blender-Python-Tool On Wed, Jan 15, 2020, 2:26 PM TetoTheSquirrelFox ***@***.***> wrote: > No no, it's waaaaay simpler than that. ^^ > Actually I want to make a copy of the vertices of the shown model. And a > python program already exists for this (it writes in a file, I just want to > make a special object that stores the vertices). > After that, user does his thing with Blender sculpt tools (without > touching the number/name/id of vertices of course). > And at the end the tool checks just the differences between the base and > the sculpted, then write them in a json file in order to be a regular morph. > > So no, I don't "touch" anything in the model, I just check the > differences between 2 states of a same model that is entirely handled by > the engine (which is complex, like, really complex). > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#226?email_source=notifications&email_token=AKYHC3UUCKPIWAQQWLWM64TQ55PNDA5CNFSM4KFX5YB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJBQEBA#issuecomment-574816772>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AKYHC3RET2UVD2APDZ6UUITQ55PNDANCNFSM4KFX5YBQ> > . >

[TetoTheSquirrelFox]

Nope, it's this file.

[TetoTheSquirrelFox]

Quick update :

Now the UI is done. I think that if the thing is finished, I will have to change things here and there, but for now I need something working for users.

[TetoTheSquirrelFox]

Great great news today ! ^^

I copied the great co_to_js.py int the class that is executed when user clicks on button "Store actual body vertices". I had to change things because python is handled differently when used in console and inside the plugin. So after changed every line because of this ^^, I did this :

• I stored in a file the body shown on screen, after have created it.
• on "Edit mode", I changed 1 vertex (somewhere on the arm) with mirror enabled, so the other arm changed accordingly.
• Store the body again.
• So now I have 2 .json files, that I open with Notepad++
• I compare them (it's easy, Notepad++ has a module made for)
  And voilà ! Only 2 vertices changed in the file :
  
  
  The colors are ugly but that's not the point. On left, base body.

I was worried before the try, because I feared that the data stored by MB-Lab were not the data used by Blender. So if I changed something in the body (by using sculpt tools for example), the changes would not be "seen" in MB-Lab objects. I don't know if I'm clear. Anyway, it's not the case, that is good for me.

So, now I know that it works, animate1978, the thing can be a project now ?
Anyway, I have a lot of work to do.

• First, be able to do the comparison in the engine, not very difficult I think, I know how to do this, I just have to collect the index of each changed vertex, and do a subtraction "new - old" and store the result in a json file.
• This way, the tool would be barely usable for users.
• And then I'd work to make the tool really useful, like allow to write many morphs in one file, manage directories for users morphs, and to the stuff written above.

Stay tuned !
Teto.

[TetoTheSquirrelFox]

It's working !
So what I did today : having a full comparison between 2 lists of vertices, with index, in order to be saved.
I took one character, stored its vertices. Disabled smoothing.

Went to Edit mode, changed 1 vertex (2, because symmetric edition)

Asked for the result and voilà !

Not sure yet, but I think that the indexes are good.
Now it's not over. What I have to do

• Seems that when I reset the character, and try again, Blender doesn't like at all. But doing things, store, doing other things, store, and so on, then finalize the differences works well.
• I have to save it in a file, with proper name. Manuel didn't reinvent the wheel, and uses strictly json library for that purpose, so it seems I just have to make a dictionary with keys (the name of the morph) and values (the changes) to write a file in the good format. I'm on it.

[TetoTheSquirrelFox]

Now I'm almost there.

As you can see, the UI changed a lot, and many parts of the name or the morphs can't be changed because they are dependent of the model.

The only thing that I have to do is to put data in an opened json, add or replace morphs, and save it. For the moment, if a morph already exists, it is replaced. Everything else seems to work.