RichysHub

I've been thinking about how to reorganise the importer, such that this structure is easier to manage. Principly that the structure would be parsed into Python objects that resemble the...

Apologies for the delayed response. I didn't know about the format change, so thank you for bringing that to my attention. Current solution would be as @atomhax suggests; using an...

Fantastic work so far 👏 I have updated issue title.

Oh wow. That's some great detective work. I'm happy for all that detail to be skipped, though I suppose there is the possibility of including them in the future. The...

Absolutely, I don't think they should be a priority in any sense. More that it's just cool to know that we **could** import them, should we ever deem that a...

That linked page is quite dated. Python 3.7 (which Blender 2.80 uses) added an additional argument to `namedtuple`, specifically to handle default arguments. https://docs.python.org/3.7/library/collections.html#collections.namedtuple ``` material_spec = namedtuple('material_spec', [ #...

Hmm. Honestly, it might just be easier to use a bare dictionary, and forgo the namedtuple plan altogether. For all the work that's going in to work **around** namedtuple, is...

I'm not 100% sure I understand the behaviour you're suggesting. - Are you thinking it would be good to support importing a `.vox`, but have the result be solely the...

Perhaps my views are best explained if I give a little background to this repository, and why it was made. October of 2017 I was playing around with making voxel...

Hmm, I wonder if there is a common way of handling the origin of imported models. If the other import options all import it relative to (0, 0, 0), or...