Total fail :D

i just went angry for this - over 3 hours of printing + 20m of material , i bet that i just have something wrong with the settings or??? anyone can help?
check this picture please .

When you loaded your stl did you notice an issue with Normals or Manifold? Did you look at the result after slicing?

no , i didn’t check the code … it happen first time … you think that there is problem or some bug in the stl file , or slicer?

so i try to load it again , the result is different, in object placement as you saw on first picture and G -code editor is like this … so what’s wrong now , the slicer or stl.file ?:smiley: i gonna try to convert it
again from sketch up to stl.

so i just did it , converted again the sketch up file to stl. and here is the result

so guys ,keep checking the G-code editor …

The stl looks bad to me. Have you checked the Normals and Manifold? If you don’t know what I am talking about you could post the file.

In Sketchup .stl files are usually poorly converted.
Try to use the Netfab cloud Service to clean them ( But don’t expect miracles.

It’s the slicer, the recommend software fails on at least half of the models on thingiverse. I now use Cura and it works perfect. You can still use the recommended software to send the G code.

Hi RichardUK,

I disagree. Many models on thingiverse have poor data with lots of errors in them. To attribute subsequent problems to the application used for further handling of such data thus seems unfounded.
If your slicing software of choice can handle stl errors, that’s great. However, I’m not sure whether that can possibly work for all the various kinds of errors found in stl files, so doublechecking the G-code for critical (i.e. flawed) objects might be a good idea, independent of which slicer is used.


The only way to figure this out is to load the stl into (you pick your editor) and check it out. I guess there are also validators out there too, but the idea is the same. You need to ensure that you have a valid stl before blaming the slicer.