

For the full background on Pathio, I recommend visiting their website. For this article I’m comparing this beta version, with my Ultimaker Cura version 3.6.0. Technical note: As of this writing Pathio is currently in beta (v0.5.0-beta4), so many of the features are not yet finished. So, what do I think of the state of Pathio, and the road ahead? Let’s find out by comparing Pathio vs Cura. Why should we consider switching from our current slicer to Pathio? Specifically, can Pathio perform better than Cura?Į3D’s Pathio team is making some bold promises, and if they can follow through Pathio could really disrupt the industry and make your life better in the process.

#Cura vs ultimaker cura upgrade#
Sponsored by printer upgrade and accessories maker E3D, Pathio aims to provide an updated take on 3D print slicing.
#Cura vs ultimaker cura software#
Whereever I used CuraEngine before in my existing software packages I will switch to Cura-CLI-Wrapper with cura-slicer.Recently a new entry appeared in the 3D print slicing market. Processing overhang-inout.stl, slicing to overhang-inout.gcode % cura-slicer -support-enable=true overhang-inout.stl Processing cube.stl, slicing to cube.gcode = Cura-Slicer 0.0.3 aka Cura-CLI-Wrapper (CuraEngine 4.4.1) = The system-wide settings reside in /usr/share/cura-slicer/base.ini and should not be be changed as it will be overwritten when upgrading Cura-CLI-Wrapper. The user settings reside in ~/.config/cura-slicer/base.ini and will not be overwritten when upgrading Cura-CLI-Wrapper, make your changes there. display settings matching termĬura-slicer overhang.stl -output=sample.gcodeĬura-slicer overhang.stl -layer-height=0.1 -support-enable=true -o sample.gcode = set CuraEngine settings (keys with '-' will be converted to '_') version= set version of CuraEngine (default: 4) binary= set executable of CuraEngine (default: CuraEngine) version display version of this program and exit Usage USAGE Cura-Slicer 0.0.7 aka Cura-CLI-Wrapper (CuraEngine 4.4.1). This reduces the amount of brim you need to remove afterwards, while it doesn't reduce the bed adhesion that much.Įssentially it makes Cura and CuraEngine easy to use on the command-line and provides a way to learn of the hundreds of settings available. Only print the brim on the outside of the model. = brim_outside_only (Brim Only on Outside) =

More brim lines enhance adhesion to the build plate, but also reduces the effective print area. A small gap can make the brim easier to remove while still providing the thermal benefits. The horizontal distance between the first brim line and the outline of the first layer of the print. Normally this is done with the initial layer acceleration, but sometimes you might want to print the skirt or brim at a different acceleration. The acceleration with which the skirt and brim are printed. = acceleration_skirt_brim (Skirt/Brim Acceleration) = Skirt_brim_minimal_length = 250 (default)Īnd with -v switch you even get a more descriptive output: % cura-slicer -help brim -v Which lists ~570 settings as of CuraEngine 4.4.1 and its defaults and from where the defaults come from (definition defaults, config or cli), and you can query also a term e.g. Speciality is to query all the settings from cura-slicer directly: % cura-slicer -helpĪcceleration_infill = 3000 (default)Īcceleration_ironing = 3000 (default)Īcceleration_layer_0 = 3000 (default)Īcceleration_prime_tower = 3000 (default)Īcceleration_print = 3000 (default)Īcceleration_print_layer_0 = 3000 (default)Īcceleration_roofing = 3000 (default)Īcceleration_skirt_brim = 3000 (default)Īcceleration_support = 3000 (default)Īcceleration_support_bottom = 3000 (default)Īcceleration_support_infill = 3000 (default)Īcceleration_support_interface = 3000 (default)Īcceleration_support_roof = 3000 (default) But it came the point (2021/03) when I needed to have a simpler interface than CuraEngine – hence I wrote Cura CLI Wrapper, the executable cura-slicer looks like prusa-slicer or slic3r and has similar usage. I’m a great admirer of the Ultimaker Cura slicer since years, yet I predominantly have been using CuraEngine on the command-line via Print3r, which hides all the tedious configuration.
