<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[SoliForum - 3D Printing Community — Problems with Slic3r on certain models]]></title>
		<link>https://www.soliforum.com/topic/3335/problems-with-slic3r-on-certain-models/</link>
		<atom:link href="https://www.soliforum.com/feed/rss/topic/3335/" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Problems with Slic3r on certain models.]]></description>
		<lastBuildDate>Sun, 28 Jul 2013 03:38:31 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Problems with Slic3r on certain models]]></title>
			<link>https://www.soliforum.com/post/31189/#p31189</link>
			<description><![CDATA[<p>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.</p><p>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. </p><p>Configure-&gt;Advanced-&gt;Threads . </p><p>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). </p><p>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 .</p>]]></description>
			<author><![CDATA[null@example.com (adrian)]]></author>
			<pubDate>Sun, 28 Jul 2013 03:38:31 +0000</pubDate>
			<guid>https://www.soliforum.com/post/31189/#p31189</guid>
		</item>
		<item>
			<title><![CDATA[Re: Problems with Slic3r on certain models]]></title>
			<link>https://www.soliforum.com/post/31188/#p31188</link>
			<description><![CDATA[<p>Thanks, netfabb worked perfectly!</p>]]></description>
			<author><![CDATA[null@example.com (vong888)]]></author>
			<pubDate>Sun, 28 Jul 2013 03:38:24 +0000</pubDate>
			<guid>https://www.soliforum.com/post/31188/#p31188</guid>
		</item>
		<item>
			<title><![CDATA[Re: Problems with Slic3r on certain models]]></title>
			<link>https://www.soliforum.com/post/31187/#p31187</link>
			<description><![CDATA[<p>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.<br />Solution I found was to download Kisslicer, and use that for tougher models.</p>]]></description>
			<author><![CDATA[null@example.com (ThatGuy)]]></author>
			<pubDate>Sun, 28 Jul 2013 03:30:22 +0000</pubDate>
			<guid>https://www.soliforum.com/post/31187/#p31187</guid>
		</item>
		<item>
			<title><![CDATA[Re: Problems with Slic3r on certain models]]></title>
			<link>https://www.soliforum.com/post/31177/#p31177</link>
			<description><![CDATA[<p>Upload the models to cloud.netfabb.com to fix them.</p>]]></description>
			<author><![CDATA[null@example.com (IanJohnson)]]></author>
			<pubDate>Sun, 28 Jul 2013 01:44:50 +0000</pubDate>
			<guid>https://www.soliforum.com/post/31177/#p31177</guid>
		</item>
		<item>
			<title><![CDATA[Re: Problems with Slic3r on certain models]]></title>
			<link>https://www.soliforum.com/post/31176/#p31176</link>
			<description><![CDATA[<p>Repetier-Host is Version 0.85b, and my Slic3r is version 0.9.9</p>]]></description>
			<author><![CDATA[null@example.com (vong888)]]></author>
			<pubDate>Sun, 28 Jul 2013 01:33:12 +0000</pubDate>
			<guid>https://www.soliforum.com/post/31176/#p31176</guid>
		</item>
		<item>
			<title><![CDATA[Re: Problems with Slic3r on certain models]]></title>
			<link>https://www.soliforum.com/post/31173/#p31173</link>
			<description><![CDATA[<p>What version of RH and slic3r?&nbsp; This is usually because the model is not manifold, but I&#039;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...</p>]]></description>
			<author><![CDATA[null@example.com (cckens)]]></author>
			<pubDate>Sun, 28 Jul 2013 01:15:01 +0000</pubDate>
			<guid>https://www.soliforum.com/post/31173/#p31173</guid>
		</item>
		<item>
			<title><![CDATA[Problems with Slic3r on certain models]]></title>
			<link>https://www.soliforum.com/post/31172/#p31172</link>
			<description><![CDATA[<p>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.</p><p>Any insights would be appreciated.</p>]]></description>
			<author><![CDATA[null@example.com (vong888)]]></author>
			<pubDate>Sun, 28 Jul 2013 01:04:40 +0000</pubDate>
			<guid>https://www.soliforum.com/post/31172/#p31172</guid>
		</item>
	</channel>
</rss>
