Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Materials are difficult to navigate #15

Open
RichysHub opened this issue Oct 17, 2019 · 1 comment
Open

Materials are difficult to navigate #15

RichysHub opened this issue Oct 17, 2019 · 1 comment

Comments

@RichysHub
Copy link
Owner

All materials are imported with uninspiring names.

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

@RichysHub RichysHub mentioned this issue Oct 17, 2019
@wizardgsz
Copy link
Contributor

wizardgsz commented Oct 17, 2019

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants