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: make object labels match instance names #2134

Open
paulr4 opened this issue Apr 16, 2019 · 4 comments
Open

Feature request: make object labels match instance names #2134

paulr4 opened this issue Apr 16, 2019 · 4 comments

Comments

@paulr4
Copy link

paulr4 commented Apr 16, 2019

Version

1.42.0-beta2+win64-full

Operating system type + version

Windows 10

Behavior

Slic3r's object labelling feature works well with 'Octoprint-Cancelobject'. However, one small improvement would improve usability.

Slic3r currently gives objects a unique label in the gcode file. For multiple instances of a single object, the label could be something like 'test.stl id:0 copy n', where n is the copy number, starting from 0. Slic3r identifies multiple instances differently, with an instance number starting from 1.

Would it be possible to use the same numbering system for both purposes? I ask because the method for selecting the object to cancel in OctoPrint can be inaccurate, and a way to double-check the object number to be cancelled against the Slic3r job would help avoid mistakes.

@bubnikv
Copy link
Collaborator

bubnikv commented May 4, 2019

it certainly makes sense. It requires a bit of gymnastics though, as the slicing back-end currently is not aware of possible instances, which are out of the print bed, therefore not printed. But it should be possible with some effort.

@paulr4
Copy link
Author

paulr4 commented May 4, 2019

I guess an instance/object name would need to be passed to the slicer backend along with the shape data. Instances off the print area wouldn't matter since they don't need to be named, sliced, or cancelled.

@rtyr rtyr added the OctoPrint label Jan 28, 2021
@robot256
Copy link

This feature is present in Prusa Slicer 2.5.0 at least. It works with Klipper "exclude object" functionality as well.

It is broken in 2.6a6. The copy ids are assigned randomly or all zero. See #10257

@kubispe1
Copy link
Collaborator

Thanks, @robot256. There is an actual statement from the developer regarding this topic in PS 2.6.0-beta1.
#10257 (comment)

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

5 participants