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

Organic supports from PrusaSlicer (vs Tree supports in BambuStudio) #2420

Closed
Gnof opened this issue Aug 29, 2023 · 4 comments
Closed

Organic supports from PrusaSlicer (vs Tree supports in BambuStudio) #2420

Gnof opened this issue Aug 29, 2023 · 4 comments
Assignees
Labels
feature New feature or request

Comments

@Gnof
Copy link

Gnof commented Aug 29, 2023

Is your feature request related to a problem? Please describe.
The current tree supports aren't as functional as the organic supports that are currently in Prusa slicer.

Specifically, tree supports often overlap with the model and cause scarring / artifacts on the printed model surface:
Slicer 1

Describe the solution you'd like
This issue does NOT occur on Prusa slicer with the same model with their implementation of tree supports (known as OrganicSupports in their source I believe? https://github.com/prusa3d/PrusaSlicer/blob/c05542590d7c2d73eb69bbf7a82a482a075815c1/src/libslic3r/Support/OrganicSupport.cpp)

Is it possible to port their supports implementation over to Bambu Studio?

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

The following settings have been tested to attempt to remediate the issue:
(Tested with all tree Styles [Default, hybrid, strong, slim])

  • "On build plate only" - turned ON (off puts the supports directly on the model, causing more issues)
  • "Support critical regions only" - tested ON and OFF
  • "Remove small overhangs" - tested ON and OFF
  • "Top Z distance" - set to 0, as well as adjusted +
  • "Support / object xy distance" - set to larger numbers (2-3 mm+ to test) this actually results in the following:
    slice5

Additional context
Add any other context or screenshots about the feature request here.

I'd actually be happy to try and do this myself but I figured I'd put in a feature request in case it's either already on the roadmap or you guys have explored this and there's some reason it can't be done so simply (which would save me the time of trying to port the feature and finding out there's a deeper issue with it)

Thanks guys!

@Gnof Gnof added the feature New feature or request label Aug 29, 2023
@Gnof
Copy link
Author

Gnof commented Aug 29, 2023

Sharing this comparison of the PrusaSlicer Organic support on the same model
slice6

@Edzi11
Copy link

Edzi11 commented Aug 29, 2023

Would be nice to get an update on the support generation since they arent super good sometimes. I've had instances of support generating mid-air or in areas that had no need for support.

@Noisyfox
Copy link
Contributor

SoftFever/OrcaSlicer#1938
Maybe try the latest Action build here.

@Edzi11
Copy link

Edzi11 commented Aug 31, 2023

SoftFever/OrcaSlicer#1938 Maybe try the latest Action build here.

Thanks will give this a try!

lanewei120 pushed a commit that referenced this issue Nov 1, 2023
Add a new suport style "Tree Organic" from Prusa, as organic support is
faster and seems more strong in some cases. Thanks to Prusa.

Feature detection including sharp tail, small overhang, long cantilever,
are still kept.

Known issue: first layer support path may go outside build plate.

Jira: STUDIO-2358
Github: #2420

Change-Id: I4cec149bf4fa9eb733ae720ac1a7f65098e3b951
(cherry picked from commit d977bc5d3b4609f4fec0aa68152a33cacf184c4a)
lanewei120 pushed a commit that referenced this issue Nov 1, 2023
Add a new suport style "Tree Organic" from Prusa, as organic support is
faster and seems more strong in some cases. Thanks to Prusa.

Feature detection including sharp tail, small overhang, long cantilever,
are still kept.

Known issue: first layer support path may go outside build plate.

Jira: STUDIO-2358
Github: #2420

Change-Id: I4cec149bf4fa9eb733ae720ac1a7f65098e3b951
(cherry picked from commit d977bc5d3b4609f4fec0aa68152a33cacf184c4a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants