Replies: 1 comment 2 replies
-
Hello!
Could you please provide exact script you are using and meshes to reproduce the result? (if you don't want to share data publicly, you can send it to or email Also, please note that we have function for uniting several meshes at once: |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi MeshInspector Team,
Thank you for the great software and library tools for working with meshes.
I am currently working on a project in python where I am merging multiple mesh segments together with a boolean union to create a watertight mesh.
As part of the process I have to do some cleaning of the data along the way.
Currently I have used:
mrmeshpy.fixMultipleEdges(mesh_obj)
mrmeshpy.uniteCloseVertices(mesh_obj, 0)
to fix some of the issues during the merging.
Everything is working and coming out well, however when I check the merged mesh in MeshInspector, some of the files have zero_area triangles.
I have tried to add:
mrmeshpy.fixMeshDegeneracies(mesh_obj, params) - (using 0.0000001 value)
during the processing but it made the result worse and caused segments that aren't close together to interpolate between them.
I think I need to run it at the end on the final mesh, not during the generation process as per the other corrections which are fixed during the merging process (iteratively when error identified).
Would mrmeshpy.fixMeshDegeneracies(mesh_obj, params) be the correct process to run to fix zero-area triangles and do I need to run a fill holes or something else afterwards to ensure the mesh is watertight still?
Should I run it at the end of the merge only or is there a way to identify if there are zero-area triangles after each merge iteration?
Any advice or suggestions would be greatly appreciated.
Regards,
Glen.
Beta Was this translation helpful? Give feedback.
All reactions