Skip to content

Fix shared boundary fan artifacts with multiple boundary loops (#2610) - #2671

Merged
akenmorris merged 1 commit into
masterfrom
amorris/2610-bug
Oct 12, 2026
Merged

akenmorris merged 1 commit into
masterfrom
amorris/2610-bug

Conversation

@akenmorris

Copy link
Copy Markdown
Contributor

Fixes #2610

snap_boundary_to_mesh snapped whichever boundary loop libigl returned first, so a pre-existing loop (e.g. a cropped shaft) could be dragged onto the shared boundary. Snap only the seam vertices left by removing the shared surface, against all loops of the shared surface.

extract_boundary_loop now picks the longest loop instead of an arbitrary one. Adds regression tests for both.

snap_boundary_to_mesh snapped whichever boundary loop libigl returned
first, so a pre-existing loop (e.g. a cropped shaft) could be dragged
onto the shared boundary. Snap only the seam vertices left by removing
the shared surface, against all loops of the shared surface.

extract_boundary_loop now picks the longest loop instead of an
arbitrary one. Adds regression tests for both.
@akenmorris
akenmorris merged commit bc942d5 into master Oct 12, 2026
5 checks passed
@akenmorris
akenmorris deleted the amorris/2610-bug branch October 12, 2026 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Shared boundaries: fan artifacts in meshes with multiple boundary loops

1 participant