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

Add mesh utilities nodes #1271

Merged
merged 3 commits into from
Feb 12, 2021
Merged

Add mesh utilities nodes #1271

merged 3 commits into from
Feb 12, 2021

Conversation

gregoire-dl
Copy link
Member

Description

Add two nodes for mesh boolean operations and mesh conversion.

Features list

  • Add MergeMeshes node
  • Add ConvertMesh node

See alicevision/AliceVision#969

@natowi
Copy link
Member

natowi commented Feb 12, 2021

This part should be added to the MergeMeshes documentation/(probably too much for the description field):

Operation types used to merge two meshes:

  • boolean_union: Create a new mesh with the combined volume of the two input meshes.
  • boolean_intersection: Create a new mesh from the intersected volumes of the two input meshes.
  • boolean_difference: Create a new mesh from the volume of the first input mesh subtracted by the second input mesh.

@fabiencastan fabiencastan added this to the Meshroom 2021.1.0 milestone Feb 12, 2021
@fabiencastan fabiencastan merged commit ed1f3e0 into develop Feb 12, 2021
@fabiencastan fabiencastan deleted the dev_addMeshUtils branch February 12, 2021 11:45
@flobotics
Copy link

flobotics commented Apr 23, 2022

hi,
i tried it, but did not work ? Also is there a way to output .obj also, now it seemed to output .stl only ?

After which node should the mergeMeshes node be added, after texturing?

The error in the log-view is like:

o-[DelaunyTetgen] Warning constraints have 4 edges on the border
Error: Encounterd a problem ,relaunch in diagnose mode
Error: Found 27 facets with intersections
o-[Booleans] Error could not tetrahedralize operand B

Then it saves an empty .stl file.

--I tried boolean-union option--

Or do i need to add e.g. 3-5 pictures from the first mesh into the "build"-process of the second textured-mesh and after that, mergeMesh A with mesh B ? So that the second mesh "knows" something ( compares camera alignment, position, etc. of these 3-5 camera-poses of second-mesh, to the camera alignment, position,etc. of the 3-5-camera-poses in the first mesh ) of the first mesh ?

thx for help

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

Successfully merging this pull request may close these issues.

4 participants