-
Notifications
You must be signed in to change notification settings - Fork 1.3k
This is a list of frequently asked questions - and answers - regarding Slic3r.
A: Slic3r version 0.9.0 introduced a new way of handling configuration which makes it easier to reuse e.g. a given filament configuration with e.g. multiple different printers. The new configuration system separates the settings for printing, filament and printer configuration in separate presets. To save a given preset, click on the small diskette button next to the preset name under the given tab.
The old way of managing Slic3r configuration is still available under the File menu. Simply use Export Config... and Load Config... to export the current configuration from Slic3r and load it back in. This is especially useful for sharing configuration files with somebody else or for exporting a configuration file for use when calling Slic3r from the command-line using the --load parameter.
A: Slic3r utilizes wxWidgets to store it's internal GUI configuration files. The exact location is platform-dependent and can be found by running slic3.pl --debug. Normally, there is no reason to poke around in these files, as they are all managed through the Slic3r GUI. You should probably use Export Config... from the File menu instead.
A: There are basically two options. The simplest is to use Slic3r stand-alone and load the resulting G-code file directly into Pronterface.
If you're feeling more adventurous, you can have Pronterface call the command-line Slic3r automatically when opening an STL file. To get this to work, you must first export the configuration, you wish to use with Pronterface, from Slic3r using Export Config... from the File menu. Next open Options from the Settings menu in Pronterface, and put the following under slicecommand:
slic3r.pl $s --load config.ini --output $o
and the following under sliceoptscommand:
slic3r.pl --load config.ini --ignore-nonexistent-config
Replace slic3r.pl with the full path to the Slic3r executable and config.ini with the full path of your previously exported configuration file. On OS X, the executable has a path like this:
/Applications/Slic3r.app/Contents/MacOS/slic3r
Whenever you edit your Slic3r configuration from within Pronterface, remember to re-export it using the Export Config... from the File menu.
You can specify a filename format by using any of the config options. Just enclose them in square brackets, and Slic3r will replace them upon exporting. The additional [input_filename] and [input_filename_base] options will be replaced by the input file name (in the second case, the .stl extension will be stripped).
More available variables include [timestamp], [year], [month], [day], [hour], [minute], [second], [version]. When using the graphical interface, [print_preset], [filament_preset], [printer_preset] will be available too.
The default format is [input_filename_base].gcode, meaning that if you slice a foo.stl file, the output will be saved to foo.gcode.
See below for more complex examples:
[input_filename_base]_h[layer_height]_p[perimeters]_s[solid_layers].gcode
[input_filename]_center[print_center]_[layer_height]layers.gcode
A: Have you calibrated Slic3r for your printer? If not, follow the steps outlined in the Calibration guide.