RE: Output filename format
I've been using this template for some time;
output_filename_format = [input_filename_base] [notes] [filament_type] [layer_height]X[nozzle_diameter] [first_layer_temperature]-[temperature] [first_layer_bed_temperature]-[bed_temperature] [print_time].gcode
It has enough info that I can look at an old file and figure out how to print it.
Sample print profiles here.
Paint on Fuzzy Skin
It would be great to be able to apply the fuzzy skin texture to certain parts of models using the "paint on" feature.
Previous post in wrong place!
please delete
It can’t be deleted. Also posting requests on the forum is the wrong place, you need to post over on the Prusa slicer GitHub. Besides the one you want has already been requested so go find it over there and add a ‘me too’ on it.
RE: Output filename format
This is now possible.
Using Version 2.4.0: Go to Help -> Show Configuration Folder
Under the folder "vendor", open "PrusaResearch.ini" with a text editor and update the value "output_filename_format" under "[print:*common*]".
There is more than one section to change this value, so ensure you change only the ones that are relevant to your needs.
RE: Output filename format
Could someone help me figure out how to add the Scale factor to the file output name? I have the same model at 100% and 200% etc but other than looking out the time stamp on the file, I would like to have the scale factor visible. Is that possible? TIA!
RE: Output filename format
I don't see how that's possible short of doing it manually because the various objects in your print assembly may have all been scaled differently, so how could the slicer know which of these scale factors you'd like to see in the file name.
RE: Output filename format
Normally I just save the project twice, one called xxxxx_100pc and the other xxxxx_200pc. That way when you generate the gcode its based on the project name instead of the first object loaded and that describes what you have done to the object anyway.
Btw its best not to use an actual % in the filename unless you are absolutely sure your system can handle it. % are special characters for many things.
RE: Output filename format
Btw its best not to use an actual % in the filename unless you are absolutely sure your system can handle it. % are special characters for many things.
I have an issue open on the PrusaLink github site on that topic. I used to include the infill percentage placeholder in the output file name, like "15%". Never had a problem until I started playing with PrusaConnect/PrusaLink. It still works fine with Prusalink on the Mini but PrusaLink on the Mk3S refuses to accept it. My issue is with consistency between the PrusaLink implementations for Mk3S and Mini, and that the Slicer shouldn't output placeholder contents that are not acceptable. (e.g., maybe replace 15% with 15pct). I totally understand that % is a "dangerous" character but it can be handled safely in code. Or just don't allow it and don't output it. Either way is fine with me. In the end, not a big deal because I also realized that I never made use of the infill information anyway 🙂, and neophyl's advice to avoid "unusual" characters is a wise one.
RE: Output filename format
Ahhh, yes that logic makes perfect sense. Thanks for answering my curiosity. I will continue to edit the generated file name manually when need be. Thank you!
RE: Output filename format
I searched today for output options.
Came to this solution after 30min of hit and miss ->
[input_filename_base]__[normal_print_time]__{digits(total_weight, 3)}g__{digits(total_cost, 2, 2)}€.gcode
Holder__1h46m__ 17g__0.41€.gcode
RE: Output filename format
I can´t edit my post. I got some errors after testing it. Don´t know why it stopped working but i had to remove the €.
[input_filename_base]__T=[normal_print_time]__W={zdigits(total_weight, 3, 0)}g__C={digits(total_cost, 2, 2)}.gcode
Holder__T=2h17m__W=023g__C=0.57.gcode
Looks even better now. 😀
RE: Output filename format
Update to an old post.
All the Output file name formats are now in the Knowledge Base:
https://help.prusa3d.com/article/list-of-placeholders_205643