PrusaSlicer output filenames for STL vs. 3MF
Hi -
This is a small nagging issue that I have been having. PrusaSlicer does not use the filename of a 3MF file when it creates the output gcode file. If I do the same thing but use an STL file, the Slicer uses the STL filename when it creates the output gcode file. As an example, if I create a model called testPart and save it as testPart.stl and testPart.3MF, the file names create by PrusaSlicer are
- testPart.stl >>> testPart_0.15mm_PLA_MINI_2h10m.gcode
- testPart.3MF >>> body811099_0.15mm_PLA_MINI_2h10m.gcode
Does anyone know what setting I need to change in order to get the slicer to use the 3MF filename for the gcode output file?
Thanks!
At the moment there is nothing to set or configure for this. Its also not a simple matter. The gcode output file name is defined in your print settings>Output options>Output filename format. You must be in expert mode to see the setting. Generally on one of the default profiles it will have something like "input_filename_base" in there. That takes its name from the name of the file.
Here is where its not quite so simple though. When you open a new blank Prusa Slicer session what you are doing is opening a new Project file. Project files for PS are of type 3mf. A 3mf file though is basically a container. It defines how to store things but what is stored is entirely up to the program. Normally when you save a PS 3mf as well as the objects you want to print it also saves all the profiles, settings, modifiers etc too. 3mf is basically a type of zip archive with some more bells and whistles.
Until you save it though it doesnt have a filename. So it uses the name of the first Object that is loaded into the container as a placeholder. It will suggest the same name if you go to save the project too. You dont have to use it as you can specify any name you want. If you do give it a name then PS will use the 3mf name for the exported gcode part of the filename base.
So when you import an stl with the name rocket_cone.stl as the first item it will use that as it needs something. so it will be rocket_cone.gcode or it will suggest rocket_cone.3mf if you choose save project. All great so far.
When you load in the contents of a different 3mf file though (not open, import, especially from a different piece of software like F360) then its loading in the CONTENTS of their 3mf. As its only bringing in printable objects and not settings or other info that it doesn't know what to do with then if that other software has called its objects box1, box2 etc then the name that prusa slicer will use as default will be box1. The behaviour is exactly the same. You have imported the contents of that container and not opened that container/project file.
You should really be naming your objects in your design software to something meaningful instead of leaving them as whatever the default is. Its the same in Blender, you end up with Cube.001, Cube.002, Cylinder.005 etc. Which is not very helpful when you want to load a particular item from one blend to another.
2.4.0-alpha1 changes
This will be changed in the upcoming 2.4.0-alpha1. Global name of the multipart object will be taken from 3MF file name (currently it uses the name of the first object). Single part objects will also use the file name from 3MF file.
