Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Additional filename placeholders #4607

Open
therealzanfar opened this issue Aug 6, 2020 · 5 comments
Open

Feature Request: Additional filename placeholders #4607

therealzanfar opened this issue Aug 6, 2020 · 5 comments

Comments

@therealzanfar
Copy link

Version

Version 2.2.0+win64

Operating system type + version

Windows 10 Pro x64, ver. 2004, build 19041.388, feature pack 120.2202.130.0

3D printer brand / version + firmware version (if known)

Prusa i3 MK3s stock

Feature Request

Additional filename placeholders for use in Print Settings -> Output Options -> Output filename format

  • Parent Folder

    My workflow commonly involves multiple STLs per project, all saved in the same folder. These parts will commonly have similar or identical names as parts in other project--for example, multiple projects may include a similar, but not identical, "axle.stl". While the filename is sufficient to identify the part in a folder hierarchy, when exported, PrusaSlicer defaults to naming the GCode file "axle.gcode" which gets lost in the printers single-level storage.

    Please add a {parent_folder} placeholder that matches the name of the immediate ancestor folder of the primary object file.

  • Object Count

    My workflow commonly involves generating multiple GCode files from a single STL object usually in different quantities. That is, I might have a GCode file with 1, 4, and 16 duplicate objects on the build plate. Which file gets printed depends on the quantity of parts needed--sometimes I'm doing a production run and I use the full-plate x16 version, while sometimes I just need a quick replacement or a prototype and only want a single object.

    Please add a {object_count} placeholder that is the count of objects on the build plate.

Together, this means my ideal Output filename format would be something like:

{parent_folder}_{input_filename_base}x{object_count}_{layer_height}mm_{filament_type[0]}_{printer_model}_{print_time}.gcode
@josedpedroso
Copy link

I also have some new placeholder variables I'd like to request:

  • output_filename: the idea would be to build print progress messages with M117 and conditional g-code, to show different stats on odd or even layers, for instance, but always maintaining the real filename visible.

  • layer_min_volumetric_rate, layer_max_volumetric_rate, layer_avg_volumetric_rate: I was thinking about making some sort of automatic temperature adjustment script on layer changes, like Marlin's autotemp feature, but steadier.

@sslupsky
Copy link

I like the suggestion of the object count placeholder. This would be very useful.

@bubnikv
Copy link
Collaborator

bubnikv commented Oct 29, 2021

{num_objects} and {num_instances} implemented with 1ddd060

New placeholder parser values for output file name template;
{num_objects} - number of printable objects on the plater.
{num_instances} - number of printable instances on the plater, adding up
  	all printable instances of all objects.

It will be released with PrusaSlicer 2.4.0-beta2.

@sslupsky
Copy link

@bubnikv Thank you!

bubnikv added a commit that referenced this issue Oct 29, 2021
{num_objects} - number of printable objects on the plater.
{num_instances} - number of printable instances on the plater, adding up
  	all printable instances of all objects.
Implements #2735 #3339 #4607
@carlosjln
Copy link

Well this is still hanging, but I'd like to have the stl file name not the project filename. I save the project with specific print settings and just swap the files but I'd like to export with the sliced STL filename.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants