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

Floating lines on Overhang Walls with Inner/Outer/Inner sequence! #4709

Open
3 tasks done
Vitorleoron opened this issue Mar 25, 2024 · 7 comments
Open
3 tasks done

Floating lines on Overhang Walls with Inner/Outer/Inner sequence! #4709

Vitorleoron opened this issue Mar 25, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@Vitorleoron
Copy link

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.0.0-rc

Operating System (OS)

Windows

OS Version

11

Additional system information

No response

Printer

K1 Max

How to reproduce

When I printed some object that have some overhang walls, with this settings above:

Configs Orca

When it reaches the layer that start close the hole, it prints the Inner wall of the bridge/overhang wall first then the "Outer" and the Inner, so it prints this lines floating, as the video above:

20240325_185517.mp4

Actual results

The results in the print is this:

20240325_185453

Expected results

This bridges should be printed in the Inner/Outer order to be anchored by the other lines!

Project file & Debug log uploads

debug_network_Mon_Mar_25_17_44_52.log.zip

Checklist of files to include

  • Log file
  • Project file

Anything else?

No response

@Vitorleoron Vitorleoron added the bug Something isn't working label Mar 25, 2024
@SoftFever
Copy link
Owner

Does it happen in 1.9.1 or 2.0.0-beta too?

@Vitorleoron
Copy link
Author

Yes, worst in the 2.0.0-rc version, but in the overhang wall lines the problem still occur in the old versions too, in the 2.0.0-rc the floating lines happen more often

@SoftFever
Copy link
Owner

Yes, worst in the 2.0.0-rc version, but in the overhang wall lines the problem still occur in the old versions too, in the 2.0.0-rc the floating lines happen more often

Could you share the project? I'd like to see if there's been any regression.
Meanwhile, based on the photo, this model has very steep overhangs.
It's not recommended to use a sandwich or outer wall-first sequence for such models.

@Dustmuffins
Copy link

Dustmuffins commented Apr 28, 2024

Could you share the project? I'd like to see if there's been any regression. Meanwhile, based on the photo, this model has very steep overhangs. It's not recommended to use a sandwich or outer wall-first sequence for such models.

I'm not the OP, but I was able to recreate it on this file. See Layer 22.

I'm not sure if this is the best place to request this, but is it possible to request a feature to switch to inner/outer w/ precise walls if the overhang is this extreme?

large overhang.zip

@pavlokomarov
Copy link

@SoftFever is any updates? Faced with similar issue: outer wall overhang is printed first, despite Inner/Outer order. Orca slicer 2.1.1

2024-07-17.20.37.57.720.mov

@FelixBuehler
Copy link

Can confirm this issue. Setting is Inner/Outer, but the overhang wall gets printed first.
image

@tastyratz
Copy link

tastyratz commented Sep 30, 2024

Could you share the project? I'd like to see if there's been any regression.

@SoftFever AFAIK this upstream Prusa issue remains open

FYI:
This issue is another instance of
#1340 and it could be significantly improved or mitigated by implementing #6073

This is actually an upstream issue with Arachne and incorrect bridge/overhang detection causing free air prints. I've done extensive testing in the original bug report.

Having the SS no perimeters on bridging setting won't stop Arachne from detecting bridges incorrectly but it does stop it from printing them in free air before the walls they attach to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants