Running PrusaSlicer in batch (command line) mode: "Mixing configurations for FFF and SLA technologies"
I have a script set up to generate 150+ test prints in a variety of filament types and nozzle sizes that I use for calibration whenever I switch nozzles or make other hardware changes. I've been using an older version of Slic3rPE for this. I'm trying to update the scripts to use the latest release of PrusaSlicer. I've managed to figure out most of the requisite parameter changes, but I'm getting a "Mixing configurations for FFF and SLA technologies" message and no output gcode is generated.
Here's the base command invocation:
/Applications/Original\ Prusa\ Drivers/PrusaSlicer.app/Contents/MacOS/PrusaSlicer --printer-technology FFF --center 125,105 --export-gcode $*
I call several different .ini files for filament and nozzle settings. I seem to be missing some simple new parameter for "don't do SLA" but I can't find it. Any tips?
and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan
RE: Running PrusaSlicer in batch (command line) mode: "Mixing configurations for FFF and SLA technologies"
A bit more concise example with the output bolded:
% /Applications/Original\ Prusa\ Drivers/PrusaSlicer.app/Contents/MacOS/PrusaSlicer \
--printer-technology FFF \
--center 125,105 \
--export-gcode --loglevel 0 \
--load printers/printer_mk3.ini \
--load nozzles/0.20mm.ini \
--load filaments/PLA.ini \
--load settings/settings_common.ini \
--load settings/settings_012_layers.ini \
--output output/PLA/0.20mm/20mmcube.gcode models/normal/20mm_Cube.stl
Mixing configurations for FFF and SLA technologies
Changing loglevel is disappointingly useless.
and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan
RE: Running PrusaSlicer in batch (command line) mode: "Mixing configurations for FFF and SLA technologies"
Quick follow-up. By eliminating the various .ini files it works. The problem is, PS won't give me any indication about what it is in each config file that it doesn't like. I've opened an issue on github, but I'm hoping someone can point me to information on what's changed between updates.
and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan
RE: Running PrusaSlicer in batch (command line) mode: "Mixing configurations for FFF and SLA technologies"
Update: the issue is fixed in PrusaSlicer 2.2.
and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan