PrusaSlicer cli (command line) actions broken on Windows?
I can't get any command line actions to work with PrusaSlicer on Windows. For example
prusa-slicer.exe --duplicate 2 C:\example\file.stl
should open PrusaSlicer with two copies of the STL object, but only one object appears. Similarly documented command line actions such as --rotate and --cut and others have no effect at all. I have tested this with PrusaSlicer 2.8.0 and also with the older 2.6 version on Windows 10.
If anyone reading this uses Windows and can get PrusaSlicer command line actions to work please let me know and tell me if you had to take some extra steps to get it working. Or if you also can't get it to work post a comment about that to confirm the issue.
RE: PrusaSlicer cli (command line) actions broken on Windows?
There are MANY issues regarding the CLI on the PS github https://github.com/prusa3d/PrusaSlicer/issues?q=is%3Aissue+sort%3Aupdated-desc+cli+
However none of them are for it not working at all.
RE: PrusaSlicer cli (command line) actions broken on Windows?
Yeah, but I'm not sure if that's because it ain't broken in Windows (and the fault lies in my PC or brain) or if the cli features are so seldomly used by Windows people that no one has reported it. I'll wait for other people with Windows to test this and comment here to say if it worked for them or not, before opening an issue at the PrusaSlicer repo.
RE:
I have tried the CLI example from the first post above on another Windows PC, that one using Windows 10, and there too PrusaSlicer is not opened.
Has anyone with Windows gotten the CLI example to work?
RE:
I tried the command line and it didn't work with just prusa-slicer.exe. Windows doesn't have the Prusa slicer software in the "search path" . Also checking the shortcut properties for prusa slicer it shows the full path 2.7.4 uses to start the slicer. You may need the full path in the cmd line. c:\full-path\prusa-slicer.exe.
Whan I use the full path in cmd line mode, it starts. I made a .bat file to try your command line using full paths, The slicer opened, .stl loaded, but no duplicate.
This is on Windows 11.
RE: PrusaSlicer cli (command line) actions broken on Windows?
Further checking shows fullpath/prusa-slicer-console.exe is the command line version. --help-ff works with this to show all the options. --duplicate 2 still doesn't work for me on windows 11.
RE:
@vhubbard: I mistakenly wrote "there too PrusaSlicer is not opened" but should have written "there too the same issue happens". That is, there too PrusaSlicer opens the file but the duplication does not happen. Other cli actions similarly have no effect.
I do run the commands from a cmd window that first has its path navigated to the folder that contains prusa-slicer.exe . I also tried prusa-slicer-console.exe, with the same results. I should have mentioned these things earlier, apologies.
When I now reread the --ff readme text and https://github.com/prusa3d/PrusaSlicer/wiki/Command-Line-Interface I wonder if the behaviour I'm assuming should work is at all supported in the first place? That is, apply some actions and then open the transformed result in the PrusaSlicer GUI. Because there's no explicit mention of it there.
After some more tests this does work for me in performing the duplication action and saving the now two objects to a new STL, without opening the PrusaSlicer GUI.
prusa-slicer.exe --export-stl --duplicate 2 C:\example\file.stl --output C:\example\file2.stl
So as a workaround I can make a script to perform an action like that and output a temporary STL file and then as separate step open the temporary file in PrusaSlicer.
Alternatively I can skip the temporary STL and use cli actions to overwrite the input file
prusa-slicer.exe --export-stl --duplicate 2 C:\example\file.stl --output C:\example\file.stl
and then as a separate step open it.