-
-
Notifications
You must be signed in to change notification settings - Fork 939
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: Merge in "No perimeters on bridge areas" from SuperSlicer #6073
Comments
Related: #5376 |
Orca bot: this issue is stale because it has been open for 90 days with no activity. |
I really hate to see this one go stale because it's such a big issue with an existing workaround we can port from superslicer. Fixing Arachne upstream is a bigger conversation but maybe this is a quick fix that helps for now? Specifically, it gives us a workaround for #1340 |
Hit this issue as well. This is a major problem for functional parts, where thick walls are often required for strength. In my case, My print is effectively capped at 3 wall loopss (.82mm line width w/ .8mm nozzle). Orca slicer starts to generate floating walls and bridges with 4 & above wall loops. |
I absolutely upvote this one as well. It also causes weird behavior where the ceiling of the benchy cabin is printed completely in mid air, instead of using a bridge. |
Is there an existing issue for this feature request?
Is your feature request related to a problem?
Bridging issues with Arachne are prevalent where it constantly tries to draw a bridge over free air. While this setting won't SOLVE many of those edge cases it WILL allow bridges to properly anchor in many other scenarios and drastically improve bridge performance.
Which printers will be beneficial to this feature?
All
Describe the solution you'd like
I think Orcaslicer could adopt this already available feature from SS for big gains in bridging performance.
Describe alternatives you've considered
No response
Additional context
A similar request was made upstream at Prusaslicer
prusa3d/PrusaSlicer#12721
However, there are no signs yet that they are considering any kind of pull back.
The text was updated successfully, but these errors were encountered: