OrcaSlicer icon indicating copy to clipboard operation
OrcaSlicer copied to clipboard

"Bridges do not overlap perimeters which result in failed print"

Open vadixidav opened this issue 1 year ago • 15 comments

Is there an existing issue for this problem?

  • [X] I have searched the existing issues

OrcaSlicer Version

2.1.1

Operating System (OS)

Windows

OS Version

Windows 11

Additional system information

No response

Printer

Bambu Lab P1S

How to reproduce

This is a known bug. See https://github.com/prusa3d/PrusaSlicer/issues/9999. It was fixed upstream in PrusaSlicer. It has not been merged to Orca.

Slice any model which has a thin section with more wall loops enabled than can be printed and a bridge subsequently next to that spot. Other situations can trigger this as well.

Actual results

Again, see https://github.com/prusa3d/PrusaSlicer/issues/9999 or https://github.com/prusa3d/PrusaSlicer/issues/11150.

Here is an example of the outcome on a model I am printing:

image

Note that the bridge is not anchored to the print at all and simply prints in mid-air. This should be well understood already by most people since this happens for most functional prints (>50%) if they contain a bridge and when Orca Slicer is used with 3 or more walls. For people who use 2 or 1 wall, this may not occur as often as the number of walls is not sufficiently high to prevent the bridge. Most authors worked around this issue by modifying their model so that Prusa and Orca slicer would print them correctly with 2 walls at most, but many authors did not care to support the 3 wall case. Now this is fixed for any number of wall loops.

Expected results

The bridge should be anchored. See https://github.com/prusa3d/PrusaSlicer/issues/9999. Fixed in Prusa slicer 2.7.3.

Project file & Debug log uploads

The project I am currently working on has 11 parts in it and it would only be confusing to upload. Please see the Prusa slicer issue for details https://github.com/prusa3d/PrusaSlicer/issues/9999. There are also other issues open on Orca Slicer which may be caused by this issue, but are other bridging-related issues which were fixed in Prusa Slicer, but I don't believe they have been properly connected to this underlying issue yet.

Checklist of files to include

  • [ ] Log file
  • [ ] Project file

Anything else?

I think contributors are already aware of this ongoing related work due to the mention of the PrusaSlicer issue in the discussion, but also see https://github.com/SoftFever/OrcaSlicer/pull/4651. This issue is just to formally note that the bridge fixes should be merged into Orca Slicer.

vadixidav avatar Jul 27 '24 05:07 vadixidav

yess! there should be at least a bridge wall overlap at minimum.. as well as a slow bridge layer count as someone else has suggested so it doesn't go from a slow layer then back to full speed as the combo of these two dramatically reduces quality of bridging

digital0785 avatar Aug 09 '24 20:08 digital0785

I've tested slicing a model I'm trying to print several different ways in Orca Slicer and find that no matter the number of perimeters (walls) I select or the orientation of the bridge, Orca attempts to create bridges that are either not anchored or attempt to run the longest path on the model.

Longest path: image image

Unanchored (mid-air): image image

jamincollins avatar Aug 20 '24 15:08 jamincollins

While the same model with similar settings slices much more sanely in Prusa Slicer: image

jamincollins avatar Aug 20 '24 15:08 jamincollins

Same problem over here. Reducing walls loops to 2 helps.

4 wall loops: image

2 wall loops: image

adolfotregosa avatar Oct 27 '24 10:10 adolfotregosa

A very unfortunate workaround to this problem is to use a very slight incline (only a few degrees) on your "flat" surface. This obviously means your flat surface won't be flat, but it will slice correctly with a sufficiently large incline. I would use Orca slicer but I absolutely require the Precise Wall setting, and Orca slicer has no fix for this issue. I still encounter it daily as I work on prints and have spent many hours of my time working around it and occasionally printing things only to realize there was a spot where a bridge didn't connect.

vadixidav avatar Oct 28 '24 20:10 vadixidav

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

github-actions[bot] avatar Jan 27 '25 00:01 github-actions[bot]

Please integrate this from prusa it'll be an overall improvement

digital0785 avatar Jan 27 '25 00:01 digital0785

plus for it! Bridging is a pain in orca!

Dedoque avatar Mar 22 '25 20:03 Dedoque

plus for it! Bridging is a pain in orca!

this has been fixed in 2.3 i believe as well as multiple bridging layers

digital0785 avatar Mar 22 '25 20:03 digital0785

Image doesn`t seems like a fix

Dedoque avatar Mar 23 '25 08:03 Dedoque

Image doesn`t seems like a fix

you're not showing an external bridge layer which is what this is referring too the only reason an internal bridge would have an issue is because theres too long a span without infill which is not a slicer issue. notice how the SS i posted it deviates from the wall path to give the bridge an anchor

Image

digital0785 avatar Mar 23 '25 10:03 digital0785

Yes, I didn't explicitly mention external bridges, but this was specifically in relation to external bridges. The issue should not be closed though. The bot merely closed it because it went stale. It is not fixed as far as I am aware.

Edit: I see this may have been fixed according to the above comments. I will look into it and close the issue if so.

vadixidav avatar Mar 25 '25 13:03 vadixidav

I tested this in OrcaSlicer 2.3.0 and the bug persists. For instance, this multi-board bin results in floating bridges when sliced with wall loops set to 100:

Image

When you set walls to 2 and bottom layers to 1, it works correctly for this print as can be seen here:

Image

Here is a desiccant holder print with wall loops set to 4:

Image

When we set wall loops to 1, it works correctly:

Image

Essentially, if you increase the wall loops, eventually it will stop completing the bridge. This issue is not fixed yet as of OrcaSlicer 2.3.0.

vadixidav avatar Mar 25 '25 13:03 vadixidav

Enabling Ensure vertical shell thickness helped me. When it was turned off, there was only overhang on one perimeter.

Image

off: Image

all: Image

The difference in quality was huge.

Image

Bata3 avatar Mar 30 '25 16:03 Bata3

i have it on moderate that could be why i didn't notice :)

digital0785 avatar Mar 31 '25 01:03 digital0785

Enabling Ensure vertical shell thickness helped me. When it was turned off, there was only overhang on one perimeter.

Image

off: Image

all: Image

The difference in quality was huge.

Image

Did you also try changing the number of walls? I believe that if you increase the number of walls that you would still get a non-overlapping bridge. That being said, it is good to see that in some situations the bridging behavior can be worked around.

vadixidav avatar Mar 31 '25 15:03 vadixidav

Did you also try changing the number of walls? I believe that if you increase the number of walls that you would still get a non-overlapping bridge. That being said, it is good to see that in some situations the bridging behavior can be worked around.

It doesn't matter how many perimeters there are, the bridging overlap will always be correct.

Image

Image

Bata3 avatar Mar 31 '25 15:03 Bata3

The bridge feature in Orca Slicer is still completely broken (2.3.0):

Image

In practice the slicer is unusable. This issue has been there for years now!! Instead of adding questionable features, the developers should solve this fundamental bug. Probably they use some other slicer for their daily prints!!!

GroovybandLive avatar Apr 03 '25 07:04 GroovybandLive

I think what is happening is that Orca doesn't adjust the location of the bridge overlap when perimeter count exceeds the actual available space. It seems to even add overhanging perimeters in empty space to try to make up for the difference. A lame workaround is to use the height range modifier to decrease the perimeters in the layer having issues. This also happens in Bambu slicer.

Image

yeahdino avatar Apr 07 '25 21:04 yeahdino

I've been struggling with this for a week. I'm running 2.3.0. I tried the latest nightly as of today because there was a commit entry that claimed to fix this. Well it did - until I imported my profile then it returned. That prompted me to check every setting again and I finally determined setting "Bridge counterbore holes" to "none" fixes it. So I hope that might be a clue that could get this fixed.

kniftar avatar Apr 09 '25 21:04 kniftar

I've been struggling with this for a week. I'm running 2.3.0. I tried the latest nightly as of today because there was a commit entry that claimed to fix this. Well it did - until I imported my profile then it returned. That prompted me to check every setting again and I finally determined setting "Bridge counterbore holes" to "none" fixes it. So I hope that might be a clue that could get this fixed.

I had to change the settings from "none" to anything else and it fixed my print. I scaled my model down beyond the treshold discussed here with the walls and the bridges started to collapse. The threshold in the model for me is on 0.4mm nozzle around 0.8mm thick walls, above it works, below it collapses.

jkortus avatar Jun 11 '25 21:06 jkortus

Instead of adding questionable features,

I am sorry to read this. Many of the "questionable features" are done by the community in their spare time to add features they consider improvements.

The threshold in the model for me is on 0.4mm nozzle around 0.8mm thick walls, above it works, below it collapses.

Can you send me a project file from the las nightly that fails and show me where it fails?

ianalexis avatar Jul 14 '25 15:07 ianalexis

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

github-actions[bot] avatar Oct 13 '25 00:10 github-actions[bot]

Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale.

github-actions[bot] avatar Oct 20 '25 00:10 github-actions[bot]