1

Topic: Problems with Slic3r on certain models

I recently got my Solidoodle 2, and I have been noticing that sometimes when I go to slice a model it ends up looking (in the Gcode editor window) like the printer is only going to print random sparse areas of the model, leaving huge open areas in between. An example is a model I recently got from Thingiverse ( . In the object placement preview screen, it looks just fine, but when I go to slice it, it ends up all messed up. Ive tried messing with the settings in Slic3r, but nothing seems to help.

Any insights would be appreciated.

Post's attachments

Screenshot (1).png
Screenshot (1).png 207.24 kb, file has never been downloaded. 

Screenshot (2).png
Screenshot (2).png 426.81 kb, file has never been downloaded. 

You don't have the permssions to download the attachments of this post.

2

Re: Problems with Slic3r on certain models

What version of RH and slic3r?  This is usually because the model is not manifold, but I've noticed that the newer versions of RH and slic3r have done some weird things to my models that have sliced fine in the past...

3

Re: Problems with Slic3r on certain models

Repetier-Host is Version 0.85b, and my Slic3r is version 0.9.9

4

Re: Problems with Slic3r on certain models

Upload the models to cloud.netfabb.com to fix them.

5

Re: Problems with Slic3r on certain models

I had the same problem, updated RH and Sli3er to the latest versions and still had issues. Netfabb helped on some, but larger models seemed to still crash Sli3er.
Solution I found was to download Kisslicer, and use that for tougher models.

6

Re: Problems with Slic3r on certain models

Thanks, netfabb worked perfectly!

7

Re: Problems with Slic3r on certain models

One of the biggest thing with Slic3er and how much memory it takes and how likely it is to crash is the number of threads you tell it to use.

From memory the default is 4... but if you are doing a large STL file, you need to drop this to 2 or even 1 to reduce the memory and processor Slic3r tries to use for slicing alone.

Configure->Advanced->Threads .

The other thing in newer versions, is specifying the smallest resolution. Setting this to 0.1mm or 0.05mm makes slic3r do a simplification before it slices, discarding polygons that are below the printable resolution anyway (and therefore, irrelevant).

But changing the threads to 1 or 2 is the biggest impact in terms of making Slic3r more stable for large STLs - with the slight trade off of longer slicing times. Its covered to great extent in Slic3rs Readme/Help files .