search

Sigmmma / Blendkrieg

Halo Model importer and exporter for Blender.
GNU General Public License v3.0
11 stars 3 forks source link

Have the importer use our naming and hierarchy scheme for Halo models. #8

Open ShellyHerself opened 5 years ago

ShellyHerself commented 5 years ago

Name regions, permutations, etc... following this idea.

halo_obj:<name>              ex: halo_obj:cyborg
│   └──node:<name>           ex: node:frame pelvis
└────region:<name>           ex: region:body
      ├───permutation:<name> ex: permutation:__base
      └───perm:<name>        ex: permutation:__base

These should be allowed on collections, and for objects. Collections in case of where multiple scene objects need to be part of the region (for instance). Lone parts can have their region specification in their name. But the importer should (in my eyes) always use the collections.

MosesofEgypt commented 5 years ago

I'm assuming in node:frame pelvis you are specifying that the object is a node with the node: part, and everything after it is considered part of the exported node name? Does this mean that someone would have to prefix node: to all their nodes or else the exporter won't detect them as nodes?

Would it also be safe to scan the scene for anything prefixed with halo_model: and assume it is intended to be a fully realized halo model with a skeleton, permutations, and regions?

ShellyHerself commented 5 years ago

The existing workflow for 3ds Max already dictates that you need a 'frame' and link your model to it.

I think naming your object halo_model:name or having it be in a collection named halo_model:name wouldn't be too much of a problem for the user, while at the same time making the exporting process more foolproof and standardized.

Maybe it wouldn't have to be the full halo_model: and could also be left to just halo_model.

We'll get to parsing this data when we start work on the exporters.