more info in file names

[Gizmo6]

Is your feature request related to a problem? Please describe. I switch a lot between materials and nozzle sizes depending on the product. I will sometimes forget which set up I have used.

Describe the solution you'd like If the file name had some sort of info such as manual PA or auto PA, nozzle size used and material. I think it would be very helpful.

Describe alternatives you've considered Manually putting this info in.

[hliebscher]

you can add more variable in filename.... samples https://wiki.bambulab.com/en/software/bambu-studio/placeholder-list

https://help.prusa3d.com/article/list-of-placeholders_205643. (names a little bit different as sample)

{input_filenamebase}{layer_height}mmJ1{print_time}{day}{print_preset}{print_preset}.gcode

AK - a_0.25mm_J1_31m19s80.20mm 0.6 Standard @Snapmaker J1 - Snapmaker J1 0.6 Düse 1.6.3.gcode

[julie777]

@Gizmo6 Do you mean the filename for the file that is sent to the printer?

[Aron3DP]

I'd like to add to this request. I'd like at least filament temp to be added to naming. I've tried the tooltip items for nozzle_temperature and initial layer and they do not work.

[Gizmo6]

@Gizmo6 Do you mean the filename for the file that is sent to the printer?

Yes. so for example file output would be. "name of file" "nozzle size" "material type" so like. "Sample 0.8 PLA"

[Gizmo6]

Thanks to [hliebscher]

Go to process tab - other - filename format. copy this and replace with the text the box.

{input_filename_base}__{nozzlediameter[0]}{filament_type[0]}.gcode

This will give file name followed by nozzle size and material used.

[JamesKR3D]

I'd also like to have the print temperature variable to be added to the filename options.

[VidiotGeek]

I'd like to add to this request. I'd like at least filament temp to be added to naming. I've tried the tooltip items for nozzle_temperature and initial layer and they do not work.

I came here looking to see if I was missing something or if there really wasn't a way of pulling the temperature into the filename output. Seems like I'm not the only one. I've tried all the tool-tip names also, in {curly} and in [square] brackets. No dice.

[ding-bat]

someone please give a working example of temperatures in filename, thanks in advance

[kylek29]

I'd like to add to this request. I'd like at least filament temp to be added to naming. I've tried the tooltip items for nozzle_temperature and initial layer and they do not work.

I came here looking to see if I was missing something or if there really wasn't a way of pulling the temperature into the filename output. Seems like I'm not the only one. I've tried all the tool-tip names also, in {curly} and in [square] brackets. No dice.

I'd also like to have the print temperature variable to be added to the filename options.

someone please give a working example of temperatures in filename, thanks in advance

nozzle_temperature is an array, so you have to reference a specific nozzle of that array. [0] would be the first one and would always be populated.

{input_filename_base}_{filament_type[0]}_{print_time}_{nozzle_temperature[0]}.gcode

Outputs as:

OrcaPlug_PLA_58m38s_230.gcode

• input_filename_base --> OrcaPlug
• filament_type[0] --> PLA
• print_time --> 58m38s
• nozzle_temperature[0] --> 230

[xi2023]

thanks @kylek29 the only thing i was missig was a name/printer model in the filename. printer settings -> notes -> type in a name or model and add {printer_notes}

{input_filename_base}_{print_time}_{layer_height}mm_{filament_type[0]}{nozzle_temperature[0]}C_{printer_notes}.gcode

filename_25m59s_0.2mm_PLA200C_printername.gcode

[kylek29]

thanks @kylek29 the only thing i was missig was a name/printer model in the filename. printer settings -> notes -> type in a name or model and add {printer_notes}

{input_filename_base}_{print_time}_{layer_height}mm_{filament_type[0]}{nozzle_temperature[0]}C_{printer_notes}.gcode

filename_25m59s_0.2mm_PLA200C_printername.gcode

Yeah, that's one way to do it (just remember to not make your notes too big!). PrusaSlicer has assignable variables in that same area of the program (so you could assign a printer_name variable and reference it), but that feature hasn't been ported yet.

[Echo-o-Tree]

thanks @kylek29 the only thing i was missig was a name/printer model in the filename. printer settings -> notes -> type in a name or model and add {printer_notes}

{input_filename_base}_{print_time}_{layer_height}mm_{filament_type[0]}{nozzle_temperature[0]}C_{printer_notes}.gcode

filename_25m59s_0.2mm_PLA200C_printername.gcode

Just to add on to this, in case others like to sort by Material color/type you can go to Filament Settings > Notes and type the Brand/Color/Material etc there. Then, in Process > Others > Filename Format use {filament_notes[0]} for single material prints, or {filament_notes[0]}_{filament_notes[1]} (add one per filament used for multi material prints)

This will append the filament notes per filament to the location you placed the line in your Filename Format section.

[github-actions[bot]]

Orca bot: this issue is stale because it has been open for 90 days with no activity.

[gidgiddoni2]

I'm a NB at Orca Slicer 1.9.1and would like to change the name of the .gcode file to be plate_number print_time.gcode... Where in Orca do I set this filename format?

[Catriks]

Is there a code for using current/project file name? Lets say I open a file called file123.stl, then save it as a doorhandle.3mf, and I want the gcode filename to be doorhandle.gcode. Using {input_filename_base} will still use the original filename.

[jbjhjm]

@Catriks your problem is discussed here: https://github.com/SoftFever/OrcaSlicer/issues/1945

[KubaMiszcz]

it doesnt work for me, I've tried your patterns and it always send filename_plate_1

where filename is name of 3mf file on disk, plate has no names, it update plate names if named, but nothing more, changing pattern wont affect generated gcode name

[jbjhjm]

@KubaMiszcz {filename} is not implemented - its being requested in https://github.com/SoftFever/OrcaSlicer/issues/1945 Plate name works fine for me too and so does filament type (don't know the specifier out of my head). So "changing pattern wont affect generated gcode name" seems invalid to me. If your Orca build doesn't react to name changes at all, it is likely a different issue and you should open a new error report.