<![CDATA[SoliForum - 3D Printing Community — Just had my first slic3r screwup]]> https://www.soliforum.com/topic/4473/just-had-my-first-slic3r-screwup/ Fri, 08 Nov 2013 13:12:19 +0000 PunBB <![CDATA[Re: Just had my first slic3r screwup]]> https://www.soliforum.com/post/41029/#p41029 Yea, I was sort of suspecting openscad. I don't think I did anything very exotic in openscad, just unioned my cone and cylinder shapes and subtracted off the PCB vise bar. The trouble all started when I added the cone. I'll check out the new RH. Thanks!

]]> Fri, 08 Nov 2013 13:12:19 +0000 https://www.soliforum.com/post/41029/#p41029 <![CDATA[Re: Just had my first slic3r screwup]]> https://www.soliforum.com/post/41028/#p41028 The original model appears to have 6 self-intersecting triangles in some key positions and a degenerate face in a crucial joint and a few 'non-orientated normals' aka flipped-triangles.

Its hard to see all, but the bad self-intersecting ones are highlighted mainly in this view, and the orange intersected triangle leading to a degenerate face is the thing one down the front of the handlebar mount right where it steps out.

My attached Repetier-Host 0.91 with its improved model analysis and repair (aka 'deep analysis' button) manages to fix it up and slic3r goes on to slice it just fine.

So the issue is 100% the model input, but I can't say if its just openscad or how you modelled it in openscad. Its confusing the slicers quite fairly due to its aforementioned model construction issues, but at least the soon-to-be-released RH 0.91 with its built in analysis/repair works a treat wink

Attached is the image and my RH-0.91-dev that I posted elsewhere.
http://www.soliforum.com/misc.php?action=pun_attachment&amp;item=3897

Same thing via RH-0.91 with model repair and straight into slic3r:
http://www.soliforum.com/misc.php?action=pun_attachment&amp;item=3898

Anyway - you can definietely move away from the slicers and back to openscad in terms of finger pointing big_smile

]]> Fri, 08 Nov 2013 13:01:38 +0000 https://www.soliforum.com/post/41028/#p41028 <![CDATA[Re: Just had my first slic3r screwup]]> https://www.soliforum.com/post/41027/#p41027 It is actually amazing how much this little part confused every slicer. I previously made it a cylinder and nothing had any problems, then a decided to make the top half very very slightly conical so it would squeeze more tightly into the conduit, and not only did I get the bad slic3r results, but when I tried kisslicer, it was differently confused. You wouldn't think such a simple thing would wreak so much havoc :-).

I did finally run it through netfabb cloud service and the resulting fixed STL was able to slice and print correctly with slic3r.

I don't know if this implies an openscad bug or slic3r bug or what.

More details at: http://home.comcast.net/~tomhorsley/har … bvise.html

]]> Fri, 08 Nov 2013 12:44:34 +0000 https://www.soliforum.com/post/41027/#p41027 <![CDATA[Just had my first slic3r screwup]]> https://www.soliforum.com/post/40870/#p40870 I guess it is time to try and figure out how to get my settings into kisslicer :-).

I was trying to print what seemed like a simple enough part and a "ramp" I cut out of the inside of a cylinder was turned into a "step" by slic3r  (running slic3r-0.9.10b-4.fc19.noarch on fedora).

If I look at the stl preview in RH, the ramp is there, if I look at the gcode simulation, it becomes a step.

Very weird. (This is a little connector designed to grab the bar on the PCB Vise from thingiverse and fit inside a short piece of electrical conduit).

PCB Vise: http://www.thingiverse.com/thing:12756

]]> Thu, 07 Nov 2013 02:19:09 +0000 https://www.soliforum.com/post/40870/#p40870