RichysHub/MagicaVoxel-VOX-importer

Materials are difficult to navigate

Opened this issue · 1 comments

All materials are imported with uninspiring names.

This issue is to discuss how we could approach this, giving unique, meaningful names to imported materials.

Materials, and objects as well...

About objects.

As-is:

  • we are creating a "collection" for each imported .vox file linking each voxel/cube to it
  • collection name = the filename
  • object names = "Cube.###" using a sequence number (it is automatically handled by Blender)
  • when join_voxels is True, we could set the name of the single object as the collection itself

It could be (I mean implementing scene-graph i.e. a set of "models"):

  • collection name as-is
  • use the "model" name read in nSHP chunk (for example "model name" + "Cube.###", or just "model name" without "Cube") BUT in MagicaVoxels names are not unique (we could add the node-ID read in the chunk)
  • when joining voxels to single object, we could just use the "model name" in nSHP (and its node-ID as supposed before)

About materials.

  • display the material type in names (emit, metal, glass...)?
  • "link" material name to object ones?