What Slicer do you use for Personal use?

Inspired by this thread

What slicer do you personally use? Good luck, Bad luck etc…

Currently I’m using Creality 1.2.3., It’s based off CURA. I used CURA the other day with bad results. It did not put the proper offsets in the G-code so it went to one of my corners & then rammed into the bed before I could stop it.
The CURA is set up right, I did not see anywhere to put offsets in.

The Creality slicer is very generic & I think it leaves a lot to be desired. It works OK, but I would like other options, such as changing the infill type.

3 Likes

I have really liked Cura for my Ender 3 pro. Sometimes it puts weird lines in the slice that show up in the print. But you can see it in the preview and reslice and it tends to correct itself.

I started with Creality but was not impressed with its capabilities.

1 Like

Just the Prusa version of Slic3r here. They basically forked and contribute back changes (in theory at least, I haven’t verified etc.).

It does what I need so far without issue, but I haven’t tried to do lithopanes or “vase mode” objects yet. I’m not sure if it does everything I might eventually need, but I’m not super advanced on this stuff.

2 Likes

The only one i’ve used is PrusaSlicer 2.2.0. It exceeds my needs.

They recently made a number of updates. These may sound small but have been great for me. I change color often and that feature has been enhanced to do a pause without unloading filament. It makes it easy to drop in an embedded object like a magnet. Also the export gcode button has an addition to write the gcode to an SD card without having to select it. After you export, another button shows up to safely eject the SD card.

2 Likes

Simplify3D for my Marlin based printer…

2 Likes

I use a hodgepodge of slicers, based on printer:

  • KissSlicer for the Polyprinters (and as a general model viewer)
  • Cura for my Monoprice Mini Delta
  • PrusaSlicer for my Prusa

I always slice and save, then print the GCode separately. I keep separate SD cards based on filament (PLA, ABS) so I don’t accidentally try to print ABS with PLA settings.

I hacked the settings on the PolyPrinter Pronterface controller to act as a print-spooler for my MPMD as well.

1 Like

My main requirements for a slicer are speed and control for single extruder, non-supported prints. That’s most of what I do nowdays.

I use PrusaSlicer for my Prusa and my Voron. A big plus is that my Prusa is a ‘just work’ printer that I don’t tinker with and I assume it works better with their slicer. I actually started using Slic3r on a Rostock Max before I had the Prusa, so that wasn’t the driving decision.

I found Slic3r (where PrusaSlicer came from) was much lighter and faster than my other free option, Cura. I strongly dislike KissSlicer for the interface, call it personal preference. I used to use Cura for some Ultimakers and while it worked well it tended to be slower than Slic3r and that really turned me off of it.

Back in school we used Simplify3D from about the time it was released until I graduated, it was really nice, fast, had a ton of features, and at the time of its release about the best support generation you could get. I’ve looked back recently but I don’t think it’s worth the money any more over Slic3r, at least not for me.

I miss some of the ‘place surface on bed’ and easy fine control you get with Simplify3D, like easy variable infill or temp towers, but Slic3r has good enough options for everything I’ve needed so far.

1 Like

I’ve been really happy with the latest version of Cura for my CR-10. I like options that it gives me, and the interface with my OctoPi doesn’t hurt either.

This is most certainly an incorrect printer setup than an issue with Cura.

For years I used to have to have an offset in the slicer to compensate for an incorrectly set z-height, until I eventually fully comprehended the differences and implications of “offset”, “level”, “flat”, “mesh leveling” etc…

Your printer should NEVER push the nozzle into the bed, regardless of what GCode is sent to it if the z-offsets are set correctly.

If you send “G28” what does your LCD say your Z height is (or use M114 to read the current positions at a terminal)? It should match the actual distance between the nozzle and the bed. Note, the actual distance will probably NOT be zero unless you (unnecessarily) spent a lot of time physically adjusting your Z end stop.

I used to adjust my z-offset in the slicer to correct for my z-home position being wrong.

If the actual z gap is different to what M114 says then you should really correct this with M851.

Don’t forget to a) save (M500) then b) re-home. If you have enabled mesh leveling then I recommend M420 S1 followed by G28 then re-measure the real distance and check against M114 result.

Once these are correct you can then dis-regard any z- offset corrections in the slicer, and trust that the first layer will actually be what you ask for. “G1 Z0” will put the nozzle just onto the bed, “G1 Z1” will give a gap of 1mm etc…

If you have calipers you can adjust with M851 until a piece of paper is JUST held after moving up “G1 Z1”, place paper under nozzle then “G1 Zmeasuredpaperthickness” where ‘measuredpaperthickness’ is… well… the thickness of the paper as measured with your calipers. I have gotten really good at visually guestimating 0.1mm instead of using paper :slight_smile:

As I say, in the past I tried to correct for bad z-offset by either changing the z-offset in the slicer (bad) or changing the initial layer height (REALLY bad, since this also affects the flow rate and not just the height, so is basically completely wrong)

1 Like