MakerBot Print is our newest print-prepration software, which supports native CAD files and STL assemblies,
allows you to interact with all your printers via the Cloud, and many other exciting new features.

Download Now

Report as inappropriate

First off, congratulations Emmett on the beautiful design and ingenious blending of mathematics, engineering and art!

I did however have a question.

While working with the OpenSCAD source file, I think I spotted what appears to be a bug. At first I thought it to be a rendering issue on the part of OpenSCAD, but now I am finding the problem reflected in my prints. Specifically, it seems like a single-layer "slice" is dissecting or otherwise somehow missing around the top fifth of the model. It is visible both in the "petal2" module as well as the "lamp" module (if the line inside the for loop which generates the petal2's is commented out). Here are screenshots from OpenSCAD which highlight the issue:

petal2: http://bit.ly/1mmCxrc

lamp: http://bit.ly/1qiWKsM

And here is a photo of a print which begins to exhibit a degradation in output at the exact same location: http://bit.ly/1o9yIB3

For reference the print was performed using PLA, with the STL generated by OpenSCAD 2014.03 scaled down to 0.8 using Cura 14.07 on an Ultimaker 2. It seems as though a single layer is missing, and from that point on the printer is extruding one layer too high (instead of directly on top of the last layer). On this print the interior lamp portion itself actually failed and disintegrated at this same position.

The model seems to print okay at full scale on a MakerBot Replicator 2. But at a smaller scale where there is less material to support each subsequent layer the problem becomes more noticeable. I could see the same seam in the model appearing when rendered by Cura with the original STL downloaded from Thingiverse, so I don't believe it is unique to my build of OpenSCAD. Granted if there actually was a single layer missing OpenSCAD wouldn't be able to export the STL file, but I hope the description helps to clarify what I am seeing.

Is there any reason you can think of why this might be happening at this specific location, across multiple OpenSCAD modules?

Thanks again for this and your many wonderful efforts!