Slic3r: Consider moving retraction settings to Filament Settings

[jammi]

Usability-wise, I'd like the retraction length setting to be a part of the filament profile, since different filaments require different retraction length due to stringing.

[Patola]

I agree with you opinion. It won't help if you use firmware retraction though.

[VBen]

perhaps a custom gcode per filament can be used to setup the firmware retraction

[bubnikv]

Maybe a general way to override printer settings by filament settings would
be useful. At the prusa3d fork I have added a limit for a per filament
maximum volumetric extrusion rate, useful for multi material printing. I
can imagine a user interface similar to the object settings to add new
attributes to a filament.

On Mon, Jan 2, 2017 at 9:05 PM, VBen [e-mail] wrote:

perhaps a custom gcode per filament can be used to setup the firmware
retraction

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/alexrj/Slic3r/issues/3643#issuecomment-270014882, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFj5IwhEB6zX_MB2dWzI4epSZ6-zq1TPks5rOVh2gaJpZM4LYtIJ
.

[lordofhyphens]

I've been thinking about override hierarchies myself (currently the idea for me is print -> filament -> printer for something that is shared), either for custom gcode or certain configurations that can logically be in different places.

Reusing the override interface makes some sense, but would require more refactoring to get them to save properly with the hierarchy.

[alranel]

It is now possible to override Retraction settings from Filament profiles :) Enjoy!

[hoegge]

Any chance getting this implemented in Slic3r PE too?

[lordofhyphens]

@hoegge ask in slic3r PE issue tracker, but it depends on how much their code has diverged.