What's with the Slice "engines"?

[Potatohead908]

What is the difference between Slic3r, MatterSlice and CuraEngine?

[Renha]

CuraEngine is only engine, others are full slicer software with GUI and other unneeded functions, like communication with printer, etc.

CuraEngine support is almost built-in to OctoPrint, unlike others.

[Captain Starfish]

From the perspective of someone looking at a menu on a front end app like MatterControl and thinking "Huh? I dunno, which one SHOULD I use?", the difference is they all have slightly different strategies for handling shapes. They all have different parameters you can tweak (although NOT necessarily through the MatterControl interface!) and they'll all generate different G-Code for the same STL file and settings.

Everyone has their own preference. I like MatterSlice for most things. It does a good job most of the time, it generates a smooth print and it's very simple (relatively) to configure. Slic3r seems a little more tuneable and has some nice features like hexagon/honeycomb fill but it has a bug where it will freeze during the slice process and it can make the printer jump around a lot. Cura is ok but I've had problems with some prints that MatterSlice just dealt with and Cura didn't really have any wonderful feature that drew me back to it after that.

Of course, once you leave the GUI of MatterControl, there are others like KISS Slicer and - if you like paying money for something you've never seen and gets only mixed reviews - you can buy Simplify3D.

[geneb]

Captain Starfish, hexagon infill has been added with the release of 1.3. They've also made some (good, IMHO) interface changes. Nothing really drastic though.

g.

[Potatohead908]

So if you were using MatterControl and a stand alone slicer, would you just take the Gcode from the slicer and past it in the "terminal window" of MatterControl?

[mhackney]

Surely MatterControl has a "Load gcode file" menu?

[Polygonhell]

I tried using again recently and yes it has a load gcode button, and an annoying dialog box to tell you that you need to ensure the gcode file was intended for your machine.
If I remember I think you just load gcode the same as any other model.
I really can't stand the matter control interface and it's terribly buggy on the Mac.

[mhackney]

Yeah, that's why I don't use it on Mac either. I've gone back to plain old Prontorface or Repetier Host for tethered printing or just print from SD card. I find that tethered printing is better at events where people are watching since they can see RH draw the print layer by layer and I can use the gcode view to show how 3D printing works.

[geneb]

You can do the same thing with MatterControl. Didn't you read the docs? *grins, ducks & runs*

g.

[Captain Starfish]

Haven't printed for a while, geneb - been busy playing with a new toy recently (4 axis CNC router). But that's nice.

Like I said, MatterControl is still my go-to. They seem to have gone backwards with the Mac UI the last couple versions I've installed but I'd still rather use it than Cura or Repetier.

[dajay23D]

I tried using again recently and yes it has a load gcode button, and an annoying dialog box to tell you that you need to ensure the gcode file was intended for your machine.
If I remember I think you just load gcode the same as any other model.
I really can't stand the matter control interface and it's terribly buggy on the Mac.

there's an option where you can get rid of that dialog box.

I've been playing around w/ MatterSlice, KISS and Slic3r a whole lot. I started out w/ MatterControl and still use it. I've never used RH and Cura. My daily routine is loading KISS Gcodes in MatterControl. Here's my opinion until I figure out a solution;
- The only thing I don't like about MatterSlice is their peripheries are not as smooth as KISS or Slic3r. There's always lots of gaps and I'm not sure how to get rid of it. I believe it's gotta do something w/ retraction and where the next layer starts. You can see it on preview. Because of this, it makes the outside look like it's got extra layer gaps, which also prevents me from using it. If they solve it or I solve this issue, I'd use MatterSlice all day. I also like how supports are integrated and how the preview shows your layers/model. There's a delay when you use the Slic3r in MatterControl. Sometimes, a good 30 sec

- I like how Slic3r codes single wall prints and bridges/overhangs. But how often do I print single wall? I find Slic3r is superior if you're printing calibration blocks all day. Often times, I want to use Slic3r, but then it doesn't code the way I want as far as infills and walls. For example, there are many times when a part doesn't need infill, but Slic3r adds it in there or else it'll print a gap. Like other said, sometimes Slic3r will jump around randomly or the path is not smooth.

- this leads me to KISS. It's the most versatile as far as generating a proper Gcode for what I want. I can randomly download something on Thingaverse, load it and it'll come out right. IMHO, I think KISS is the most challenging to calibrate. I can never seem to get Z height, Seam Hiding, Destring combos to work together. However, thanks to mhackney's codes! I'm using his codes and just changing some minor perimeters and I've been getting some real consistent prints. I really have to sit down one day and play w/ the Destring and seam hiding options. right now, I'm getting really thin layers and tiny gaps during layer changes in square objects. If i print a single wall calibration block, the layer gap/seam area is very thin and does not connect. I saw someone posting a similar issue, but I can't i find it at the moment. IME, KISS is also weak in overhangs and support features. Or maybe, I just haven't perfected the settings, yet.