-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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: Support z-contact distance Optional with Detect Bridges #2620
Comments
Original Post:
|
To improve quality of the object over support, we have added a new settings: "thick bridges". If enabled (that is by default), PrusaSlicer behaves as before. If disabled, bridges are printed as in any other slicer: The extrusion rate is given by the normal layer height x extrusion width * bridge flow ratio. |
Hi, |
Yes, once we have the first public alpha out.
pá 19. 3. 2021 v 15:25 odesílatel ProTubeVR ***@***.***>
napsal:
… To improve quality of the object over support, we have added a new
settings: "thick bridges". If enabled (that is by default), PrusaSlicer
behaves as before. If disabled, bridges are printed as in any other slicer:
The extrusion rate is given by the normal layer height x extrusion width *
bridge flow ratio.
[image: image]
<https://user-images.githubusercontent.com/5830947/111674988-e9ecbc80-881c-11eb-968f-de0954195229.png>
Implemented with ceea9de
<ceea9de>
f01f021
<f01f021>
Duplicate of #341 <#341>
#4126 <#4126> #2217
<#2217>
Hi,
Is it possible to test this ?
(sorry i don't find the build with it)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2620 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSIZCB3H7ZNSH7VLIOEDTENNHDANCNFSM4IBRVD3Q>
.
|
Version
2.0.0
Operating system type + version
win10
3D printer brand / version + firmware version (if known)
mk3smmu2s, 3.7.1
Behavior
Supports leave an extra gap. I had this issue well over a year ago, read about #102 #102, and a few others. Since it seemed well understood at the time, I assumed it would get fixed.
Upon further reflection, I've realized this is something the Devs are well aware of. Rather than discuss its merits as a bug - I have a suggestion/Feature request:
Several people have expected the support contact z-distance to directly express the distance from the bottom of the printed material to the supports, and the change in behavior with "detect bridging perimeters" is not only unexpected, but limiting for those times where the advanced user wants to generate tight supports while retaining the advantages of the bridging support currently available in PrusaSlicer.
As mentioned in the forum thread linked below:
Note, I moved the original post to the first comment as I think it's irrelevant, this is really a feature request. Sorry for the confusion!
The text was updated successfully, but these errors were encountered: