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: Support z-contact distance Optional with Detect Bridges #2620

Closed
AbeFM opened this issue Jul 11, 2019 · 4 comments
Closed
Labels

Comments

@AbeFM
Copy link

AbeFM commented Jul 11, 2019

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:

Perhaps "Loose Bridge Support" should be an option which retains the current behavior, and "Tight Bridge Support" would be the version where the supports keep the same distance above bridges and non-bridges (hence leaving out weird factors of nozzle diameter, etc).

You could change either "Loose" or "Tight" to "Normal" if you prefer the term.

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!

@AbeFM
Copy link
Author

AbeFM commented Jul 11, 2019

Original Post:

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.

Here's some quick data collected:

z-contact-distance | Layer height | XY dist % of 0.2 | Support | Object | As printed Distance | Error | `

z-contact-distance Layer height XY dist % of 0.2 Support Object As printed Distance Error  
0 0.08 50 1.54 1.62 0 0  
0.001 0.08 50 1.22 1.62 0.32 0.319  
0.1 0.08 50 1.12 1.62 0.42 0.32  
0.2 0.08 50 1.02 1.62 0.52 0.32  
0.5 0.08 50 0.72 1.62 0.82 0.32  
               
z-contact-distance Layer height XY dist % of 0.2 Support Object As printed Distance Error  
0 0.1 50 1.52 1.63 0.01 0.01  
0.001 0.1 50 1.22 1.63 0.31 0.309  
0.1 0.1 50 1.13 1.63 0.4 0.3  
0.2 0.1 50 1.02 1.63 0.51 0.31  
0.5 0.1 50 0.73 1.63 0.8 0.3  
z-contact-distance Layer height XY dist % of 0.2 Support Object As printed Distance Error  
0 0.15 50 1.54 1.69 0 0  
0.001 0.15 50 1.24 1.69 0.3 0.299  
0.01 0.15 50 1.23 1.69 0.31 0.3  
0.05 0.15 50 1.19 1.69 0.35 0.3  
0.1 0.15 50 1.14 1.69 0.4 0.3  
0.2 0.15 50 1.04 1.69 0.5 0.3  
0.5 0.15 50 0.74 1.69 0.8 0.3  
               
z-contact-distance Layer height XY dist % of 0.2 Support Object As printed Distance Error  
0 0.15 5 1.54 1.69 0 0  
0.05 0.15 5 1.19 1.69 0.35 0.3  
0.1 0.15 5 1.14 1.69 0.4 0.3  
0.2 0.15 5 1.04 1.69 0.5 0.3  
0.5 0.15 5 0.74 1.69 0.8 0.3  
               
z-contact-distance Layer height XY dist % of 0.2 Support Object As printed Distance Error  
0 0.2 50 1.45 1.69 0.04 0.04  
0.001 0.2 50 1.25 1.69 0.24 0.239  
0.1 0.2 50 1.15 1.69 0.34 0.24  
0.2 0.2 50 1.05 1.69 0.44 0.24  
0.5 0.2 50 0.75 1.69 0.74 0.24  
               
z-contact-distance Layer height XY dist % of 0.2 Support Object As printed Distance Error First Layer
0 0.3 50 1.58 1.88 0 0 125%
0.001 0.3 50 1.48 1.88 0.1 0.099 125%
0.1 0.3 50 1.38 1.88 0.2 0.1 125%
0.2 0.3 50 1.28 1.88 0.3 0.1 125%
0.5 0.3 50 0.99 1.88 0.59 0.09 125%
               
z-contact-distance Layer height XY dist % of 0.2 Support Object As printed Distance Error First Layer
0 0.3 50 1.5 1.8 0 0 100%
0.001 0.3 50 1.41 1.8 0.09 0.089 100%
0.1 0.3 50 1.31 1.8 0.19 0.09 100%
0.2 0.3 50 1.21 1.8 0.29 0.09 100%
0.5 0.3 50 0.91 1.8 0.59 0.09 100%
`
or see https://forum.prusaprinters.org/forum/english-forum-general-discussion-announcements-and-releases/minimum-support-distance/#post-152704

Really I just want to know how to make the supports supportive. And I have a STRONG suggestion that the tool tips be updated to reflect that changing the "z contact distance" won't effect the "z contact distance".

As usual, if there is ANYTHING I can do to help this progress, help with the understanding, justification, etc, please let me know.

@AbeFM AbeFM changed the title Support z-contact distance errors causing poor overhangs. Feature Request: Support z-contact distance Optional with Detect Bridges Jul 11, 2019
@bubnikv
Copy link
Collaborator

bubnikv commented Mar 18, 2021

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

Implemented with ceea9de f01f021

Duplicate of #341 #4126 #2217

@ProTubeVR
Copy link

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

Implemented with ceea9de f01f021

Duplicate of #341 #4126 #2217

Hi,
Is it possible to test this ?
(sorry i don't find the build with it)

@bubnikv
Copy link
Collaborator

bubnikv commented Mar 19, 2021 via email

@bubnikv bubnikv closed this as completed Mar 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants