-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
First model layer on top of raft doesn't use "bridge speed" (1.1.7) #2301
Comments
My apologies - I didn't refer to the dual extruder setup in this regard! Extruder1 was configured for perimeters and infill Didn't test with single extruder yet, if the first model layer on top of the raft-support will also print with perimeter speed instead of bridge speed like in my dual extruder case! |
Aha, will test that! |
@jonaskuehling, I'll write a regression test for this issue. Anyway, it looks like if you need to decrease the bridge speed for getting good support adhesion, maybe we need a separate setting for this instead of using bridge speed? I'm afraid 7-10mm/s isn't optimal for your actual bridges, is it? (Is this thing mentioned in another issue here?) |
I'm not quite sure about materials like PLA for example since we rather use it. For ABS in particular, as well as PET (Colorfabb XT) and some other more ABS-like plastics a slow bridge speed doesn't introduce trouble with "classic bridging" (between towers, unsupported), especially when using "don't support bridges" option. But I guess a lot of people using pretty fast PLA printers like Ultimakers and the like won't see the need for slow unsupported bridges just to improve support adhesion.. A dedicated speed parameter for support-adhesion-related bridging doesn't hurt in my oppinion! Not sure if the specific topic of this issue (bridge speed on top of raft) is already mentioned somewhere else. The support-adhesion problematic actually is - and we are incredibly happy to finally found a configuration that produces easily peelable but adhering support with Slic3r's built-in logic, that just turns out to be amazingly powerful as you always promised @alexrj ;-) |
@alexrj when talking about a dedicated speed setting for supported perimeters, let me make another suggestion: Thus, I'd suggest handling all perimeters where there is support generated for as "supported perimeters" and apply the new "supported perimeters speed" value. This way we have a clear separation between bridges and supported perimeters, while covering the full supported surface area. What do you think? |
… layers. This behavior is more consistent when all the other bottom surfaces lying on the void (thus on support material). #2301
Okay, I pushed a change that treats first object layer above raft just like any other bottom surface above support material, as per your original report. Regarding your last comment, you're right (and you're a good observer!): overhang detection for perimeters and support material generation use different logic, so they might not catch the same things. The former requires that the overhang is equal or greater to one nozzle diameter (i.e. it's an overhang if nozzle is pushing plastic entirely on the void), while the latter triggers support whenever the loop centerline lies on void. Support material is thus generated more often. This level of sensitivity would be too much for perimeter overhang detection (it was implemented like this, and it produced lots of changes in flow causing bad quality on vases) so I think it would be correct to use the nozzle diameter logic for support material as well. |
Hey,
we recently had significant success with current break-away support integration (1.1.7) by massively decreasing the bridge speed, as supported perimeters and infill regions are treated as bridges and - as others also experienced lately - the support adhesion was rather bad due to the minimal contact between support and model when printed too fast.
By using really slow bridge speed (talking about ABS here) like 7-10mm/s we could get the current support working quite satisfying, as the supported regions have more time to securly lay down on the support interface and round perimeters don't get dragged away as the print head moves on.
Now, the first model layer on top of raft doesn't use bridge speed, although it is printed with bridge logic.
I guess that's not intended? :-)
The text was updated successfully, but these errors were encountered: