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: Merge in "No perimeters on bridge areas" from SuperSlicer #6073

Open
1 task done
tastyratz opened this issue Jul 9, 2024 · 6 comments
Open
1 task done
Labels
enhancement New feature or request

Comments

@tastyratz
Copy link

Is there an existing issue for this feature request?

  • I have searched the existing issues

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.

@tastyratz tastyratz added the enhancement New feature or request label Jul 9, 2024
@lhndo
Copy link

lhndo commented Aug 24, 2024

Related: #5376

Copy link

Orca bot: this issue is stale because it has been open for 90 days with no activity.

@github-actions github-actions bot added the stale label Nov 23, 2024
@tastyratz
Copy link
Author

tastyratz commented Nov 23, 2024

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

@github-actions github-actions bot removed the stale label Nov 24, 2024
@ZigZagT
Copy link

ZigZagT commented Dec 7, 2024

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.

3 wall loops
3 walls

4 wall loops
4p

@henrivdr
Copy link
Contributor

henrivdr commented Dec 7, 2024

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.

@evilC
Copy link

evilC commented Dec 14, 2024

I would also like to see this, but for a different reason
I am currently trying to print in CarbonX ezPC+CF, and this stuff is a right pain with bridging
For normal bridging, I can slow right down and it will be OK, but the perimeters do not play ball even when slowed down
Here is a test part:
image
Here is how it comes out:
image
As you can see, the normal bridge is OK, but the perimeters simply do not hold up. The sag you can see in the bottom right is at the start of the bridge for that perimeter - ie it started top left corner, did the top edge, then the right edge, then the perimeter bridge at the bottom of the picture.
What I think is happening is that for the perimeter, the pressure has built up in the nozzle, and once the floor beneath the nozzle disappears, the filament is free to just squirt out.
When it does the normal bridge, it will stop extruding, move to the start of the bridge, and then start extruding, and I think it must not have that same pressure built up.
I have tried using "Extrusion Rate Smoothing", even setting it to a ludicrously low value of 2, to get it to ramp down the pressure really slowly, and start slowing down earlier:
image
But this does not solve the problem.
My hunch is that if I could disable bridge perimeters, then all would be OK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants