Welcome! Log In Create A New Profile

Advanced

Direct voxel input.

Posted by SteveBaker 
Direct voxel input.
June 02, 2018 10:56PM
I'm working on an application for people who 3D print models for tabletop gaming - and my tool works most naturally with a dense voxel grid internally...which I have to slowly-and-painfully convert into triangles using Marching Cubes and write out as an ungodly huge STL file at the end.

I'm betting that slic3r takes the ungodly large triangle mesh and slowly and painfully turns it back into voxels...right?

Would it be possible to come up with a simple Voxel file format to allow tools like mine to short-circuit this ridiculous loop?

A voxel file could be as simple as height/width/depth as unsigned long's and then one bit per voxel in a packed array...maybe you'd want to get complicated and have multiple layers for color and such...but that could be handled easily.

We could get fancy and use octree encoding - but that loses out on the simplicity we have with STL.

Any thoughts?
Re: Direct voxel input.
June 03, 2018 03:08AM
Imagine a cube with a horizontal hole in it. How would slicer know how to interpret the cloud of voxels?
Re: Direct voxel input.
June 03, 2018 11:41AM
Have you seen: [www.voxelizer.com]


Ultra MegaMax Dominator 3D printer: [drmrehorst.blogspot.com]
Sorry, only registered users may post in this forum.

Click here to login