Every day i use Slic3r i find a new flaw or bug - like the one pictured below, where it completely forgot to infill the layer (presumably the part where it bridges over sparse infill). Or on the same print, where it suddenly speeds up in the most critical region of the external perimeter. Or the fact that, ever since RC2, it crashes if i slice more that one job without restarting Slic3r.
I keep telling myself to try Cura, but never get around to it.
What’s your slicer of choice? For those using Cura, are there any features missing that make you wish you’d be using another slicer?
Slic3r is probably doing that bridging on a different layer. Things like that can get kinda weird, especially with “combine infill” turned on, but they usually seem to work out in the print. “It’s not a bug, it’s a feature”?
If you want to dip your toe in Cura, you might want to check out MatterControl. You can import your Slic3r config into it, and it will translate it so that you can seamlessly switch between Slic3r and CuraEngine.
I tried cura and fell in love. Much quicker to slice and print and have never had trouble with it. I just wish it had infill every n layers like slic3r
@Whosa_whatsis the print just finished and there’s definitely no material there. Plus, I’m using a very down to earth with none of the fancy features turned on (except brim). It’s little things like that which annoy me to no end. Thanks for the tip with Mattercontrol, i’ll try it out.
I swear to kisslicer, it has never fail me. Too bad that its abandoned. I try here and there cura and slic3r, have also bought simplify3d, witch is very good if not the best of the bunch, but has poor start/stop strategy or seam hiding if you want. Kisslicer is still my overall winner, although almost a year with no updates. Cura on the other hand has reactions figured really well, but like said, kisslicer really swallows everything and does good job every time over and over again.
kisslicer for me too, It just gives me consistently good prints on everything. If he’s finished with it I wish he’d just upload the source!
I might try cura for the octoprint integration and to support FOSS.
In answer to your original question, I like Cura, but Slic3r’s multiple selectable filament and print profile configurations have me hooked. I don’t think I can get along without them.
I have fine tuned configs for all my filaments, so I just select one in the drop-down, rather than changing multiple parameters. Same with print profiles. High-res, zero infill? Select. Coarse with 100% infill? Select.
@Carlton_Dodd That’s the one thing that’s really making it difficult for me to switch away from Slic3r. Printer profiles are important too, as there are several different models that I use regularly. Cura now has a machine selection menu, but things like nozzle and filament size still have to be changed manually each time I switch between a Bukobot and a Bukito.
I am using cura and had never an issue. It is so simple and fast…of course it lacks of some advanced features as stated by many others, but i never used them before, anyway. Give it a try…
My biggest problem with Cura is that it’s a really bad printer host, and because it’s a host, it’s generally not integrated with other hosts. We’re now starting to see other hosts (like octoprint and mattercontrol) supporting CuraEngine, so it’s looking more appealing.
@Ashley_Webster there’s a python script that will remove those, I’ll have a look for it…
For day to day use I use Cura, it just simply gets the job done with little hassle. The only thing i wish it had is filament profiles.
Filament profiles seem to be low-priority for Cura because the Ultimaker 2 has filament diameters and temperatures handled by the firmware, as part of their control panel code. Of course, wide adoption of UFID will mean that none of our slicers need to know that information.
@Whosa_whatsis Have you tinkered with the new Cura RCs? The new printer host is customizable and even includes a sample Pronterface UI. It has the potential become a very nice host.
Out of curiosity would a page that takes one config file, parses it and turns it into another config file be something you guys would like? I have allot of the code already written I would just needed to write a parser.
Sometimes I can get better Slic3r infill results from the same STL just by rotating the part 90 degrees. I usually experience the opposite bug, where it infills something it shouldn’t.
@John_Ridley
I’ve managed to build Slic3r by slavishly following the instructions for building with local::lib; it never worked for me trying to install the dependencies in the usual system directories.
@Mark_Estefanos every X layers infill is coming to Cura. I did not want to add it till I knew how to do it properly. I have the idea figured out how to do it properly (exactly what I need to code, not just the general idea), but I haven’t got around to code it yet. (So much to do, so little time 
)
@Daid_Braam Awesome! I’m looking forward to it.