Hello from M3D!


@harryn the file that you sent caught us a bit off guard, as it contains thousands of single meshes. At the moment Voxelizer is not designed to handle this type of situations. But thanks to your input we will try to improve it to cover more cases like yours. Yes please send also the dae so that we can see that one as well. We didn’t do many tests on this format, so there are probably parts than can need to be fixed.
In the meantime please try with this model and tell me if everything works fine (no need to unpack it): Sample_Ship_OBJ.zip (1.4 MB)


Hi again.
I’ll send the other file when I get home.
Just trying the ship file and I can’t seem to make the colours fit to the final model

it opens with colour but it voxelises then has no colour. Adding the image and textures still doesn’t give me the full colour preview.
Had this same problem last night - what am I doing wrong? Something out of sequence perhaps? The online videos don’t seem to follow the experimental programme to well.
The programme at school, we sorted out; the programme couldn’t access the network so we set up a hot spot on the phone and connected via that and all well now.



This is the expected behavior as the default option is still single color printing.

To get the closest possible match between the colors of the texture and the colors that you can get from your printer you need to click on the ‘Find key colors’ button. You can click it multiple times to get different combinations. If you are not satisfied with a particular color choice of the software, you can edit it by clicking on the color box or by manually editing the filament ratios.

Maybe you are already aware of the problem, anyway keep in mind that it is not possible to achieve all the colors from only four filaments. If your key color (the fourth one) is white, for instance, getting black is just impossible. That’s why the color wheel that we show has empty areas in it.

When moving towards gcode generation and printing, remember to check which ‘Generation mode’ works best for your model. In the case of this ship, for example, I believe is ‘Segmentation’. From the last release notes:

  • Weaving (the default) gives the previously available functionality, interweaving multiple outlines to achieve desired colors. This gives good results on vertical surfaces but doesn’t affect horizontal ones.
  • Segmentation splits the object into multiple objects based on the colors. This works for all surfaces but has more computational complexity and may lead to longer printing times.
  • Complex attempts to use Weaving for vertical surfaces and Segmentation for horizontal ones


Thank you Agiachino, that will give me something to play with today. I’m hoping that M3D will come up with a 5 filament head sometime so we can have CYM + W + B and have better saturation and depth of colour.

A link to a file with obj, dae and fbx files of the same model from Daz3d for you to try



Hello again,
I’ve had fun playing with Voxelizer2 with new knowledge and I get the picture, colour has to be personally assigned to the parts of the print. What I was hoping for was that Voxeliser2 would take the mtl file and add it to the obj file in the correct places so that a fully coloured model as originally conceived was produced. I can’t seem to make that happen. I assume the XYZ da Vinci Color mini does apply the colour info file with the obj… to produce their prints. They look too complicated for that not to occur.


Hi @harryn
in order to correctly load a textured obj file, the .obj, the .mtl and the texture image have to be in the same folder (which can also be a zipped one).

You then need to apply an Internal texture material to it.

See the attached example.

colorCube.zip (46.7 KB)