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

Multi-material printing request: Retract when crossing interface shells #2298

Closed
jonaskuehling opened this issue Oct 10, 2014 · 4 comments
Closed
Labels
Done This issue is implemented and considered complete.
Milestone

Comments

@jonaskuehling
Copy link

The "interface shells" option for multi-material (or -color) printing is great, but would be even better when those interface shells (=internal perimeters..) would also trigger retraction, so that the materials/colors don't get mixed up during non-retracted internal travel moves.

I think one would only activate die interface shells option anyway, when highest color-/material-separation even inside the object is intended. For example with at least one translucent material.

Think about a dual-color print from red and translucent material. There would be lots of red strings (travel without retraction from one red island to the next, potentially crossing translucent regions) inside the translucent volume.

Should be standard I think, simply never cross any kind of perimeter (be it outside or inside/interface) without retraction.

(Again, I think I have already read about this kind of request somewhere, but cannot find it again, unfortunately. Let me know in case there' already some milestone marking for it...)

Talking about 1.1.7-stable btw.

@jonaskuehling
Copy link
Author

Basically it's a detail-improvement of #1847 ...

@alranel alranel added this to the 1.2.2 milestone Dec 8, 2014
@alranel
Copy link
Member

alranel commented Dec 8, 2014

I see what you say.
However, the Interface shells option doesn't generate internal perimeters but only internal solid horizontal shells between materials. Internal perimeters are always generated if adjacent regions are assigned to distinct extruders. I agree with you that it should trigger retraction if a region boundary is crossed.

alranel added a commit that referenced this issue Dec 9, 2014
…riggered also when crossing the boundaries of a single region. #2298
@alranel
Copy link
Member

alranel commented Dec 9, 2014

Done!

@alranel alranel closed this as completed Dec 9, 2014
@alranel alranel added the Done This issue is implemented and considered complete. label Dec 9, 2014
@jonaskuehling
Copy link
Author

Ah ok, now I got it!

Thanks for fixing the retraction issue in any case, will test that shortly with further "manual soluble support prints" (manually generated support volume to achieve close contact between model and support).

BTW did you make any progress in terms of a "soluble support" option lately? Should be quite easy since support would just needed to be generated with model layer height, instead of dynamically calculated height to end up with the desired space to the object like it's wanted for break-away-support. Further the object's supported regions mustn't be printed like bridges but just like any other full-contact-layer, squished perfectly on top of the support interface.

You know we'd pay for it, don't you? ;) Would be just one chance to give at least something back for your awesome development so far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Done This issue is implemented and considered complete.
Projects
None yet
Development

No branches or pull requests

2 participants