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

Tree supports - do not avoid support blocker #14208

Open
evilC opened this issue Jan 4, 2023 · 5 comments
Open

Tree supports - do not avoid support blocker #14208

evilC opened this issue Jan 4, 2023 · 5 comments
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: New Feature Adding some entirely new functionality.

Comments

@evilC
Copy link

evilC commented Jan 4, 2023

Is your feature request related to a problem?

The new tree supports in A5.3.0+xmas are great, but not creating supports inside the support blocker area is not always desirable.

Consider the following slice:
image
(The support blocker is the selected box in this picture)
Here, the intent is to not generate supports for the bridges inside the support blocker (The tops of the 6 vent holes on each side), but an undesired effect is also happening - the supports for the clips at the top of the picture are routing around the support blocker, when they don't need to

Admittedly, the solution here is rather simple (Just scale down the support blocker a bit), but that's more hassle, and may not always be possible?

Describe the solution you'd like

An option that specifies that supports may travel THROUGH a support blocker, but may not support a face WITHIN the support blocker

Describe alternatives you've considered

Size down the support blocker or use multiple smaller ones

Affected users and/or printers

All

Additional information & file uploads

No response

@evilC evilC added Status: Triage This ticket requires input from someone of the Cura team Type: New Feature Adding some entirely new functionality. labels Jan 4, 2023
@ThomasRahm
Copy link
Contributor

Currently this behavior is intentional and permanently enabled. Making this into a setting would be very easy.
The big question (for the guys at UltiMaker) is whether such a setting is needed (resizing the support blocker would achieve the same result here) or only causes setting-bloat.

@evilC
Copy link
Author

evilC commented Jan 5, 2023

Imagine a scenario such as this:
image

(Section analysis enabled so that you can see inside)
In this case, you may want to not bother with support for the tops of the feet (They are short bridges), only the roof in the middle really needs support as it is a long bridge
If this option were added, you would need one support blocker to stop it trying to create supports for the tops of the feet
With the code as it stands, you would need 4 support blockers, because by placing one support blocker which blocks the top of all of the feet, you would also block supporting of the central roof

@MariMakes
Copy link
Contributor

Hey @evilC,

Thanks for raising this.
I really like your example. 👍
I've brought it up for consideration to the team.

For internal reference - CURA-10161

@MariMakes MariMakes added Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. and removed Status: Triage This ticket requires input from someone of the Cura team labels Jan 16, 2023
@wiretail
Copy link

wiretail commented May 9, 2023

For what it's worth, having the ability to block where supports route and merge, and thus control/guide them a little, is a quite useful feature I wouldn't want to see removed. (You could still use actual models set to have no walls printed I suppose as blockers -- as you have to do that to control/break up the tree monoliths in the prior incarnations of tree supports, and it's not ideal or obvious.)

I'd vote for a checkbox or similar on the support blocker object, letting you pick which behavior you want. Both can be desirable.

@MariMakes
Copy link
Contributor

Update from our side. @ThomasRahm seems to have the resolved this issue here: Ultimaker/CuraEngine@1d62038
You can expect it in the next Cura release 😉 👍

@MariMakes MariMakes added Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. and removed Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. labels May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: New Feature Adding some entirely new functionality.
Projects
None yet
Development

No branches or pull requests

4 participants