XY hole compensation causes print artefacts on large holes

[laukejas]

Is there an existing issue for this problem?

• I have searched the existing issues

OrcaSlicer Version

2.3.0-dev

Operating System (OS)

Windows

OS Version

Windows 10

Additional system information

No response

Printer

Voron 2.4

How to reproduce

When a hole in the model has a partial opening to the outside of the part, and xy_hole_compensation is set to a non-zero value, OrcaSlicer assumes the layers with the opening to be part of the external perimeter (which is technically true), which results in print artifact - a ridge inside the hole:

While this is technically correct, it is clearly undesirable in such cases, and there is no way to fix it, at least none that I can find.

To recreate the issue:

1. Open the attached .3mf.
2. Slice the model with the current settings (default profile + xy_hole_compensation set to 0.15mm)

Actual results

A ridge forms in the large hole on the layers where it connects to the external perimeter via a small hole.

Expected results

The large hole should maintain it's diameter throughout it's entire height.

Project file & Debug log uploads

A00001091.zip

Checklist of files to include

• Log file
• Project file

Anything else?

Please make Orca aware of such situations, or at least provide the user with a way to fix these cases with some manual effort.

[Mario-vminion]

it's an old bug and it returns....

[laukejas]

@Mario-vminion So it is indeed classified as a bug? When I discovered it's due to hole connecting to the external perimeter, I kind of thought it's logical for software to do this, even if undesirable for the user. Do you mean to say it was solved somehow, but now returned?

[Mario-vminion]

I had it reported in October 2023

[laukejas]

@Mario-vminion Do you have a link to that issue? Not sure what you named it. Maybe we should merge them.

[Mario-vminion]

No it was closed and it was solved…then

[laukejas]

@Mario-vminion Closed issues should still be here in this repo. If you have the time to find that issue you posted, it would be great. We could reopen it. Devs typically view returned issues (regressions) with much more priority than new issues.

[Mario-vminion]

maybe this one #736