Incorrect Filament type in published gcode file name
I believe this started when I upgraded to 2.3.0 just recently. Prior to that I was on the older version without paint on supports etc.
I have an MK3S and MMU2s.
If I am running Prusaslicer in my MMU2S Multi, hardware printer profile (to choose which of the 5 loaded filaments I want to use), when I publish a gcode to octoprint, the filament type in the file name seems to default to whatever is my Filament #1 selection.
So if I have PETG in Filament #1, and PLA in Filament #2, and I print with Filament #2, my output filename reflects PETG, even though the object was selected to use Filament #2.
Did this ever work correctly/is it supposed to?
RE: Incorrect Filament type in published gcode file name
I'm pretty sure that's just the way it works. In the output file name options in a print settings you specific the extruder the filament type is taken from, which by default is the first one.
RE: Incorrect Filament type in published gcode file name
@fuchsr
Is there a way to change the output filename to reflect the currently being used filament?
In the output file name is {filament_type[0]}, can that be changed to something else?
RE: Incorrect Filament type in published gcode file name
You can set it manually. Filament _type uses the usual coding convention of starting with index 0 instead of 1, so extruder 1 is filament_type[0], say extruder 2 is filament_type[1] etc. But I don't see a way to do this dynamically based on what you're actually printing.
RE: Incorrect Filament type in published gcode file name
That's odd, yeah, I don't want to go into the print settings each time I change something to make sure the published filename is correct. Surprising there isn't a way to do this automatically. It knows what extruder that file was created using (assuming only 1 is specified, a true multicolor print would have to be done differently) so I don't know why they don't code it to check and use that.