Replies: 1 comment 1 reply
-
That's probably related to compilation flags, or floating point precision (MeshLab 2022.02 uses floats, 2022.02d uses double). MeshLab does nothing magic on boolean operations, it just calls igl. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've recently been using boolean operations in libigl, but the calculations are less ef
ficient for complex 3D objects. But when I use meshlab for boolean operations, the time can be 2~3 times faster. After that, I took a brief look at the source code of the Boolean operation module in meshlab, and also called the libigl library, but why is the efficiency much faster than calling libigl myself?
It can be seen that meshlab also calls the Boolean operation in libigl through the igl::copyleft::cgal::mesh_boolean() interface.
I tried to test with 3D objects with different numbers of triangles, and the speed of meshlab is about 2 or 3 times faster than my own code.
Beta Was this translation helpful? Give feedback.
All reactions